volume is dirty?

Status
This thread has been Locked and is not open to further replies. Please start a New Thread if you're having a similar issue. View our Welcome Guide to learn how to use this site.

sambe

Thread Starter
Joined
Nov 7, 2005
Messages
8
After running a Autodesk 3D product my CPU crashed, dell tech support helped reset the system boot, but my machine is still slow and keeps running chkdsk on boot up, and says that the volume is dirty,,, please help!!
 
Joined
Jun 23, 2005
Messages
6
Sambe,

try this, hope it helps.

Go to Start- Run and type in cmd to open a Command window.

Type in chkntfs C: It should tell you if the dirty bit is set ("C: is dirty")

If it is, type in chkntfs /x C:

This will prevent chkdsk from scanning drive C: at startup.

To reset it to normal, again open a Command window, and type in chkntfs /d

regards

Zoned
 

JohnWill

Retired Moderator
Joined
Oct 19, 2002
Messages
106,425
I'm not sure setting the system to not check the drive is a long-term solution, it's better to find out why it keeps trying to run CHKDSK. Something is obviously corrupted for that behavior to continue through multiple boots, ignoring it won't fix it.
 
Joined
Dec 21, 2003
Messages
158
Found this hope it explains a bit more

what you're experiencing is what Windows refers to as "setting the dirty bit" and what you have to do is unset that bit. Every time Windows XP starts, autochk.exe is called by the kernel to scan all volumes to check if the volume dirty bit is set. If the dirty bit is set, autochk performs an immediate chkdsk /f on that volume. Chkdsk /f verifies file system integrity and attempts to fix any problems with the volume. It is usually caused by a hard shut down or a power loss during a read-right operation on that particular drive.

How do I fix it, you ask?

Well, that's easy. First click Start> Run> bring up a command prompt by typing in "CMD" and type " fsutil dirty query d: ". This queries the drive, and more than likely it will tell you that it is dirty. Next, type "CHKNTFS /X D:". The X tells Windows to NOT check that particular drive on the next reboot. At this time, manually reboot your computer, it should not do a Chkdsk and take you directly to Windows.

Once Windows has fully loaded, bring up another CMD prompt and type and now you want to do a Chkdsk manually by typing "Chkdsk /f /r d:". This should take you through 5 stages of the scan and will unset that dirty bit. Finally, type "fsutil dirty query d:" and Windows will confirm that the dirty bit is not set on that drive. Good luck!
 

JohnWill

Retired Moderator
Joined
Oct 19, 2002
Messages
106,425
Actually, you can't do a CHKDSK /F of the boot volume, which I believe is the issue here. That would be queued up for the next reboot, and we're in the same loop. :D
 
Joined
Jan 27, 2007
Messages
1
welshY said:
Found this hope it explains a bit more

what you're experiencing is what Windows refers to as "setting the dirty bit" and what you have to do is unset that bit. Every time Windows XP starts, autochk.exe is called by the kernel to scan all volumes to check if the volume dirty bit is set. If the dirty bit is set, autochk performs an immediate chkdsk /f on that volume. Chkdsk /f verifies file system integrity and attempts to fix any problems with the volume. It is usually caused by a hard shut down or a power loss during a read-right operation on that particular drive.

How do I fix it, you ask?

Well, that's easy. First click Start> Run> bring up a command prompt by typing in "CMD" and type " fsutil dirty query d: ". This queries the drive, and more than likely it will tell you that it is dirty. Next, type "CHKNTFS /X D:". The X tells Windows to NOT check that particular drive on the next reboot. At this time, manually reboot your computer, it should not do a Chkdsk and take you directly to Windows.

Once Windows has fully loaded, bring up another CMD prompt and type and now you want to do a Chkdsk manually by typing "Chkdsk /f /r d:". This should take you through 5 stages of the scan and will unset that dirty bit. Finally, type "fsutil dirty query d:" and Windows will confirm that the dirty bit is not set on that drive. Good luck!

I just completed the process outlined above and it seemed to work...thank you. Question I have is, do I need to reactivate the CHKNFTS check?
 

JohnWill

Retired Moderator
Joined
Oct 19, 2002
Messages
106,425
CHKNTFS /D restores it to default behavior.

CHKNTFS /? will show you a help screen of all the options.
 
Joined
Jul 9, 2007
Messages
2
Just a thank you note. There are quite a few web links for this problem, all of them tell you the cause but very few showed your simple solution which worked like a charm, so I'm now a new member!

Regards

Dolo
 
Status
This thread has been Locked and is not open to further replies. Please start a New Thread if you're having a similar issue. View our Welcome Guide to learn how to use this site.

Users Who Are Viewing This Thread (Users: 0, Guests: 1)

As Seen On
As Seen On...

Welcome to Tech Support Guy!

Are you looking for the solution to your computer problem? Join our site today to ask your question. This site is completely free -- paid for by advertisers and donations.

If you're not already familiar with forums, watch our Welcome Guide to get started.

Join over 807,865 other people just like you!

Latest posts

Members online

No members online now.
Top