CHKDSK performing hundreds of additional checking or recovery operations
Posted on 2009-04-20
I'm working on a computer for a client; it's probem is that it won't boot up. It passes POST but aborts when attempting to load Windows, either in Normal Mode or Safe Mode. Checking the condition of the hard drive was the obvious first step.
When I booted into the Recovery Partition and ran CHKDSK with no flags, it completed with no error messages or comments. Just to be sure, I set the /p flag and re-ran it; again, no error or comment. Then, just out of curiosity, I ran it with the /r flag set. This time, the line:
CHKDSK is performing additional checking or recovery ...
appeared dozens or even hundreds of times before it completed it's task (I can't accurately estimate this, since they scroll upward off of the viewable screen).
Naturally, not having seen anything even close to this number of repetitions of this line, I was concerned. I tried the whole sequence over again (1. Run CHKDSK without flags, 2. Run it with '/p' flag set and 3. Run with '/r' flag set). It did the same exact thing again; that is, no errors are reported in runs 1 and 2, but dozens or hundreds of the 'CHKDSK is performing additional checking or recovery ...' messages are generated.
Naturally, I'm worried about the condition of this drive. Is this okay? Does it indicate the need to replace the drive or perform some maintenance or repair of this drive that is more serious than CHKDSK can provide? Or should I replace the drive? The drive repair (which I have performed 3 times, now) has failed to correct the original problem.
Also, it looks to me like a BSOD is displayed for a split-second before reboot (at least there is a flash of blue). I entered the BIOS and turned off 'Halt on Error' feature, but this has not allowed me to see the screen. Any thoughts?
More generally, can anyone explain why this would happen? It would make me a smarter technician and I (and my clients) would be grateful for that.
Thanks to All for the attention you put into reading and responding to this.