Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Checkdisk


  • Please log in to reply

#1
Mohit Daksh

Mohit Daksh

    Member

  • Member
  • PipPipPip
  • 217 posts
From 2-3 days my computer is starting to act a little weird although I don't suspect any virus or other malware.
Whenever I boot it asks me to scan both the partitions using the check disk utility even though I shut down the computer properly.
  • 0

Advertisements


#2
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Click Start, then Run, type cmd, and click "Ok". At the prompt in the "Ok". At the prompt in the command window that opens, type fsutil dirty query D: and press "Enter
Does the result of this indicate the drive is "Dirty"?


  • If you have Spyware Doctor installed, uninstall it.
  • If you have ZoneAlarm installed, open it, click the "Overview" tab, then select "Preferences", and UNcheck the "Protect ZA Client" check box.
Click Start, then Run, type cmd in the Open box and click "Ok". At the prompt in the Command window, type the following commands, pressing "Enter" after each one:


  • chkntfs /d ..... (This will reset autocheck options to default...will come back invalid on some installations)
  • chkntfs /c D: ..... (This will allow checking the specified drive )
  • chkntfs /x D: ..... (The x switch tells Windows to NOT check the specified drive on the next boot)
At this point, restart your computer, it will not do a chkdsk and will boot directly to Windows.

This next step is important as this is where the Dirty Bit will be unset.



Click Start, then Run, type cmd in the Open box and click "Ok". At the command prompt, type the following, pressing "Enter" after each one: (Again, note the spaces.)
  • chkdsk /f /r D: ..... (To manually run a full chkdsk operation on the specified drive)
  • Y ..... (To accept having it run on the next boot)
This should take you through 5 stages of the scan and will unset the Dirty Bit. Be patient...this is a very thorough check and will take quite a while.

Finally, when the chkdsk operation has completed, type fsutil dirty query D:, press "Enter", and Windows will confirm that the Dirty Bit is not set on that drive.

Reboot again and see if chkdsk still runs on startup.
  • 0

#3
Mohit Daksh

Mohit Daksh

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 217 posts
Thank you rshaffer61 :)

Yes it shows that the drive is dirty and I'll follow the steps you told me to and tell you the results soon..
Thanks once again :)
  • 0

#4
Mohit Daksh

Mohit Daksh

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 217 posts
Thank a lot rshaffer61!! My computer is running perfectly fine now :)

If you have a little time can you please explain a bit about this dirty bit thing?
  • 0

#5
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
I hope this explains it as I am supplying two different explanations for it.

• A Dirty Bit or invalid Bit is a bit of Virtual Memory Page or a bit of Memory Cache that has been modified by the CPU but did not or has not been written back to storage yet.
• This will cause a error to occur in that bit which in turn causes the chkdsk to run on every boot.
• This Dirty Bit or Invalid Bit is caused by changes being made by chkdsk /f operation and the changes were not made before the system was shut down.
Chkdsk will run in a continued state of a loop till the Invalid Bit is repaired or cleaned






• A piece of Memory that has not corrected itself after being checked
• It fails to do this when it has not been able to write to storage before the system was turned off.
• This results in a basically corrupted memory hole that gets stuck in a constant loop till it is corrected.

Edited by rshaffer61, 23 June 2009 - 07:34 AM.

  • 0

#6
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
BTW I just wanted to say:

Congratulations. :) for a successful resolution for your issue. I am happy everything has been worked out for you. With that being said I am happy to say:


You are very welcome. I'm glad we could help and please let us know how everything works out for you.
If there is anything else we can do to help please feel free to ask. I appreciate that you allowed me to assist you with your issue and for your patience. Thank you for choosing GeeksToGo for help. :) :)
This issue now appears to be resolved.


If other members are reading this and have a similar problem please begin a New Topic and someone will assist you as soon as possible


If you are happy with the service I provided, please consider making a donation to GeeksToGo to support the Free Technical Support offered. Go HERE to make a donation.
  • 0

#7
Mohit Daksh

Mohit Daksh

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 217 posts
Thanks again rshaffer61.. I got it.. :)

I am a student right now with zero earnings so I cannot donate right now but I assure you I will definitely do it the day I have a paypal account.. I am very thankful to GTG for helping me and many others every time we have a problem.. You guys just rock!! :)

Edited by Mohit Daksh, 21 June 2009 - 11:16 PM.

  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP