Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I started up my Windows XP box last weekend after it had been off for quiet a while, at least a few months. At first, when I started it up I received a blue screen with no message, and it restarted. I then selected Last known good configuration, and XP started booting up. Awesome! But wait, it tells me that it has to run a CHKDSK...

I can wait. So I do, it goes through the CHKDSK, but then it restarts, and what does it ask for on the next restart? Another CHKDSK. So I try to skip the CHKDSK this time, and what happens? I cannot press a key to skip the CHKDSK. So right now I'm stuck in an infinite loop of CHKDSKs and unable to get into XP. I've tried all the variations of Safe Mode, disabling restart on system failure (maybe I was missing a blue screen after the CHKDSK...). But no, nothing.

I was able to get into the recovery console, but honestly I have no idea what to do now that I'm there. Anyone have any ideas?

share|improve this question
There is already a answer located on this very website that goes into detail on how to disable the authomatic chkdsk on a volume. – Ramhound Oct 4 '13 at 14:55
Hold on, I forgot a very valuable piece of information. I cannot press a key to skip the CHKDSK. – NobleUplift Oct 4 '13 at 14:58
My comment remains the same. You have to modify a registry key that is causing this. Of course the drive itself is failing. Windows knows this command needs to be ran. You should replace the drive in question.… – Ramhound Oct 4 '13 at 15:02
@NobleUplift is CHKDSK repairing files? If so this can be expected behavior as Windows may need to restart to continue the CHKDSK, How many times has this happened? – TheXed Oct 4 '13 at 15:11
I made the mistake of using Intel Fake RAID to create a RAID-1 array. If I do have to reinstall, no way I'm doing that again. Also, the CHKDSK comes back 100% clean, just as every one before it has. – NobleUplift Oct 4 '13 at 15:15

Because you say you had a bluescreen i would recommend using the hirens cd. Use the bluescreenviewer because maybe there is a hardware error. If there is not i would back-up all the files you need and install windows again.

I hope you had something to this.


share|improve this answer
I'll try it out next chance I get. You should consider registering so that you keep your reputation if I upvote/accept your answer. – NobleUplift Oct 4 '13 at 15:01
He said there was no blue screen... – TheXed Oct 4 '13 at 15:08
@TheX - "I received a blue screen ..." granted its not clear if the author means something other than a BSoD – Ramhound Oct 4 '13 at 15:16
I had one blue screen to begin with, but I have not received a blue screen since this infinite loop began. – NobleUplift Oct 4 '13 at 15:17
@NobleUplift - Your system actually is crashing thus the infinite reboot. Your hdd needs to be replaced. This infinite reboot problem was likely caused by a corrupt system file or required drive being deleted by chkdsk. – Ramhound Oct 4 '13 at 15:26
up vote 0 down vote accepted

I tried a few hacks to stop Windows from doing this, such as disabling CHKDSK at boot and renaming chkdsk.exe to chkdsk1.exe, or just replacing chkdsk.exe with an empty, read-only file. Of course, none of these worked.

The problem was the way that Windows read my RAID array at boot. I had an issue with the installation of the RAID driver, and somehow the RAID signature on the hard drives was triggering the CHKDSK on every boot. These Intel chipsets are such a hassle they aren't worth using in the slightest.

When I deleted the RAID array, I was able to boot into Windows XP no problem.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .