Win2k Startup

[stylehurst]

I run W2k SP4 and have recently had the following problem
occur: On startup Chkdsk always runs saying there is a
problem on the C drive. A check of the Event Log shows the
following: System Log "Error detected on hard drive during
paging operation" Application Log: Winlogon "Cleaning
minor inconsistencies Cleaning 4 unused index entries from
index $S11 of file 0x9 Cleaning 4 unused entries from
index $SDH of file 0x9 Cleaning 4 unused security
descriptors"

A full chkdsk states no bad sectors

Has anybody else experienced this problem & is there a
cure other than stopping chkdsk from running at startup. A
complete re-format & re-install does not solve the
problem.

By-passing chkdsk does not seem to cause problems.
Any suggestions and/or explanation would be welcome.

 

[Greg Stigers]

Jason Hall answered a similar question, "RE: Chkdsk runs every boot" on May
13th. He wrote:
The first thing that I would do would be to boot to the Recovery Console
and run chkdsk /r, in case there really is something that needs to be
fixed. Booting to recovery console will ensure that no application can
interfere with the process (like PCAnywhere, Antivirus, and Backup
utilities).

For more information on chkdsk:
Q218461: Description of Enhanced Chkdsk, Autochk, and Chkntfs Tools in
Windows
support.microsoft.com/?id=218461

Stephen also wrote:
You need to check the event logs to see if your system is logging disk
errors. You may be having hardware issues. When windows detects corruption
it sets a "dirty bit" that tells it to run ckhdsk (autochk) at start up.
Once it runs and completes, the bit should be set back to clean. You can try
booting to the recovery console and run chkdsk /R. If it indicates errors
were found and fixed, run it again. Repeat this until no errors are found.
If it always finds errors, chances are your having hardware troubles in your
disk sub system.

 

[stylehurst]

Thanks Greg, gives me something to start on.
Checked Event log, getting Event ID51 messages; "Error
detected during paging operation"

Out of interest what are the hardwarew problems in disk
sub system yyou are referring to at the end of your
message?
What are the cures if different from running chkdsk

 

[Jason Hall [MSFT]]

--------------------

From: "Greg Stigers" <[email protected]>
Subject: Re: Win2k Startup
Date: Sat, 15 May 2004 13:05:19 -0400

Jason Hall answered a similar question, "RE: Chkdsk runs every boot" on May
13th. He wrote:
The first thing that I would do would be to boot to the Recovery Console
and run chkdsk /r, in case there really is something that needs to be
fixed. Booting to recovery console will ensure that no application can
interfere with the process (like PCAnywhere, Antivirus, and Backup
utilities).

For more information on chkdsk:
Q218461: Description of Enhanced Chkdsk, Autochk, and Chkntfs Tools in
Windows
support.microsoft.com/?id=218461

Stephen also wrote:
You need to check the event logs to see if your system is logging disk
errors. You may be having hardware issues. When windows detects corruption
it sets a "dirty bit" that tells it to run ckhdsk (autochk) at start up.
Once it runs and completes, the bit should be set back to clean. You can try
booting to the recovery console and run chkdsk /R. If it indicates errors
were found and fixed, run it again. Repeat this until no errors are found.
If it always finds errors, chances are your having hardware troubles in your
disk sub system.

---------------------

Stole the words right outta my mouth ; )
...and saved me some tying time


--
~~ JASON HALL ~~
~ Performance Support Specialist,
~ Microsoft Enterprise Platforms Support
~ This posting is provided "AS IS" with no warranties, and confers no
rights.
~ Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
~ Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.

 

[Greg Stigers]

I was quoting a "Stephen" from his post in the "Chkdsk runs every boot"
thread. But I assume that the disk subsystem refers to whatever hardware
your system uses for the disks. This can be the basic motherboard-based IDE
controller(s), cable(s), and IDE drive(s), or can be a hardware RAID. But,
as Stephen wrote, "If it always finds errors", "it" being repeated runs of
chkdsk /r in the Recovery Console, you have reason for concern. On the other
hand, if it does not, you do not.