Chkdsk Reports Problems

[Black]

Whenever I run chkdsk on my system drive, (NTFS) it reports about correction
of errors in Volume Bitmap and then reports about problems with the file
system and to run chkdsk /f.... Chkdsk /f does correct the problems (if
viewed in application event viewer) but no matter how many times I do it, a
fresh chkdsk always reports the same errors. What could be wrong. I have a 4
month old 60 GB drive which is properly placed and cooled. I am running XP
SP1. Any ideas as to what could be wrong. I will be obliged.

 

[GSV Three Minds in a Can]

Whenever I run chkdsk on my system drive, (NTFS) it reports about correction
of errors in Volume Bitmap and then reports about problems with the file
system and to run chkdsk /f.... Chkdsk /f does correct the problems (if
viewed in application event viewer) but no matter how many times I do it, a
fresh chkdsk always reports the same errors. What could be wrong. I have a 4
month old 60 GB drive which is properly placed and cooled. I am running XP
SP1. Any ideas as to what could be wrong. I will be obliged.

Could well be a disk drive problem .. somewhere between 1 in 50 and 1 in
100 die every year. If I were you I be backing up my data and trying a
new drive (or at least running the manufacturer's diagnostics on it).

 

[Bert Smith]

Hi

Please take a look at the following that I sent to Jane, a helpful Microsoft
Support person about this problem.
Hi Jane

I have done some extensive research over my NTFS file problems in Windows XP
Professional that I contacted Microsoft about and I think I have resolved
it.

A Google search revealed an interesting article
http://webspiffy.com/archives/2002/08/ntfs_file_system_glitch/ .

First, there appears to be a problem with chkdsk recording false positive
errors when run from a command prompt. I can find no reference to this
problem in the Microsoft Knowledge Base. To quote from the above article
that is reportedly sourced from Microsoft, "This problem occurs because when
chkdsk is run against a NTFS volume, chkdsk.exe may report that security
descriptors are in the database that are no longer referenced by any file or
folder, and that it is removing them. However, chkdsk.exe just reclaims the
unused security descriptors as housekeeping activity, and is not actually
fixing any kind of problem."

Thus the instruction given by chkdsk to run chkdsk with the /f fix option to
correct these errors can be safely ignored, but of course, only in certain
specific circumstances.

There are many reports in web forums of poor souls doing high and low level
formats on their hard drives, ASR restores, changing hard disks, etc and
generally pulling their hair out, all to no avail because of this bug in
chkdsk.

I sincerely hope that Microsoft fixes this problem ASAP. At least please
tell people to use chkntfs c: to see if a volume is dirty before they press
the panic button! Chkdsk is the only NTFS file utility that will correct
problems with files/disks and a bug like this can be an unneeded heart
stopper, if chkdsk is giving false positive errors!

Now to the lock ups I received when running chkdsk /r.

Your advice about InCD causing this is almost certainly correct. (THANKS!)
On uninstalling InCD 4.0.1.7 I now find that chkdsk /r will run from a
restart without a lock up. I did not try this until yesterday because of the
bogus "errors" I was getting from chkdsk run from a command prompt. (I did
not like my system files being threatened!) In 2 trials, after the uninstall
of InCD no lockups! No more silly STOP 0x7E messages. Problem (almost
certainly) resolved. What I don't understand is how InCD interferes with the
running of autochk on restart. On reboot, when autochk is run, InCD would
not be loaded. I intend contacting AHEAD Nero and advising them of this.