chkdsk loop hell (XP)

[atlanticjim]

chkdsk loop hell (XP) SOLVED (sort of)

Ok, need help again. (damn. . twice in one day).

Have a client's machine that was stuck in a winxp reboot loop for a few days then just crashed to chkdsk loop with many errors. I discovered a bad ram stick and removed it. Now I am in chkdsk reboot hell. No errors found but wont move to the xp load screen.

Is there some registry setting that I can use to stop this maddness.

 

[iisjman07]

The chkdsk that XP runs isn't a full chkdsk scan. I'd run chkdsk with the /r variable from a boot cd

 

[atlanticjim]

The chkdsk that XP runs isn't a full chkdsk scan. I'd run chkdsk with the /r variable from a boot cd

I will try that, I ran disk check from hiren's (forget which one) and it completed without error. I suspect that if I run it from a PE environment it will not change the registry value to prevent it on reboot from the hd.

 

[Tweak]

There is a registry fix that allows the volume to no longer be flagged as "dirty", I cannot recall the exact steps involved but this thread offers multiple solutions.

http://help.lockergnome.com/general/Chkdsk-Volume-Dirty-Help--ftopict30855.html

or Google results...

http://www.google.com/search?hl=en&source=hp&q=dirty+volume+chkdsk&aq=2&oq=dirty+volume&aqi=g6

Sorry i cannot recall specific answer on this occasion.

 

[atlanticjim]

There is a registry fix that allows the volume to no longer be flagged as "dirty", I cannot recall the exact steps involved but this thread offers multiple solutions.

http://help.lockergnome.com/general/Chkdsk-Volume-Dirty-Help--ftopict30855.html

or Google results...

http://www.google.com/search?hl=en&source=hp&q=dirty+volume+chkdsk&aq=2&oq=dirty+volume&aqi=g6

Sorry i cannot recall specific answer on this occasion.

Thanks Tweak, the first entry has the reg entries that I need.
I will update with success/failure.

 

[atlanticjim]

Solved. . sort of.

Thanks for the help.

I found a solution although I consider it a work around to prevent chkdsk from checking the c: hd.

It did work to get windows to load. Now I am going about my regular clean up and tweaks.

Here is the quote from www.raymond.cc

The chkntfs utility works by modifying the BootExcecute value in the system registry. The BootExecute value is located in the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CURRENTCONTROLSET\CONTROL\Session Manager

The default value is for BootExecute is autocheck autochk *. When you use the /x switch, it will add a /k parameter prior to the asterisk. The /k parameter excludes volumes from being checked for the presence of a dirty bit.

For example, I run the command chkntfs /x c: in command prompt. This command would modify this registry entry to autocheck autochk /k:c *

There are some experts believe that it is better not to disable CHKDSK from scanning your hard drive. But as for me, I don’t want CHKDSK to scan my hard drive because if it finds anything bad, it will change the file to File00001.CHK. When that happens, I’ll have to use some third party tools to recognize and recover the CHK file.

 

[Tweak]

Guess sort of is better than not at all.