Windows XP forum: checkdisk runs at startup

Everything is possible ...
Start from purging temp files, scanning for errors and defrag:

http://www.fixyourwindows.com/optimizewindowstempfiles.htm
http://www.fixyourwindows.com/optimizewindowsharddrive.htm

If it doesnt help, get a hard drive test/diagnostic utility from the disk/computer manufacturer, and run it.

All the Best!

Did you run MSconfig and see if it or some other disk process is set to run on start.

Also check the boot.ini for any odd switches on the ARC path.

with Google Christy. The first one is a reply to someone else that had the same problem as you, maybe it will help. There are other replies under the first one but I didn't read the rest of them.
http://www.annoyances.org/exec/forum/winxp/1080019958

been asked that brought on that reply was for your exact problem (I thought anyway) LOL. You're welcome.

Are you runing Symantec SystemWorks Pro. gmperry

1. OK, I'll ask again because the first time (a previous thread) you skipped it.

Right click My Computer, select Manage. Expand Event Viewer and select the Application log. In the right hand pane, locate Winlogon and the event 1001. Double click to open it and copy and paste its content in the reply.

2. Here's the Data Lifeguard Tools 11 diagnostic for your hard drive. Read the instructions and perform at least a QUICK TEST.

Caution

Avoid at first the EXTENDED TEST, because it performs writes on HDD.


Good Luck,

Cetin


Trying to unweave, unwind, unravel
And piece together the past and the future,

T. S. Eliot

- Find interesting of what ? Technical problem, poster, thread, reply style ?

- Trying for Help ? Nah, Im a "Computer Cures" guy, because they were / are / will be different schools

OK, lets go further.

1. Finally Sesame was opened. Yes, the chkdsk log its OK. What you dont know its the fact that there are instances when they look OK (slight different than yours) but there are potential failure problems.

2. The Diagnostic Test log looks OK too.

So, it seems that were back at the original problem. Is it true ? Nah, we eliminated some possible causes such as your Imminent HD failure concern (not to mention the collateral benefits).

So, whats going on ? My theory its that you used some so called tuning tricks including probable something regarding shutdown too. Lets download the Auto End Tasks to Enable a Proper Shutdown (line 76, right side) reg file and open it (right click, select Edit). Youll see there three places that have direct shutdown impact. Compare those with the actual yours. The idea here its that your shutdown duration shouldnt be shorted by some tweaks.

You are welcome and Good Luck,

Cetin


Trying to unweave, unwind, unravel
And piece together the past and the future,

T. S. Eliot

WaitToKillServiceTimeout default value is 20000 (ms, decimal). This means 20 seconds. Yours it's 2000, so that means 2 seconds. So, change it to 20000 (20 seconds).

Let's try another workaround. Instead of Turn Off Computer & Turn Off sequence, use Log Off for every account (if several opened). After that, use Turn Off. This will give some clues if there is application related culprit or not.


Good Luck,

Cetin


Trying to unweave, unwind, unravel
And piece together the past and the future,

T. S. Eliot

>> So, my 2 seconds do not give Windows enough time to shut down all processes and running programs---that would be equivalent to an improper shutdown and so would evoke check disk ? If I set the value to '0', then checkdisk will always run on next boot ??<<

Yes, your shown scenario (2 seconds) is possible. However, if one set the value to 0 doesn't necessarily mean that chkdsk will run at the next restart.


>> During the process of downloading the floppy creater to run Western Digital's diagnostic test, I took the 'opportunity' to set the boot sequence from CD-HD-Floppy to Floppy-CD-HD. Since then, check disk has not ran at start up. Anything on that ?<<

It might be a simple coincidence. The floppy on the first position adds a delay to the boot process. However, in your case it's the dirty bit (in fact an improper shutdown bit) that triggers chkdsk. So, there is no correlation between Floppy drive first (boot order) and the bit that it's stored on the hard drive.


You are welcome and Good Luck,

Cetin


Trying to unweave, unwind, unravel
And piece together the past and the future,

T. S. Eliot

>> If I log off instead of shut down, I am back to the log on screen for logging on for a different user. Normal ?<<

Probable you're using the Classic Logon. So, you might try to check the "Users must enter a user name and password for this computer" box (run control userpasswords2).


>>Where on the HD can that dirt be ?<<

Check out the "More Information" section from the ScanDisk Runs After Improper Shutdown or Hard Disk Error.

Ignore the fact that it deals with windows 98 and previous version.


As for those settings, I saw the normal 2-3-1 sequence. Why your it's different ? Who knows, maybe you're using some third party tweaks applications.


Good Luck,

Cetin


Trying to unweave, unwind, unravel
And piece together the past and the future,

T. S. Eliot

I do not want to "remove" the message. That is not the issue. What is more important is to find out why it is happening. Seems to be no problems with the drive...

My File system is FAT32.

I have already ran check disk with the different parameters. No problems were ever found.

christy

I origional have SP1. SP2 was installed via a download. There have been no problems. All my devices run normally. Thanks for trying to help.

christy

I think SP2 is not designed that way. If that is true,then we would have to reformat and reinstall every time we install a program or get updates from Windows Update.

I did not follow the development of SP2. I think all those testing while in Beta would have taken care of all the potential problems. Well....Good Night and sleep well.

christy