Hello all,

I keep having a problem : When I start my pc Windows shows an error message, much like the checkdisk process.
Windows loads first, and when the XP logo disappears a blue screen comes up that says : "One or more drives has to be checked for consistency. Name = D: (BACKUP (yes that's the real name)). You have 10 seconds to abort. When it's finished, it finds no errors, but the next time I boot my pc it scans again.
I've tried a lot of things, like running a chkdisk process manually, but then it shows the same scanning process twice when my pc boots. D: is a partition, C and D are the same disk. I've tried removing the chkdisk program from my windows folder, but it keeps checking. My parents are too stupid to abort it, so they come to me to complain that it's too slow, and it annoys me a lot too.

Can someone please tell me how to stop this?

Is your PC shutting down correctly?
Perhaps something isn't getting set right in the registry upon a successful boot.

Yes, it shuts down correctly. How can I check if everything's going alright with the registry?

Go to a command prompt and type:


What does it say?

You can disable the startup check on that drive with:


I also suggest you do a full bad sector test on the disk.

Or you can try this:

Go to the command prompt and type:


If it indicates dirty, then run:


Check with the fsutil command again to see if it's fixed.

Thanks for the help, I really appreciate it. I have tried the first command : it showed a little window, similar to when you run a batch file, but it was gone within a second. The same thing happened to the 'dirty' command. I've also disabled the startup check, I'll try rebooting now.

It works! Thanks a lot!

Even though you've sorted the problem (with the very helpful post from arco), I just thought I'd chime in about the window disappearing within a second when you run commands. I presume what you're doing is going to Start --> Run and typing the command in there. What this'll do is open the CMD/DOS window, execute the command you enter and then close the window again. In order to keep the window open and see the output, you should go to Start --> Run and type in cmd instead. This will give you the window into which you input the commands that you were inputting into the Run dialogue. The window won't close this time so you'll have time to see the output.

Thanks amp, I was wondering already .

Glad you got it fixed.
As amp88 said you have to enter cmd in the run dialog to have the window stay open. I figured that went without saying, but I guess you don't come from the DOS generation.

I have issue with it being referred to as fixed. Disabling the startup check will ignore the symptom, it does nothing to solve it. The thorough disc check mentioned earler is still necessary I'd say.

As soon as I wrote that I wondered if there's a program running at shutdown that doesn't exit cleanly and makes the computer think there was a problem when there wasn't. That's going to be a bit harder to figure out.

Maybe the best thing is to ignore it and see if it goes away...

my m8 had exactly the same problem after he installed 1 game on his F: drive.
Since there wasnt any other software except few photos he moved the photos on another drivers uninstalled the game but he was still getting the same error.Checkdisk didnt help and it way very annoying at every boot.

We simply formated that drive again and the issue dissapeard.

Quote from IReallyHateBureaucracy :

I have issue with it being referred to as fixed. Disabling the startup check will ignore the symptom, it does nothing to solve it. The thorough disc check mentioned earler is still necessary I'd say.

As soon as I wrote that I wondered if there's a program running at shutdown that doesn't exit cleanly and makes the computer think there was a problem when there wasn't. That's going to be a bit harder to figure out.

Maybe the best thing is to ignore it and see if it goes away...

I've let it scan for 100 times already, it never found anything.

yeah, the problem should be some windows Bug, so the "drive d must be tested at next startup flag" is never removed. For example when u use partion magic and order it to change something about your partitions it wants to restart your computer to have full access just after loading the main XP routines, when deinstalling it just before the restart, there will alway be a message "can't perform ..." because Partition Magic is missing and left this performing request somewhere. So it should all be fine at his pc