Iam having the same problem, with two Windows 7 machines failing to start up at the same time. I had a power failure, and found that the many "normal" troubleshooting cases I tried, including a fresh Windows 7 reinstall, all failed. All of the machines
uses SATA drives, one of the machines booted from an SSD drive. I've experienced many many power failures and never had a problem the CHKDSK didn't fix, but in this case even a fresh install from the Windows 7 install disk would not fix the problem. I reset
the CMOS, removed the battery from my motherboard, tried every repair option I could find. Eventually I disconnected all hard drives, bought a new drive and put that in, and installed Windows 7 on it. But when trying to reconnect the old drives, one at a
time, I could not even reformat the SSD drive, until I took it to my laptop (a third machine, it's looking good at 96% complete). The fact that the same hardware has two different results depending on which Win 7 machine I try to use it from tells me it's
a problem with the original machine. Yet I reset the BIOS settings, removed the battery, etc. I don't get it.
The way this happened to two of my machines at home, and possibly a third at work (I'll investigate tomorrow) all at the same time, combined with the user above who reported it happening to 12 machines, tells me this is something other than a drive failure
problem. It's not hardware, unless a software update problem fried these drives. I believe all of the drives were SATA drives, so perhaps there is a bug in a Windows Update SATA driver or something, so that they were all put into some form of error state
at the same time.
At any rate, I found the message from Malkeleah to be thin on reading
the problem and thick on abusing the poster who was trying to be helpful. I would report him for posting a message that offered no help but only insults, but it seems he is the moderator. I agree that the long reply was not helpful because it was
a shotgun reply trying to hit a target somewhere, but at least he was trying to help, and none of the insults help resolve the issue, which seems to me to be two-fold:
- some update, perhaps SATA driver, results in an unbootable hard drive.
- crcdisk.sys cannot deal with this situation and hangs.
If the second problem was at least detected and resolved, perhaps it could report whatever the condition was that would have otherwise put crcdisk.sys in that state, and that would provide a clue here.
Paul