Chkdsk failed and now won't quit running and failing on bootup.

Went to do a normal error check from windows XP home edition, just installed today, right clicked c drive > properties > tools > error check > checked both boxes > OKed checkdisk on reboot.

Windows Software 5498 This topic was started by ,


data/avatar/default/avatar18.webp

484 Posts
Location -
Joined 2001-10-23
Went to do a normal error check from windows XP home edition, just installed today, right clicked c drive > properties > tools > error check > checked both boxes > OKed checkdisk on reboot.
 
when it rebooted it said it cannot access the volume. I tried disabling viruscheck in BIOS and a couple other things, it didn't help. Now I would like to get it to run sucessfully or at least stop trying.
 
So far I've found these but the first doesn't help, and the second doesn't seem to apply, though I'm not certain.
 
http://support.microsoft.com/default.aspx?scid=kb;en-us;823439
http://support.microsoft.com/?kbid=235771
 
It doesn't give me the exact error listed in the top link, but it very similar.
 
Turns out I cannot boot to safe mod or command prompt. Eventually, the HD light stays on, but nothing happens, even after waiting a while.
 
Any ideas? Everthing seems to work fine in Windows XP home on when it gets there, and it's fresh off a new formatted reinstall of XP home. Boot sector was even scanned with latest NAV 2004 with updates, before and after reformat, and shows no viruses. Will run a complete scan, though I'm doubting the previous viruses lingered.
 
Any ideas?

Participate on our website and join the conversation

You have already an account on our website? Use the link below to login.
Login
Create a new user account. Registration is free and takes only a few seconds.
Register
This topic is archived. New comments cannot be posted and votes cannot be cast.

Responses to this topic


data/avatar/default/avatar18.webp

484 Posts
Location -
Joined 2001-10-23
OP
OK, I've done a fresh install after a quick zero out by the samsung utility on different hardware.
 
The first chkdsk was more of the same, Cleaning up of minor inconsitancies on the drive.
 
Then the next 3 all had no problems:
"Windows has checked the file system and found no problems."
 
Next, I put it back, but use the same cable as is attached to it now. Hopefully it's the cable and not the mobo.

data/avatar/default/avatar18.webp

484 Posts
Location -
Joined 2001-10-23
OP
1) Originally it was using an UDMA cable. When I threw it into my spare parts computer, it was using a standard IDE cable. It currently still is, and will scndsk a few times using it immediately after OS install (as done on the spare parts rig). After I do that, I'll probably test it in the same (original) computer, but using a different UDMA cable.
 
2) I ran the "no problems" chkdsk scans on the alternate HW with only the OS installation, no updates, no NAV etc. (not even SP1).
I'll run the next set of scans under the software conditions.
 
Right now I'm trying to figure out the the HW situation so I can return the computer to my friend. The windows disk can be used if need be for a scndsk. So I'm putting the NAV situation on the back burner.
 
3) I'll have to check that later, as I'm reformatting the HD again ATM.

data/avatar/default/avatar18.webp

484 Posts
Location -
Joined 2001-10-23
OP
Hmmm...
 
Not sure about the HD... Just (literally) found some new info and am trying to put it all together.
 
http://search.microsoft.com/search/resul...+chkdsk&s=1
 
I don't think the logs have been saying
"Windows has made corrections to the file system."
or
"Windows found problems with the file system."
 
So is this just simple housecleaning?