Vista - Chkdsk /F always reports the same errors despite "fixing" said err

Chkdsk /F always reports the same errors despite fining said errors

Sample of errors shown:
Index entry wpcuninst.mof in index $I30 of file 5317 is incorrect.
Index entry pmcsnap.dll.mui in index $I30 of file 5328 is incorrect.
Index entry ppcsnap.dll.mui in index $I30 of file 5328 is incorrect.
Index entry printmanagement.msc in index $I30 of file 5328 is incorrect.
Index entry pathping.exe.mui in index $I30 of file 5330 is incorrect.
Index entry ping.exe.mui in index $I30 of file 5330 is incorrect.
Index entry tracert.exe.mui in index $I30 of file 5330 is incorrect.
Index entry gpprnext.dll in index $I30 of file 5406 is incorrect.
Index entry ppcRsopCompSchema.mof in index $I30 of file 5406 is incorrect.
Index entry ppcRsopUserSchema.mof in index $I30 of file 5406 is incorrect.

How do I get chkdsk to fix these errors once and for all?

CS wrote:
> Chkdsk /F always reports the same errors despite fining said errors
>
> Sample of errors shown:
> Index entry wpcuninst.mof in index $I30 of file 5317 is incorrect.
> Index entry pmcsnap.dll.mui in index $I30 of file 5328 is incorrect.
> Index entry ppcsnap.dll.mui in index $I30 of file 5328 is incorrect.
> Index entry printmanagement.msc in index $I30 of file 5328 is incorrect.
> Index entry pathping.exe.mui in index $I30 of file 5330 is incorrect.
> Index entry ping.exe.mui in index $I30 of file 5330 is incorrect.
> Index entry tracert.exe.mui in index $I30 of file 5330 is incorrect.
> Index entry gpprnext.dll in index $I30 of file 5406 is incorrect.
> Index entry ppcRsopCompSchema.mof in index $I30 of file 5406 is incorrect.
> Index entry ppcRsopUserSchema.mof in index $I30 of file 5406 is incorrect.
>
> How do I get chkdsk to fix these errors once and for all?

Download a diagnostic utility from the hard drive mftr. If you can't
find one for your specific hard drive, Seagate's SeaTools works well.
You will create a bootable cd (or floppy) with the file you download.
Boot with the media you created and do a thorough test of the drive. If
the drive fails any physical tests, replace it.

If the drive tests good, test your RAM. I like Memtest86+ from
www.memtest.org. You will do something similar to the hard drive
utility. Download the image for the bootable CD and boot with it. Allow
Memtest to run for an extended period of time (at least 1 hour) unless
you get errors right away. If you get errors, replace the faulty stick
of RAM.

You need third-party burning software to burn an .iso in XP. I'm not
sure whether Vista's built-in burning program can do this. Look in
Vista's Help for "burn image" if you don't have third-party burning
software installed (Roxio, Nero, etc.).


Malke
--
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"
MS-MVP Windows - Shell/User

This isn't a hardware issue. It is almost as if something is preventing
chkdsk from completing what it needs to do.

"Malke" wrote:

> CS wrote:
> > Chkdsk /F always reports the same errors despite fining said errors
> >
> > Sample of errors shown:
> > Index entry wpcuninst.mof in index $I30 of file 5317 is incorrect.
> > Index entry pmcsnap.dll.mui in index $I30 of file 5328 is incorrect.
> > Index entry ppcsnap.dll.mui in index $I30 of file 5328 is incorrect.
> > Index entry printmanagement.msc in index $I30 of file 5328 is incorrect.
> > Index entry pathping.exe.mui in index $I30 of file 5330 is incorrect.
> > Index entry ping.exe.mui in index $I30 of file 5330 is incorrect.
> > Index entry tracert.exe.mui in index $I30 of file 5330 is incorrect.
> > Index entry gpprnext.dll in index $I30 of file 5406 is incorrect.
> > Index entry ppcRsopCompSchema.mof in index $I30 of file 5406 is incorrect.
> > Index entry ppcRsopUserSchema.mof in index $I30 of file 5406 is incorrect.
> >
> > How do I get chkdsk to fix these errors once and for all?
>
> Download a diagnostic utility from the hard drive mftr. If you can't
> find one for your specific hard drive, Seagate's SeaTools works well.
> You will create a bootable cd (or floppy) with the file you download.
> Boot with the media you created and do a thorough test of the drive. If
> the drive fails any physical tests, replace it.
>
> If the drive tests good, test your RAM. I like Memtest86+ from
> www.memtest.org. You will do something similar to the hard drive
> utility. Download the image for the bootable CD and boot with it. Allow
> Memtest to run for an extended period of time (at least 1 hour) unless
> you get errors right away. If you get errors, replace the faulty stick
> of RAM.
>
> You need third-party burning software to burn an .iso in XP. I'm not
> sure whether Vista's built-in burning program can do this. Look in
> Vista's Help for "burn image" if you don't have third-party burning
> software installed (Roxio, Nero, etc.).
>
>
> Malke
> --
> Elephant Boy Computers
> www.elephantboycomputers.com
> "Don't Panic!"
> MS-MVP Windows - Shell/User
>

