CHKDSK always starting up for no reason.

[catattack]

Hey guys... I did scheduled ONE chkdsk /f a while ago like 2 or 3 days and, every time I turn on my computer ( when it was shut down allready), it ALWAYS does the CHKDSK /f or the ya know.... Checking disk for errors thing. Well, i'm not stupid and I know that shutting down the computer Improperly does this, but I shut down by going to start and shut down ever single time... Also, when I try to defrag my one hard drive, it says it cant be defraged because a CHKDSK /F has allready been scheduled, when it hasnt. Whats wrong here?

[Jonny M]

Maybe schedule another and see if it clears? Is there anything about it in task scheduler?

[catattack]

I have done that before and nope I allready checked and its not in there...

[catattack]

Its only doing it on ONE hard drive, and everytime I let it happend or just restart it keeps bringing it up!!! Anyone know a solution?

[catattack]

I have scheduled both of my drives to have a check disk or whatever, and it did my first (operating system) one and it just said... A check disk was scheduled for this drive... Then it went to the logo, and little bit later it went into another checkdisk, but this one, this is the problem drive. This one says "One of your disk needs to be checked for consistency". What does that mean?

[directhex]

i thought there was a windowsupdate to fix it doing this every boot - or was it something else every boot? i forget...

[catattack]

Anyone know about this? Anyone?!

[Steve]

First up, boot off your XP CD (presuming you have XP here) and use the recovery console. Run chkdsk from there. I've found that version sometimes picks up and fixes problems the other doesn't.

If that doesn't work, you can fire up the command prompt in windows and run (presuming C is the drive that's being checked) :-

chkntfs /x C:

Basically, chkntfs looks to see if the "dirty bit" is set on that partition/drive. If it is, there are suspected errors on the drive and it needs checking. Sometimes it doesn't work properly though. Running the /x switch on it prevents it from running an autochk on that drive at system boot.