New
#1
Do these chkdsk messages mean that I need to replace the drive?
Or is it something that a reformat/reinstall of windows might fix? How do I determine that?
I've basically had a ton of chkdsk errors, and I can't tell if it is leftover from a faulty RAM stick that I removed a week ago, or if it's a failing disk that needs to be replaced (although it's a pretty new Western Digital Caviar Black drive).
I've posted several of the chkdsk and NTFS/Disk failure event logs below (.evtx files that will open in your event viewer).
- Disk-related events from the last several months (EVTX file)
- "Administrative Events" from yesterday (EVTX file) that show a ton of different errors (some of the ones that repeat dozens of times I pared down to 10 or so
Here is the story around the chkdsk ones:
Several times I did the following (which I think performs a chkdsk /f):
- fsutil set dirty c:
fsutil set dirty d:
shutdown -r
That resulted in the multiple pairs of C/D "Cleaning up index... No problems found." messages. Then I ran the following twice (/f is not necessary as it is implied by /r):
- chkdsk /r c:
shutdown -r
Those resulted in similar results, although just before the event was logged, there is this Disk EventID 7:
- The device, \Device\Harddisk0\DR0, has a bad block.
Then I ran a
- chkdsk /b /r c:
Which resulted in a ton of deleting of corrupt attributes, so many that it appears the log is truncated. And this seems like about when programs started seriously failing, and I am having serious issues using the machine..
I ran a couple of chkdsk's from within windows using the Tools tab on the drive properties, which gives me the indices and "no problems found" messages, and another one of these:
- The driver detected a controller error on \Device\Harddisk2\DR2.
All of this is in the events that are linked to above.
I ran the disk diagnostics app from Western Digital, which passed the quick and extended scans. HDTune passed the quick scan and is still green most of the way through a full scan.
I also ran sfc, which seemed to be unable to fix anything. I get the same results if I run it again:
C:\Users\khastie>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 them.
Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
C:\Windows\Logs\CBS\CBS.log
And here is the gist of what was returned in the CBS.log:
2011-01-08 19:45:35, Info CSI 00000307 [SR] Repairing 4 components
2011-01-08 19:45:35, Info CSI 00000308 [SR] Beginning Verify and Repair transaction
2011-01-08 19:45:35, Info CSI 0000030a [SR] Cannot repair member file [l:30{15}]"poqexec.exe.mui" of Microsoft-Windows-ServicingStack.Resources, Version = 6.1.7600.16385, 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 in the store, hash mismatch
2011-01-08 19:45:35, Info CSI 0000030c [SR] Cannot repair member file [l:24{12}]"explorer.exe" of Microsoft-Windows-explorer, Version = 6.1.7600.16450, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2011-01-08 19:45:35, Info CSI 0000030e [SR] Cannot repair member file [l:24{12}]"WerFault.exe" of Microsoft-Windows-ErrorReportingFaults, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2011-01-08 19:45:35, Info CSI 00000310 [SR] Cannot repair member file [l:22{11}]"jsproxy.dll" of Microsoft-Windows-IE-ClientNetworkProtocolImplementation, Version = 8.0.7600.16700, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2011-01-08 19:45:35, Info CSI 00000312 [SR] Cannot repair member file [l:24{12}]"explorer.exe" of Microsoft-Windows-explorer, Version = 6.1.7600.16450, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2011-01-08 19:45:35, Info CSI 00000313 [SR] This component was referenced by [l:150{75}]"Package_2_for_KB977074~31bf3856ad364e35~amd64~~6.1.1.1.977074-4_neutral_GDR"
2011-01-08 19:45:35, Info CSI 00000316 [SR] Could not reproject corrupted file [ml:48{24},l:46{23}]"\??\C:\Windows\SysWOW64"\[l:24{12}]"explorer.exe"; source file in store is also corrupted
2011-01-08 19:45:35, Info CSI 00000318 [SR] Cannot repair member file [l:22{11}]"jsproxy.dll" of Microsoft-Windows-IE-ClientNetworkProtocolImplementation, Version = 8.0.7600.16700, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2011-01-08 19:45:35, Info CSI 00000319 [SR] This component was referenced by [l:156{78}]"Package_4_for_KB2416400~31bf3856ad364e35~amd64~~6.1.1.2.2416400-19_neutral_GDR"
2011-01-08 19:45:35, Info CSI 0000031c [SR] Could not reproject corrupted file [ml:48{24},l:46{23}]"\??\C:\Windows\SysWOW64"\[l:22{11}]"jsproxy.dll"; source file in store is also corrupted
2011-01-08 19:45:35, Info CSI 0000031e [SR] Cannot repair member file [l:24{12}]"WerFault.exe" of Microsoft-Windows-ErrorReportingFaults, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2011-01-08 19:45:35, Info CSI 0000031f [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.WindowsFoundationDelivery"
2011-01-08 19:45:35, Info CSI 00000322 [SR] Could not reproject corrupted file [ml:48{24},l:46{23}]"\??\C:\Windows\SysWOW64"\[l:24{12}]"WerFault.exe"; source file in store is also corrupted
2011-01-08 19:45:35, Info CSI 00000324 [SR] Cannot repair member file [l:30{15}]"poqexec.exe.mui" of Microsoft-Windows-ServicingStack.Resources, Version = 6.1.7600.16385, 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 in the store, hash mismatch
2011-01-08 19:45:35, Info CSI 00000325 [SR] This component was referenced by [l:266{133}]"Microsoft-Windows-WindowsFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.1.7600.16385.Windows Foundation Language Pack"
2011-01-08 19:45:35, Info CSI 00000328 [SR] Could not reproject corrupted file [ml:520{260},l:58{29}]"\??\C:\Windows\System32\en-US"\[l:30{15}]"poqexec.exe.mui"; source file in store is also corrupted
2011-01-08 19:45:35, Info CSI 0000032a [SR] Repair complete
2011-01-08 19:45:36, Info CSI 0000032b [SR] Committing transaction
2011-01-08 19:45:36, Info CSI 0000032f [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired
Should I try to do a SysRestore back to before I started having problems (it would be about 25 restore points back, on 12/16/10)? Seems like a bad idea, especially with a corrupt disk, and behavior like I describe in this very detailed post (mostly related to the bad RAM stick, but still very relevant to this current post).
It seems like I should just try reformatting and reinstalling windows (although if I am going to do that, why not give SysRestore a shot first anyway?)
But am I showing signs of having not only had a bad stick of RAM but also a failing drive? Aaargh, I tried to buy hi-quality parts for my first home-built system specifically to avoid this! Ah well - I'd just like some help in determining whether or not to send the drive back on warranty or whether I have a shot at recovery (which looks doubtful at this point).
Thanks in advance,
kghastie
Quote