[see bottom reply]
Here's your 1Oct2009 message from your other thread:
Subject: Re: CHKDSK Shut Down_Hang Up
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?
And your 7Oct2009 message in this thread:
Subject: Re: 0x00000024
message I have gotten the above error message several times accompanied by the
following detail: (0x001902FE, 0xADB804DC, 0xADB801D8, 0x8056C3B6).
According to the message, I should uninstall antivirus, defrag and back
up utilities then run CHKDSK. I recently uninstalled Memeo Back Up
software that came with a WD external hard drive.
I have run CHKDSK several times. Each time it stalls but at a later
point in the review of the hard drive.
This is a 4.5 year old Toshiba A75 Satellite Lap Top with outstanding
performance up until this point.
Questions: (1) How do I take off the defrag programs? is there are way
to evaluate this situation vis-a-vis the value of keeping the computer?
Any other advice?
Thanks in advance.
Al Charbonneau
Hi Al, (You're welcome in advance.
What is your full Windows version, edition, and Service Pack level?
(For instance, I'm using Windows XP, Professional, SP3.)
Important: Which drive are you running Chkdsk on? The external WD?
Where are you getting the STOP message? In Windows or at startup?
Where did you see a message that told you to uninstall something before
running CHKDSK? You should not add or subtract any files until Chkdsk is
successful in fixing the file system, and the system is healthy.
The 4 additional parameters with your 0x00000024 STOP message are:
1. Source file and line number.
2. The address of the exception record.
3. The address of the context record.
4. 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."
(0x001902FE, 0xADB804DC, 0xADB801D8, 0x8056C3B6)
1. File: 0x0019 (Decimal:25), Line: 0x02FE (Decimal:766)
2. 0xADB804DC = 2914518236 decimal
3. 0xADB801D8 = 2914517464 decimal
4. 0x8056C3B6 = 2153169846 decimal
I do not have any more particular information on those things.
Caution:
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
could try copying a known good copy of ntfs.sys to your system32 folder,
after renaming the present ntfs.sys file to ntfs.old first, but...
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, (not ntfs.sys,) 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.
How much RAM does the laptop have?
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: Verifies each file record segment in the master file table
Stage 2: Checks the directories in the volume
Stage 3: Verifies the security descriptors for each volume
Stage 4: Verifies all clusters in use (file space)
Stage 5: Verifies unused clusters (free space)
Stage 2 usually takes longer than either stage 1 or stage 3. Stage 4 takes
longer than stage 5, unless you have much more than 50 percent free space.
CAUTION: Do NOT interrupt CHKDSK /F (or /P or /R) once it has started.
Do not start CHKDSK if there is possibility of power loss due to storm or
wind downed branches within 24 hours or so. If you have millions of files
on the drive, CHKDSK could take days, rather than hours to complete. The
progress percentage indicates tasks completed, not necessarily elapsed
time. Directories (folders) with a lot of files and subfolders take longer
to check, so it is normal in such case for Chkdsk to appear to be stuck on
a certain percent number. As long as there is occasional drive activity, it
is still working. If there has been NO drive activity for 30+ minutes,
first try Ctrl+C to stop it, before resorting to other means.
Keep the environment around the drive COOL. If you suspect over heating,
put some ice cubes in a large zip lock food bag, or sturdy trash bag, seal
it, lay a single layer fluffy towel over it, and set the laptop on that.
Do not move the laptop while there is drive activity, and of course, you
need to be on external power while running CHKDSK. (Got UPS?)
How do I take off the defrag programs?
If you are talking about the Windows XP Disk Defragmenter, don't. If you
are talking about a 3rd party defrag or optimizer program, wait until you
are sure the file system is stable, and are able to logon to Windows
normally, and then use Add/Remove programs to remove it/them.
... the value of keeping the computer?
Does the 4.5 years old computer or at least drive, have a 5 year warranty?
Run the various hardware diagnostics available for your model of laptop,
including disk drive diagnostics and RAM memory test. The desktop Toshiba
on the table beside me is still going strong after more than 11 years,
(with the original CMOS battery!) and a new hard drive ~7+ years ago.
Microsoft Online Crash Analysis - Download Windows Memory Diagnostic
http://oca.microsoft.com/en/windiag.asp
Note: That page itself is the User Guide, File SaveAs to disk.
The Windows Memory Diagnostic download file is: mtinst.exe (640 KB)
(If your computer manufacturer's website has a mem test, use it.)
If you answer all the questions in this message, we might be able to
provide better advice. Based on what has been revealed so far, if the
system drive is the problem drive, you should be able to do this:
1. First run "CHKDSK" in read only mode with no parameters.
If it completes, you know that CHKDSK itself is working properly.
You may get this message:
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these.
2. Run "CHKDSK /F" to completion. (From Recovery Console: CHKDSK /P)
3. Run disk drive and memory diagnostics. Fan(s) working OK?
4. When you can logon to WinXP normally, run WinXP Disk Defragmenter.
5. Run WinXP Disk Cleanup, and RESTART the computer, and immediately:
6. Run Disk Defragmenter Analyse only. Save the report with date/time.
(Post a copy of the report here. X out any personal info.)
7. Wait 7 days before adding or removing any software.
While waiting, once per day, shutdown the computer for 5 minutes.
Start the computer and time how long until desktop wallpaper appears.
(It would be best to disable Hibernation for the time being also.)
8. Then run Disk Defragmenter Analyse only again, and post report here.
Note that the normal order is to run Disk Cleanup before defrag, but above,
I want you to defrag the temporary files area in its present condition,
partly to give defrag a workout with a heavier workload, and to detect any
potential problems with those areas of the disk that get changed the most.
Defrag needs at least 15 percent free space to function properly, so if you
do not have that much free space, go ahead and free enough space first.
Start> (all)Programs> Accessories> System Tools> Disk Defragmenter
Start> (all)Programs> Accessories> System Tools> Event Viewer
(In Event Viewer, Application, look in Source column for Winlogon. When
Check Disk runs at startup, that is where results are recorded.)
Have you ruled out the possibility of virus or other malware?
(Triple-click here, to be of good cheer.
--Richard
