Hard drive problems

Discussion in 'General Hardware' started by GoNz0, Dec 1, 2003.

  1. GoNz0

    GoNz0 NTFS Stoner

    Messages:
    2,781
    Location:
    the year 2525
    hello every 1, well here i go again.

    80gb maxtor as my main drive, with windows on it. now every time i run chkdsk i get this
    anyway, i ran chkdsk /r and /f

    neither fix the problem. i ran powermax from the maxtor site to see if the drive was failing, it passed the 3 available tests on offer, including recertification and burn in scan's

    i reboot and run chkdsk from windows and same again (as the above quote)

    i have been into recovery console and ran fixboot & fixmbr, it didnt make the slightest bit of diffrence.

    im trying to avoid a low level format and reinstall, as its only been 2 months since the last format.

    it will be no biggie to low level the c drive, as i have 4 other drives to store my crap on, it would be nice to fix the problem though.

    any help is welcome :)

    (oh and it's via chipset, so i reinstalled the 4.49's as theres reported issues with the 4.50 release to the extent they took it off the site.)

    *edit* i use diskeeper 8, after all these issues cropped up i ran the boot time defrag to defrag the MFT, i was hoping mabey it would move it to another sector to fix the issue, but it remains.
     
  2. j79zlr

    j79zlr Glaanies script monkey Political User

    Messages:
    2,725
    Location:
    Chicago
    try running chkdsk /f from the recovery console. You shouldn't have to run fixmbr or fixboot unless you are having problem getting the drive to boot at all.
     
  3. GoNz0

    GoNz0 NTFS Stoner

    Messages:
    2,781
    Location:
    the year 2525
    read my post agin, i already tried that :(
     
  4. RogerPhillis

    RogerPhillis Guest

    Not much help .......... but I have used a Chaintech mobo with a Via chipset that came up with very similar errors on a Western H .Drive ; what I would call "Phantom " errors.

    So the system is always trying to put right errors that are not really there.
    I suppose it could be a H .Drive Controller issue.
     
  5. GoNz0

    GoNz0 NTFS Stoner

    Messages:
    2,781
    Location:
    the year 2525
    well i kinda ruled that out after rolling back to the 4.49's, no change as yet.
     
  6. GoNz0

    GoNz0 NTFS Stoner

    Messages:
    2,781
    Location:
    the year 2525
    well just to let you know, it looked like the phantom error you were on about roger, so after a full format, and reinstall, i don't get the errors anymore, shame it needed a format, oh well, glad i have 4 backup drives :)
     
  7. GoNz0

    GoNz0 NTFS Stoner

    Messages:
    2,781
    Location:
    the year 2525
    oh well the errors are back, i dunno what to do now.
     
  8. dave holbon

    dave holbon Moderator

    Messages:
    1,014
    Location:
    London England
    Do you have an APIC on you motherboard? This can cause these sorts of problems. If your board supports more than 16 interrupts via this chip you need to repair you XP installation even if you have the chip disabled as XP will detect it and then can’t understand why all your devices that use interrupts are sharing the same IRQ’s.

    During this process you will receive many blue screens of death but miraculously just when you are about to give up your system will work.




    :) :) :)
     
  9. GoNz0

    GoNz0 NTFS Stoner

    Messages:
    2,781
    Location:
    the year 2525
    huh?
     
  10. LeeJend

    LeeJend Moderator

    Messages:
    5,291
    Location:
    Fort Worth, TX
    APIC (an IC) I think it stands for Asynchronous Peripheral Interface Controller. Check under SYstem Mangler under MB stuff.
     
  11. GoNz0

    GoNz0 NTFS Stoner

    Messages:
    2,781
    Location:
    the year 2525
    new drive arrived this morning via advanced RMA, just got to swop the info to the new drive, and get the faulty unit returned within 30 days :)

    nice 1 maxtor, didnt even have to fill in a RMA, a nice irish guy phoned me and sorted it all out :)