Try chkdsk /r (repair with full surface scan).

--


Regards,

Richard Urban
Microsoft MVP Windows Shell/User
(For email, remove the obvious from my address)



"CS" <CS@discussions.microsoft.com> wrote in message
news:6BBB274C-E4E4-4029-981D-601ED5D4CE43@microsoft.com...
> Chkdsk /F always reports the same errors despite fining said errors
>
> Sample of errors shown:
> Index entry wpcuninst.mof in index $I30 of file 5317 is incorrect.
> Index entry pmcsnap.dll.mui in index $I30 of file 5328 is incorrect.
> Index entry ppcsnap.dll.mui in index $I30 of file 5328 is incorrect.
> Index entry printmanagement.msc in index $I30 of file 5328 is incorrect.
> Index entry pathping.exe.mui in index $I30 of file 5330 is incorrect.
> Index entry ping.exe.mui in index $I30 of file 5330 is incorrect.
> Index entry tracert.exe.mui in index $I30 of file 5330 is incorrect.
> Index entry gpprnext.dll in index $I30 of file 5406 is incorrect.
> Index entry ppcRsopCompSchema.mof in index $I30 of file 5406 is incorrect.
> Index entry ppcRsopUserSchema.mof in index $I30 of file 5406 is incorrect.
>
> How do I get chkdsk to fix these errors once and for all?

Tried that as well. Same as before.
This looks exactly what I'm seeing by the KB is for Win 2k not Vista:
http://support.microsoft.com/kb/327009/en-us
This is really annoying because it might mask real issues when they arise. I
really don't want to have to reformat and install Vista.

"Richard Urban" wrote:

> Try chkdsk /r (repair with full surface scan).
>
> --
>
>
> Regards,
>
> Richard Urban
> Microsoft MVP Windows Shell/User
> (For email, remove the obvious from my address)
>
>
>
> "CS" <CS@discussions.microsoft.com> wrote in message
> news:6BBB274C-E4E4-4029-981D-601ED5D4CE43@microsoft.com...
> > Chkdsk /F always reports the same errors despite fining said errors
> >
> > Sample of errors shown:
> > Index entry wpcuninst.mof in index $I30 of file 5317 is incorrect.
> > Index entry pmcsnap.dll.mui in index $I30 of file 5328 is incorrect.
> > Index entry ppcsnap.dll.mui in index $I30 of file 5328 is incorrect.
> > Index entry printmanagement.msc in index $I30 of file 5328 is incorrect.
> > Index entry pathping.exe.mui in index $I30 of file 5330 is incorrect.
> > Index entry ping.exe.mui in index $I30 of file 5330 is incorrect.
> > Index entry tracert.exe.mui in index $I30 of file 5330 is incorrect.
> > Index entry gpprnext.dll in index $I30 of file 5406 is incorrect.
> > Index entry ppcRsopCompSchema.mof in index $I30 of file 5406 is incorrect.
> > Index entry ppcRsopUserSchema.mof in index $I30 of file 5406 is incorrect.
> >
> > How do I get chkdsk to fix these errors once and for all?
>
>

There are new switches for chkdsk in Windows Vista. Try this command line:

chkdsk /?

Although I haven't tried it, there appears to be a /b switch that, if I recall, revisits previously marked sectors?

Here is the command line that I run for every chkdsk:

chkdsk (drive letter) /x /f /v /r /v /l:65535

Good luck,
Mike

I've found a workaround that is less than satifactory.

locate and rename each and every file and then rename them back.

"MikeWilson" wrote:

>
> There are new switches for chkdsk in Windows Vista. Try this command
> line:
>
> chkdsk /?
>
> Although I haven't tried it, there appears to be a /b switch that, if I
> recall, revisits previously marked sectors?
>
> Here is the command line that I run for every chkdsk:
>
> chkdsk (drive letter) /x /f /v /r /v /l:65535
>
> Good luck,
> Mike
>
>
> --
> MikeWilson
>