Read this and see if it pertains to you.http://support.micro...om/?kbid=316506
Run "msconfig.exe" and then disable scandisk at startup.
Usually the problem lies in some form of driver conflict screwing up windows shutdown procedure.
Update all your drivers to latest, in particular your IDE drivers.
Also Nvidia and ATI have little proggies which are memory resident & seem to resist all efforts to close them at shutdown. Using MSCONFIG, you can disable these unnecessary hindrances from starting (although technically it is better to disable these through services management).
On volumes marked as "dirty," Windows automatically runs chkdsk when the computer is started or restarted.
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.
One thing you must think about is why this is happening. It may be just a update problem that caused this or it may be that your hard drive is getting corrupted sectors. I have seen a loose data cable cause this problem. I have also seen where the hard drive was still running when the computer shut down because some program was still writing to the drive. Removing the offending program(older Adobe photoshop) stopped the chkdsk.