CHKDSK C: reports errors only when run from within XP

[h7qvnk7q001]

When I run CHKDSK C: from within XP, I get several errors of the
form:
"<filename> first allocation unit is not valid. The entry will be
truncated."
The errors are typically on \Windows\Prefetch* files, but the specific
files reported with errors change with each run of CHKDSK.

When I use CHKDSK /F and let the test run on a restart, there are no
errors.

When I boot to Recovery Console and run CHKDSK there are no errors
found.

I have run the hard disk manufacturers diagnostic program, and no
errors are found.

This is happening on a FAT32 volume that I'm trying to get "clean" to
convert to NTFS.

What could be the cause of this behavior?

T.

 

[philo]

When I run CHKDSK C: from within XP, I get several errors of the
form:
"<filename> first allocation unit is not valid. The entry will be
truncated."
The errors are typically on \Windows\Prefetch* files, but the specific
files reported with errors change with each run of CHKDSK.

When I use CHKDSK /F and let the test run on a restart, there are no
errors.

When I boot to Recovery Console and run CHKDSK there are no errors
found.

I have run the hard disk manufacturers diagnostic program, and no
errors are found.

This is happening on a FAT32 volume that I'm trying to get "clean" to
convert to NTFS.

What could be the cause of this behavior?

I've seen that myself on a machine I was working on...
RAM and HD diagnostics ran clean...
Though I found nothing that I could put my finger on...I tried underclocking
the machine slightly...
and the "problem" went away.

Just a guess here but it *might* be due to a mobo that is just a bit out of
tolerance

 

[db]

the prefetch files can be deleted
if you choose to do so.

afterwards each prefetch file will be rebuilt as
you launch a program.

for example
when you launch word, a prefetch file for it
will be created. there is more info at Microsoft.com
but basically, the prefetch file is a log with the
exact locations of the word system files.

this is like a quick checklist that speeds
up the start time of a program,
rather than looking through the whole disk for the
files like it use to with the older windows.

you might want to wait before
converting to ntfs. instead monitor
the prefetch folder over the next week.

i would run a check disk everyday
until the questionable issues are
eliminated / resolved.

- db
When I run CHKDSK C: from within XP, I get several errors of the
form:
"<filename> first allocation unit is not valid. The entry will be
truncated."
The errors are typically on \Windows\Prefetch* files, but the specific
files reported with errors change with each run of CHKDSK.

When I use CHKDSK /F and let the test run on a restart, there are no
errors.

When I boot to Recovery Console and run CHKDSK there are no errors
found.

I have run the hard disk manufacturers diagnostic program, and no
errors are found.

This is happening on a FAT32 volume that I'm trying to get "clean" to
convert to NTFS.

What could be the cause of this behavior?

T.