Sudden Disk Check errors on boot

[jneiberger]

I powered up my Vista 64 machine tonight and chkdsk starting going berserk. I saw a whole bunch of "deleting index entry" and something about Windows and AMD64. I had no idea what I was even seeing until I did some research, but I'm confused about what's happening.

Anyway, from a command prompt I ran sfc /scannow and this is what I saw:

C:\Users\Administrator>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files but was unable to fix some of th
em.
Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
C:\Windows\Logs\CBS\CBS.log

C:\Users\Administrator>findstr /c:"[SR]" %windir%\logs\cbs\cbs.log>%userprofile%
\Desktop\sfcdetails.txt

So, I checked that file and saw this:

2009-02-12 02:17:10, Info CSI 000003a0 [SR] Cannot verify component files for Microsoft-Windows-VideoViewer, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest may be damaged (TRUE)
2009-02-12 02:17:11, Info CSI 000003a1 [SR] Cannot verify component files for Microsoft-Windows-VistaSP1CEIP, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest may be damaged (TRUE)
2009-02-12 02:17:11, Info CSI 000003a2 [SR] Cannot verify component files for Microsoft-Windows-VMG-Shared.Resources, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest may be damaged (TRUE)
2009-02-12 02:17:11, Info CSI 000003a3 [SR] Cannot verify component files for Microsoft-Windows-VMG-Shared, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest may be damaged (TRUE)
2009-02-12 02:17:11, Info CSI 000003a4 [SR] Cannot verify component files for Microsoft-Windows-VolumeManagement-Core, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest may be damaged (TRUE)
2009-02-12 02:17:11, Info CSI 000003a5 [SR] Cannot verify component files for Microsoft-Windows-VolumeManagement, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest may be damaged (TRUE)
2009-02-12 02:17:11, Info CSI 000003a6 [SR] Cannot verify component files for Microsoft-Windows-VssAdmin.Resources, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest may be damaged (TRUE)
2009-02-12 02:17:11, Info CSI 000003a7 [SR] Cannot verify component files for Microsoft-Windows-VssAdmin, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest may be damaged (TRUE)
2009-02-12 02:17:11, Info CSI 000003a8 [SR] Cannot verify component files for Microsoft-Windows-VSSProviders, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest may be damaged (TRUE)
2009-02-12 02:17:11, Info CSI 000003a9 [SR] Cannot verify component files for Microsoft-Windows-VssProxyStub, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest may be damaged (TRUE)
2009-02-12 02:17:11, Info CSI 000003ac [SR] Verify complete
2009-02-12 02:17:12, Info CSI 000003ad [SR] Verifying 100 (0x0000000000000064) components
2009-02-12 02:17:12, Info CSI 000003ae [SR] Beginning Verify and Repair transaction
2009-02-12 02:17:12, Info CSI 000003af [SR] Cannot verify component files for Microsoft-Windows-VssService.Resources, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest may be damaged (TRUE)
2009-02-12 02:17:12, Info CSI 000003b0 [SR] Cannot verify component files for Microsoft-Windows-VssService, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest may be damaged (TRUE)
2009-02-12 02:17:15, Info CSI 000003b2 [SR] Verify complete

And toward the end I saw this:

