none
Windows 7 and chkdsk on boot

    Question

  • It appears that the CHKDSK wants to run almost every time I reboot my computers with Windows 7. It happens on desktops and laptops as well.
    Any help?
    Udi Burg www.unisfair.com
    Wednesday, October 07, 2009 6:14 PM

Answers

  • This sometimes worked on XP and should also work on Vista or Windows 7.

    Click on Start then Run , type cmd and press Enter . Next type fsutil dirty query x: where x: is your boot drive. This queries the drive, and more than likely it will tell you that it is dirty.

    Next, type chkntfs /x c: . The X tells Windows to NOT check that particular drive on the next reboot. Now manually reboot your computer, it should not do a chkdsk and should take you directly to normal Windows login.

    Once Windows has fully loaded, bring up another Command Prompt and enter chkdsk c: /r . Reply Y when asked if you want this to happen on the next boot. This should take you through 5 stages of the chkdsk scan and will unset that dirty bit. This can take an hour or more depending on the size of your hard drive, be patient and let it complete.

    Once booted back to Windows, open another Command Prompt and query the dirty bit again by entering fsutil dirty query c: and Windows will confirm that the dirty bit is not set on that drive.

    Above from Experts Exchange

    Thursday, October 08, 2009 12:42 AM

All replies

  • You could well be experiencing a 'drive consistency' problem.  If so, then I'm afraid the best course of action is to first completely wipe the drive and start over.  Delete all partitions and then create new ones and start over with a fresh install.  If the problems still continue then it's best to replace the drive.

    Manufacturer diagnostic tools are also useful to run a better 'check' on the drive than Windows provides.


    If the behaviour is indeed happening as I've described here then it's happening because Windows is perceiving the drive as having bad sectors.  Those may or may not be genuine.  In some circumstances a corrupted install can cause Windows to perceive a reliable drive as 'bad'.  It's best to thoroughly check before assuming that the drive actually is an unreliable one.
    Wednesday, October 07, 2009 11:19 PM
  • This sometimes worked on XP and should also work on Vista or Windows 7.

    Click on Start then Run , type cmd and press Enter . Next type fsutil dirty query x: where x: is your boot drive. This queries the drive, and more than likely it will tell you that it is dirty.

    Next, type chkntfs /x c: . The X tells Windows to NOT check that particular drive on the next reboot. Now manually reboot your computer, it should not do a chkdsk and should take you directly to normal Windows login.

    Once Windows has fully loaded, bring up another Command Prompt and enter chkdsk c: /r . Reply Y when asked if you want this to happen on the next boot. This should take you through 5 stages of the chkdsk scan and will unset that dirty bit. This can take an hour or more depending on the size of your hard drive, be patient and let it complete.

    Once booted back to Windows, open another Command Prompt and query the dirty bit again by entering fsutil dirty query c: and Windows will confirm that the dirty bit is not set on that drive.

    Above from Experts Exchange

    Thursday, October 08, 2009 12:42 AM
  • Steps provided by Ztruker is worth to have a test. Before that, we can first test to run a Check Disk in Safe Mode. After that, reboot the computer to see if issue still exists.

     

    • Proposed as answer by Benelli750sei Wednesday, February 19, 2014 1:37 PM
    Thursday, October 08, 2009 1:47 AM
  • It appears that the CHKDSK wants to run almost every time I reboot my computers with Windows 7. It happens on desktops and laptops as well.
    Any help?
    Udi Burg www.unisfair.com

    I have a similar issue but it happens after Event Error ID 55 is logged (NTFS). Can you check your logs and see if you have this ominous error occur as well?
    My subesquent CHKDSK finds no! erros(s).
    Monday, November 09, 2009 8:53 PM
  • Steps provided by Ztruker is worth to have a test. Before that, we can first test to run a Check Disk in Safe Mode. After that, reboot the computer to see if issue still exists.

     


    How do you run a CHKDSK in Safe mode? You invoke a chkdsk c: (Systemdrive) which runs before Win starts on it. I fail to understand this suggestion.
    Monday, November 09, 2009 8:56 PM
  • get into Safe Mode, input CMD in Search, run it as Administrator. Type: CHKDSK C: /f /r
    Tuesday, November 10, 2009 6:27 AM
  • get into Safe Mode, input CMD in Search, run it as Administrator. Type: CHKDSK C: /f /r

    I still don't get this hocus pocus: It will still only execute CHKDSK C: /f /r on reboot/restart the same.
    Tuesday, November 10, 2009 10:32 AM
  • Yes, that's true
    - Bill
    Friday, November 13, 2009 3:02 PM
  • This issue can be caused by the same problem as described in the http://tinyurl.com/w7corrupt post. The program in that post clearly reproduces this issue without causing real disk problems.
    • Proposed as answer by Bert Huijben Monday, March 01, 2010 3:43 PM
    Friday, February 05, 2010 11:11 PM
  • I followed all your instructions carefully. It took me more than one hour to complete (with a hard drive of 220 GB) and my problem is solved! Thank you a lot!!!
    Thursday, April 29, 2010 6:16 PM
  • This worked for me on a Win 7 machine - thanks :)
    Thursday, May 06, 2010 1:18 AM
  • Ztruker

    I am a relative novice with Windows 7 and have just experienced this problem, but when I run cmd and fsutil dirty query x: I get a message saying I need administrator privileges.  Can you tell me how I can make that happen either before I enter the cmd prompt or after?

    Sorry to be dense

    Monday, June 07, 2010 9:18 AM
  • I'm having the same problem with an Asus netbook running Windows seven, however, when I run the dirty query, I'm told that c: is NOT dirty.

    Chkdsk doesn't run on every boot, but often enough for it to be really annoying.  Every time I let it run the check, no errors are found.

    Wednesday, June 09, 2010 3:20 PM
  • Thanks Ztruker... worked like a charm for my win 7 - 64 bit installation!
    Sunday, June 20, 2010 8:03 PM
  • Hi alittleoldman,

    If you click start then type cmd in the search box. Wait for cmd to appear under "Programs" and right click the icon, selecting "Run as administrator"

    Best, 


    Randall Kent | The Sevaa Group | www.sevaa.com
    Wednesday, June 30, 2010 11:58 AM
  • This worked for me. Thanks for the help. I was getting really annoyed.
    Thursday, July 29, 2010 3:41 PM
  • I'm having the same problem with an Asus netbook running Windows seven, however, when I run the dirty query, I'm told that c: is NOT dirty.

    Chkdsk doesn't run on every boot, but often enough for it to be really annoying.  Every time I let it run the check, no errors are found.

    Exactly the same situation here.

    I have recently enlarged my system partition to fill out the entire drive. Since then I have had the same problem, no errors, but still chkdsk on most boots.
    Monday, August 16, 2010 6:18 PM
  • Ztruker

    I am a relative novice with Windows 7 and have just experienced this problem, but when I run cmd and fsutil dirty query x: I get a message saying I need administrator privileges.  Can you tell me how I can make that happen either before I enter the cmd prompt or after?

    Sorry to be dense


    You will need to go to C:\WINDOWS\System32 and then, right click on CMD.exe and hit: Run as administrator. This will do the trick.
    Wednesday, August 18, 2010 7:55 PM
  • This sometimes worked on XP and should also work on Vista or Windows 7.

    Click on Start then Run , type cmd and press Enter . Next type fsutil dirty query x: where x: is your boot drive. This queries the drive, and more than likely it will tell you that it is dirty.

    Next, type chkntfs /x c: . The X tells Windows to NOT check that particular drive on the next reboot. Now manually reboot your computer, it should not do a chkdsk and should take you directly to normal Windows login.

    Once Windows has fully loaded, bring up another Command Prompt and enter chkdsk c: /r . Reply Y when asked if you want this to happen on the next boot. This should take you through 5 stages of the chkdsk scan and will unset that dirty bit. This can take an hour or more depending on the size of your hard drive, be patient and let it complete.

    Once booted back to Windows, open another Command Prompt and query the dirty bit again by entering fsutil dirty query c: and Windows will confirm that the dirty bit is not set on that drive.

    Above from Experts Exchange


    Hi, I have the same issue as described below but my issue is a little more weirdo than that! I just imaged my HP Z200 with Windows 7 Pro x64. It's a brand new HDD also (500go Seagate) and as soon as I'm finished imaging my HP, I can log in the computer, join it to the domain... etc! I reboot it on first time, chkdsk starts on startup for no reason! Then, it's doing its stuff and then reboot. At reboot, it loops on startup repair for ever and I can't do anything. I tried Bootrec.exe /all_switches_without_luck!

    I've done some changes to my PC to check for any hardware problem.

    - I changed the HDD (Samsung 500go for a Seagate 500go) - No luck

    - Swapped the Video card (nVidia Quadro 580FX for a Radeon EAH4350)

    I suspect the mobo to be in problem, maybe the HDD controller...

    Is anybody have seen this before? Thanks so much!

    David.

    Thursday, August 19, 2010 2:48 PM
  • I used the first solution and it worked, but now I get BSODs that restart my computer. They have happened when I press the back button in my browser, when I link two items together in Yahoo Pipes, or when I'm away from the computer entirely. Should I try resetting the dirty bit? How would I do that?
    Tuesday, September 07, 2010 8:40 PM
  • After having done all of that, including doing plain old chkdsk c:  on safe mode, it continues to send me to the same error screen, insisting that I do a system restore because there is a recently installed program preventing my chkdsk.  Thing is, I can't do a system restore because it won't let me do that either.

    I can't format it either.  It allows me to do all the preliminaries, but it won't erase the HP drive completely as  when I reboot, I return to my system as if none of my formatting had taken place.

    Also, I've run the Malwarebytes, but that yields nothing and two other spyware programs won't update their files to the computer either.

    All of this seemed to take place when I downloaded Firefox a few months ago.  I didn't really notice it much until i wanted to download Skype, which download works, only I can't communicate from the platform to the network on the computer when I enter my password. So, I'm thinking that these communications problems and my problems logging on with software based on my computer, or receiving updates for my windows and firefox are all related.

    Please advise.

     

    Friday, December 24, 2010 10:15 PM
  • Umm... As I read it, doing the  chkntfs /x c: disables chkdsk from *ever* running again at boot. Is this wise?
    Keith De La Rue
    Friday, January 21, 2011 2:23 AM
  • This sometimes worked on XP and should also work on Vista or Windows 7.

    Click on Start then Run , type cmd and press Enter . Next type fsutil dirty query x: where x: is your boot drive. This queries the drive, and more than likely it will tell you that it is dirty.

    Next, type chkntfs /x c: . The X tells Windows to NOT check that particular drive on the next reboot. Now manually reboot your computer, it should not do a chkdsk and should take you directly to normal Windows login.

    Once Windows has fully loaded, bring up another Command Prompt and enter chkdsk c: /r . Reply Y when asked if you want this to happen on the next boot. This should take you through 5 stages of the chkdsk scan and will unset that dirty bit. This can take an hour or more depending on the size of your hard drive, be patient and let it complete.

    Once booted back to Windows, open another Command Prompt and query the dirty bit again by entering fsutil dirty query c: and Windows will confirm that the dirty bit is not set on that drive.

    Above from Experts Exchange

    This worked, thank you.

    Monday, January 24, 2011 10:11 PM
  • Sorry for my bad english, its not my first language anyway.

    I have the same problem, everytime i reboot CHKDSK appears.

    I was reading your comment above really carefully, followed it step by step, CHKDSK is no longer there on the reboot but when i get to the stage where you said to bring up another Command Prompt and enter chdsk c: /r as soon as i press enter  on the cmd window its says that the drive cannot be locker or something i cant remember and then i have a blue screen saying that the computer crashed then its loading some files and reboot its self and then it will ask me if i want to run it on safemode or normally.

    Just bought my gaming rig 2 months ago and i had to took it back twice already because it was crashed almost everytime after that CHKDSK. I do not understand what could be the problem and the other thing is that my computer freezes for like 30 seconds in every 10 minutes. I was thinking about to buy another hard drive but if i can fix it by this way i would not waste any money.

    Im really hoping that you can give me some advice. By the way i have Windows 7 Professional which was installed after they fixed my computer.

    Thank You

     

    Friday, January 28, 2011 7:13 PM
  • For almost a year I suffered from this problem.   Included was Event Error ID 55 is logged (NTFS) in the event logs.   On occasion, a day pass without the event.  Typically there would be multiple entries on a single day.   I was confident it was not a bad drive because it was new.  I attributed my problem from using EASEUS Disk Copy  to migrate to a larger disk drive.   I was beginning to loose the faith in Windows 7

    I followed the steps as outlined  - CMD , run it as Administrator. Type: CHKDSK C: /f /r 

    Reboot and let it complete.      I did this several times but it did not resolve the problem.   Last week I found this forum.   I then decided to try it in "safe mode"  - nothing to loose right ?!?!

    The computer started in safe mode,   It appeared to stop loading the necessary files for safe mode, but I could hear the disk drive working.  Kinda funny, it even stopped displaying the sys drivers on MUP.SYS. 

    To my astonishment, the computer had restarted in normal mode, and since I have not had the problem re-occur.   It may be my hopeful attitude, but the computer seems to boot much faster now !  

    I don't know what happened, but I do know the problem has ceased.    I Agree with WIN7INE whats safe mode got to do with it when chkdsk is executing before windows starts. 

    I have to give a thanks to the suggestion in safe mode. 

     

     

    Saturday, March 19, 2011 12:44 PM
  • There is no Run to click on Windows 7 start menu, that I can see.  I can type run into search, then click run, then type cmd and press enter.

     

     fsutil dirty query x:  requires system administrator access.  It's my pc, I am prompted and can give get access with other commands like chkdsk/f but not with this one. 

     

    Why am I typing chkntfs /x c: next and go through another reboot, if I'm just going to bring up another Command Prompt and enter chkdsk c: /r  ?

     

    Not very good instructions for this windows 7 user.  =( 

     



    Monday, March 28, 2011 8:37 PM
  • Thanx a lot!!!! it worked.. @ win xp..!!
    Sunday, May 08, 2011 9:11 PM
  • Thanks for that. The safe mode did the same thing for my computer.
    Monday, July 11, 2011 4:38 PM
  • I have had the same issue and i tried the command prompt and it tells me not that its dirty, but i need admin privledges. Its my laptop and i did set the admin privledges to my account/the only account on the laptop. I am so frustrated! I just bought this laptop and its acting up :( please help :)
    Sunday, August 07, 2011 5:29 AM
  • I have had the same issue and i tried the command prompt and it tells me not that its dirty, but i need admin privledges. Its my laptop and i did set the admin privledges to my account/the only account on the laptop. I am so frustrated! I just bought this laptop and its acting up :( please help :)
    When you go to start up Command Prompt or "CMD.exe" Right click it and go run as administrator (If you're in windows 7 that is)
    Tuesday, September 13, 2011 9:11 AM
  • Hi guys

    If you have problem using chkdsk why not try and download a hard drive utility specific to your drive direct from the drive maker like ( SeaTools for Windows ) or maxblast for maxtor,

    these utilities sometimes work when windows crap doesn't im actually doing one now and windows wouldn't do it plus it takes the pain out of trying to direct chkdsk to the drive you wanna do as im sure your aware.

    these are worth a try that is providing you have a os up and running, that is!.

    regards

    CS

    Wednesday, September 21, 2011 7:39 PM
  • RickeyV,

     

    I don't know if you have looked under "Start > All Programs > Accessories>"  but under here you will find the CMD.exe, you can Right Click on this and select "Run As Administrator" then the commands work =)

     

    -LMAOIMH

    Thursday, October 06, 2011 4:24 PM
  • I am having the same issue with the chkdsk problem; however, mine is a little bit different.  I cannot get into my Windows at all and cannot get into Safe Mode to attempt to follow the instructions to fix it.  Even if I hit a key to cancel the chkdsk, I keep looping around.  It does ask me if I want Windows 7 or a previous version (XP) and I choose Windows 7...I shouldn't even have the option as my previous version of XP became corrupted through some viruses and someone installed Windows 7 instead.  I had a bunch of errors about some files in Windows 7 and then when I started up the next time, this is all happening!!!  I'm stuck and cannot get on my laptop (work computer) at all right now.
    Sunday, October 09, 2011 1:43 AM
  • I have the same problem now, how did you get it solved?
    Monday, February 06, 2012 9:15 PM
  • Ztruker's advice really helps! Thanks!
    • Edited by notricky Sunday, May 06, 2012 9:21 AM
    Sunday, May 06, 2012 9:18 AM
  • I'm having the same problem with an Asus netbook running Windows seven, however, when I run the dirty query, I'm told that c: is NOT dirty.

    Chkdsk doesn't run on every boot, but often enough for it to be really annoying.  Every time I let it run the check, no errors are found.


    This is exactly my situation as well (except I'm using a desktop), Any thoughts?
    Tuesday, August 07, 2012 5:22 PM
  • This Happened To Me Everytime, But Then I Found Out That My HardDrive Was Corrupted :(

    Usayd. Sea

    Wednesday, February 27, 2013 9:38 AM
  • In the past 3 days I have had 4 systems start displaying this behaviour. 

    They are all windows 7 Pro (version 6.1 build 7601) sp1. Various makes and models (HP, Dell, & Lenovo). Update is as of April 12/2013.

    The fix works but what's triggering it?

    We have another 50 PCs that I don't want to have to fix one at a time!

    Thanks

    Garry

    Wednesday, April 17, 2013 4:47 PM
  • Hi Garry Dodman - how did you fix it?  We have this problems on all Windows 7 Pro computers.  It started happening after April 12, 2013.


    garyli

    Wednesday, April 17, 2013 6:51 PM
  • Like Garry Dodman and Gary Li I have got this problem with a Windows 7 Pro laptop, also starting on 12th April 2013.

    Does anybody have any idea as to cause?

    Thanks

    Donald

    Thursday, April 18, 2013 4:00 PM
  • Guys it was Windows update problem dated 10th April 2013.

    uninstalling KB2823324 should get it fix.

    some how it also related to KAV & Trend Micr0 machines.

    Just follows the below discussion for more details:

    http://social.technet.microsoft.com/Forums/en-US/w7itprogeneral/thread/2773e5f7-6852-4ce7-ba46-37dd125ea595

    http://social.technet.microsoft.com/Forums/en-US/w7itprogeneral/thread/245c2696-59cb-4a05-94fe-ff763867f677

    Thursday, April 18, 2013 5:23 PM
  • Today Microsoft released update KB2840149 to replace KB2823324, which was originally made available through MS13-036.  Previously KB2823324 was removed from distribution for reasons explained in KB2839011

    Customers who have automatic updates enabled will not need to take any further actions to get the new update. For those manually updating, we encourage you to apply this update at your earliest convenience. 

    Wednesday, April 24, 2013 6:29 AM
  •  fsutil dirty query x:  requires system administrator access.  It's my pc, I am prompted and can give get access with other commands like chkdsk/f but not with this one.

    Why am I typing chkntfs /x c: next and go through another reboot, if I'm just going to bring up another Command Prompt and enter chkdsk c: /r  ?

    Not very good instructions for this windows 7 user.  =(

    You must run the Command Prompt as an Administrator. Click > Start All Programs > Accessories > System Tools > Right click Command Prompt and then click Run as Administrator.

    Sunday, February 16, 2014 5:49 AM