chkdsk = BSOD

[bevross]

I had a sort of weird problem: scheduled a "chkdsk" via Windows, rebooted, system went through the entire process, not finding errors & then booted back into Windows. At this point, I couldn't run Windows Explorer: clicked on the icon, screen went black, then got the desktop again. Figured maybe another reboot would help but, on reboot, got the dreaded BSOD ("blue screen of death"). There was some error message but, unfortunately, I did not jot it down nor remember (too freaked). So, I turned the machine off via the power button. After that, everything's back to normal, no issues with anything.

I'll add that I ran Hitachi's disk checking program and everything checked out fine. Might also add that only 1 month ago the hard drive on my desktop totally crashed and, at the time, I was running -- chkdsk! Now I'm wondering if it's really wise to run chkdsk at all & perhaps I should just stick with the drive manufacturer's diagnostic programs? Anyone?

[s0larian]

The same happend for me. I ran chkdsk /F, and after the reboot chkdsk came up with a few minor errors (which where no errors at all after looking it up with google). But that was it, I wasn't able to boot into XP anymore. It ended always with BSOD. I thought the reason could have been my fully encrypted Harddisk (with Safeguard Easy 4.1), but it looks like others are also experiencing the same problem.

[bevross]

Well, I don't have my harddisk encrypted with anything but I was thinking the funky setup of the harddisk (with hidden recovery partition) may have something to do with it. Also, unlike you ("I wasn't able to boot into XP anymore"), after a power down, my machine started up & has been unproblematic. Did you have to reinstall Windows or something? By the way, my system's a 3 month old T42.

[s0larian]

yes, I had to reinstall XP. I was lucky to recover my data with Rescue and Recovery (parts of it) and the rest through a linux partition. I don't have the hidden HPA, so this was definetly not the reason that caused my crash.