2009-02-12 02:19:53, Info CSI 00000500 [SR] Cannot verify component files for Microsoft-Windows-VMG-Shared, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest may be damaged (TRUE)
2009-02-12 02:19:53, Info CSI 00000501 [SR] Cannot verify component files for Microsoft-Windows-VolumeManagement-Core, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest may be damaged (TRUE)
2009-02-12 02:19:53, Info CSI 00000502 [SR] Cannot verify component files for Microsoft-Windows-VssProxyStub, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest may be damaged (TRUE)
2009-02-12 02:19:53, Info CSI 00000503 [SR] Cannot verify component files for Microsoft-Windows-VMG-Shared.Resources, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest may be damaged (TRUE)
2009-02-12 02:19:53, Info CSI 00000504 [SR] Cannot verify component files for Microsoft-Windows-VolumeManagement, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest may be damaged (TRUE)
2009-02-12 02:19:53, Info CSI 00000505 [SR] Cannot verify component files for Microsoft-Windows-VideoViewer, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest may be damaged (TRUE)
2009-02-12 02:19:53, Info CSI 00000506 [SR] Cannot verify component files for Microsoft-Windows-VistaSP1CEIP, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest may be damaged (TRUE)
2009-02-12 02:19:53, Info CSI 00000507 [SR] Cannot verify component files for Microsoft-Windows-VssAdmin.Resources, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest may be damaged (TRUE)
2009-02-12 02:19:53, Info CSI 00000508 [SR] Cannot verify component files for Microsoft-Windows-VSSProviders, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest may be damaged (TRUE)
2009-02-12 02:19:53, Info CSI 00000509 [SR] Cannot verify component files for Microsoft-Windows-VssAdmin, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest may be damaged (TRUE)
2009-02-12 02:19:53, Info CSI 0000050a [SR] Cannot verify component files for Microsoft-Windows-VssService.Resources, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest may be damaged (TRUE)
2009-02-12 02:19:53, Info CSI 0000050b [SR] Cannot verify component files for Microsoft-Windows-VssService, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest may be damaged (TRUE)
2009-02-12 02:19:53, Info CSI 0000050d [SR] Repair complete
2009-02-12 02:19:53, Info CSI 0000050e [SR] Committing transaction
2009-02-12 02:19:53, Info CSI 00000512 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired


I have no idea what's going on. It appears that something has been corrupted, but I have no idea how. I'm also confused that a lot of what appears to be hosed has to do with AMD64 something-or-other and I have an Intel Core i7 processor, not AMD64.

I'm also confused about whether or not this repair actually worked. At first it appears that it did not, but then at the very end of the file it says that the repair was successful. Which is it?

If something is still wrong, what do I do to fix it?

Thanks!

 

[linney]

How to analyze the log file entries that the Microsoft Windows Resource Checker (SFC.exe) program generates in Windows Vista

http://support.microsoft.com/kb/928228#appliesto

Do you have your valuable data backed up and saved somewhere? You may be heading for a clean install of the operating system.

In Vista ChkDsk can be a bit of a rogue and has been known to corrupt systems rather than fix them.

Chkdsk "file 9" and what follows - walterouze

http://www.eggheadcafe.com/software/aspnet/31697890/chkdsk-file-9-and-what.aspx

http://www.google.com/search?q=Chkdsk+"file+9"+vista&rls=com.microsoft:

This link is not directly related to Vista but explains the danger of using ChkDsk in Vista.

The CHKDSK utility incorrectly identifies and deletes in-use security descriptors

http://support.microsoft.com/kb/831374/en-us#appliesto

 

[jneiberger]

I can't find anywhere what "Cannot verify component files" actually means. I also can't figure out why it apparently says my processor is an AMD64 when it is actually an Intel Core i7 920.

Very weird behavior.

 

[BadBigBen]

I also can't figure out why it apparently says my processor is an AMD64 when it is actually an Intel Core i7 920.

that is because the CPU uses the 64 bit extension first developed by AMD... Intel calls it EMT64...

First off, I would check the integrity of the HDD by using the manufacturers tools... have the tools check the mechanics, the recording surface, basically a FULL test... that way you know that it is not the HDD but the FS at fault...

I fear that you are heading towards a repair install...

How To Perform a Repair Installation For Vista

http://www.vistax64.com/tutorials/88236-repair-install-vista.html

Ben

"If it works don't fix it! If it doesn't use a sledgehammer..."

How to ask a question, when posting them to a professional forum.

 

[jneiberger]

I just got home and ran sfc /scannow from safe mode and it reported the same things, basically. Then I ran a scheduled disk check and it didn't find anything wrong with the drive or the file system. I think I'm going to chalk it up to a weird fluke for the time being.