CHKDSK never fixes errors.

[AnotherMuggle]

I have a fairly recent install of Windows XP and I have no issues with how the system is running.

If I do CHKDSK in the command prompt then it says there are errors in the file system and that I should do CHKDSK /F.

I have done this and restarted 4 times now but it still says the error is there. It's not a bad sector on the disk and hard disk diagnostics report that its ok.

Why are the errors not getting fixed?

[EzyStvy]

Have you tried the error checking tools found in the properties of the drive?

[AnotherMuggle]

I did that and let it run all the way to the end...it no longer reports that I have any errors

I have a feeling it may be back though and from what I have read online it appears that when running in read-only mode (in Windows) it is prone to incorrectly reporting errors.

UPDATE...I ran it again and now it is saying the errors are there again :S

Ran it a 3rd time they weren't there...then a 4th time and they are back.

[AnotherMuggle]

This seems to answer my question:

"Correcting errors in the Volume Bitmap. Windows found problems with the file system.
Issue:

Correcting errors in the Volume Bitmap.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these.

Tis is a known issue and the error messages are not actually means that there is problem in your system. You can safely ignore the error messages. The reason you are seeing these errors appear is because when you run CHKDSK in command prompt, it runs in “Read only” mode, and the state of the computer is changing at the time you run the utility. A "read only" chkdsk on an active NTFS volume will result in false positive errors, this is normal.

Read-only CHKDSK will abort before it completes all three phases if it encounters errors in earlier phases and is prone to falsely reporting errors when in read-only mode. That is, CHKDSK may report that a disk is corrupted even when there is no real corruption present. This can happen if NTFS happens to modify areas of the disk on behalf of some program activity that CHKDSK is examining at the same time.

To verify a volume correctly, the volume must be in a static state, and the only
way to guarantee that state is to lock the volume. CHKDSK only locks the volume
when it runs before entering Windows or in Recovery Console with /F or /R (which
implies "F") is specified."