CHKDSK Shut Down/Hang Up

[Al Charbonneau]

After getting a STOP: 0x00000024 message I ran CHKDSK several times. A
couple of times it progressed well than shut down before completion. Another
time it hung up at 63% of stage 4. Any recommendations?

[Richard Urban]

Obtain, and run, the hard drive test utility that your hard drive
manufacturer provides on their web site. They all have them.

--

Richard Urban
Microsoft MVP
Windows Desktop Experience


"Al Charbonneau" > wrote in message
...
> After getting a STOP: 0x00000024 message I ran CHKDSK several times. A
> couple of times it progressed well than shut down before completion.
> Another
> time it hung up at 63% of stage 4. Any recommendations?

[Jose]

On Oct 1, 8:58*pm, Al Charbonneau
> wrote:
> After getting a STOP: 0x00000024 message I ran CHKDSK several times. *A
> couple of times it progressed well than shut down before completion. *Another
> time it hung up at 63% of stage 4. *Any recommendations?

Yes - more information please.

Was this event preceded by a power interruption, ungraceful shutdown
or aborted boot attempt?

Do you see this message when you try to boot?

Are you able to boot and later you see the message?

How are you running chkdsk?

Do you have bootable XP installation media or a Recovery Console CD?

If I saw this on a boot attempt, step 1 would be to use my XP Recovery
Console CD and run chkdsk /r from there.

[Richard[_12_]]

> "Al Charbonneau" > wrote in
> message
> ...
> After getting a STOP: 0x00000024 message I ran CHKDSK several times. A
> couple of times it progressed well than shut down before completion.
> Another
> time it hung up at 63% of stage 4. Any recommendations?

Hi Al,

What is your full Windows edition, version, and Service Pack level?
(For instance, I'm using Windows XP Professional, Service Pack 3.)

Where are you getting the STOP message? In Windows or startup?

Where is the rest of the STOP message? There should be at least 1 more, or
as many as 4 more parameters with that particular stop error that indicate:
1. Source file and line number.
2. Optionally contains the address of the exception record.
3. Optionally contains the address of the context record.
4. Optionally contains the address where the original exception occurred.

"All stop errors due to problems with NTFS or FAT have encoded in their
first parameter the source file and the line number within the source file
that generated the stop error. The high 16 bits (the first four hexadecimal
digits after 0x) identify the source file number, and the lower 16 bits (the
last four hexadecimal digits of the parameter) identify the source line in
the file where the stop occurred."

You should not be using the CHKDSK /R command unless you have reason to
believe that you have caused physical damage to the disk by dropping or
bumping the drive severely. The STOP message indicates an NTFS_FILE_SYSTEM
problem. There is either a problem with the NTFS.SYS driver, or some sort of
corruption in the file system. Therefore there is no need to check for bad
sectors in the free space. Since CHKDSK obviously completed the 3 File Fix
stages before beginning stage 4, it is not likely that the file system
itself is the problem. That leaves either the ntfs.sys file itself, or a
problem with the disk drive. Either way, you should get the drive
manufacturer's diagnostic tool from their website and check the disk. You
can try copying a known good copy of ntfs.sys to your system32 folder, after
renaming the present ntfs.sys file to ntfs.old first.

Microsoft NOTE: "The Chkdsk tool has built-in support for NTFS and does not
require the Ntfs.sys driver to make repairs."

Therefore, since you had some problems with Chkdsk, the drive itself is the
more likely problem, either corrupt SCSI or IDE drivers, or physical
malfunction, such as power supply or over heating. Which drive is having the
problem? System volume? or non-system volume? Are you running chkdsk from
within Windows, or at startup with Autochk, or from the winXP CD Recovery
Console? Outside the Windows operating system, chkdsk cannot use the virtual
memory pagefile, and must run entirely in RAM (Random Access Memory), which
can greatly increase the time to run if you have less than about 512 MB RAM.

Troubleshooting Disks and File Systems
http://technet.microsoft.com/en-us/library/bb457122.aspx

Again: Specifying the /R parameter is usually not necessary because NTFS
identifies and remaps bad sectors during the course of normal operations:
"NTFS is a journaling file system because it guarantees the consistency of
the volume by using standard transaction logging and recovery techniques. If
a disk becomes corrupted, NTFS runs a recovery procedure that accesses
information stored in a transaction log file. The NTFS recovery procedure
guarantees that the volume is restored to a consistent state. For this
reason, it is unlikely that NTFS volumes might become corrupted."

"Chkdsk is sluggish on a drive that is heavily fragmented."

Stage 1: Chkdsk verifies each file record segment in the master file table
Stage 2: Chkdsk checks the directories in the volume
Stage 3: Chkdsk verifies the security descriptors for each volume
Stage 4: Chkdsk verifies all clusters in use;
Stage 5: Chkdsk verifies unused clusters.

Stage 2 usually takes longer than either stage 1 or stage 3. Stage 4 usually
takes longer than stage 5, unless you have much more than 50% free space.

FWIW. (For What It's Worth. :)
--Richard