• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Can't stop CHKDSK from running when I boot

Chhhh

Limp Gawd
Joined
Sep 25, 2000
Messages
444
Everytime I reboot, CHKDSK wants to run on my D drive. The drive is a partition on a SATA RAID 1 array.

Even though it didn't find any errors the last time it ran, it still wants to run again. Is there any way to check why this is happening? If I move everything off the drive, and just format it, would that stop it?


Thanks
 
CHKDSK Runs Uncontrollably Every Boot Up

Check the "Check Disk - Disk Checking Runs Upon Boot" entry in the Windows XP From A to Z section of kellys-korner-xp.com for tips:

Check Disk runs on every boot: Note - I have seen this happen when Windows File Protection has either been disabled or not allowed to run upon canceling the bootup Check Disk.

Suggestions and Checkpoints:

Go to Start/Run/CMD and type in: fsutil dirty query c:
(Modify the drive letter accordingly)

If it comes back as dirty, it hasn't cleared. For more information go to Start/Run/CMD and type in: CHKNTFS /?

Option: From a command prompt type chkntfs /D and then reboot, a chkdsk should run but not again on next boot.

This edit does not work for all users, circumstances depending:

Disable or Enable CheckDisk Upon Boot (Line 82)
http://www.kellys-korner-xp.com/xp_tweaks.htm

To use the Regedit: Save the REG File to your hard disk. Double click it and answer yes to the import prompt. REG files can be viewed in Notepad by right clicking on the file and selecting Edit.

Chkdsk Runs Each Time That You Start Computer
http://support.microsoft.com/support/kb/articles/q316/5/06.asp

Checkpoint:

Go to Start/Run/Regedit and navigate to this key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

Highlight the Winlogon file.

In the list look for "SFCScan", this should be set to (0) if it is set to (1) the scan will happen at every boot.

Go to Start/Run/Regedit and navigate to this key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager

Look for the REG_MULTI_SZ value with the following name: BootExecute. This value contains commands that will be executed at startup. The default value is: autocheck autochk *

After scheduling one or more chkdsks, the entry will contain one or more autochk lines. Delete each of these lines and put the default one in place.

If you always want a check to be performed at startup, change the value to: autocheck autochk /f *

If you don't want any checks to be performed, delete all autocheck entries.

Last checkpoint: Modify as needed:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\MyComputer\cleanuppath
Registry entry should read: %SystemRoot%\system32\cleanmgr.exe /D %c

How to schedule a CHKDSK on every boot
Chkdsk Runs Each Time That You Start Computer After Upgrade to Windows XP

Scandisk after a Bad Shutdown - Go to Start/Run/CMD and type in: CHKNTFS/T:4
Where 4 is the amount of waiting time.
 
i tried running the fsutil dirty query d:" and it told me that the drive was ditry, even though chkdsk just ran 30 seconds before when i booted and said it was fine. i tried the chkntfs /d and that didnt work either. all the registry entries are they are suppposed to be aswell.

hmm, i dont know what else to try
 
Maybe your drive is getting ready to croak. Have you checked the S.M.A.R.T. values?
 
Met-AL said:
Maybe your drive is getting ready to croak. Have you checked the S.M.A.R.T. values?


The drives are only about a month old, and theRAID utility saiys the SMART values are OK.
 
On a side note, are you overclocking the FSB on a chipset that doesn't lock the PCI bus?

If so, that might be the source of your corruption. You run a IDE controller out of spec too far, you can end up with corrupted disks. I have no idea if this pertains to SATA controllers though.
 
Back
Top