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).

1. Disk-related events from the last several months (EVTX file)
   
2. "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

Test your HDD with Seatools
| Seagate

yowanvista said:

Test your HDD with Seatools
| Seagate

Click to expand...

OK, and so it passed the SeaTools Quicktest, and I'll run the long test after HDTune's extended test is done (it's close and so far has found no errors). So assuming I get no errors with SeaTools, what then?

Can you run CrystalDiskInfo too, and post the reuslts here?

SeaTools passed the Long Driver Status test as well now. So I have now run a dozen chkdsks, sfc, HDTune, SeaTools and the Western Digital diagnostics tool. Is there something in particular that CrystalDisk might tell me that is different than the others?

Crystal Disk reads and displays the S.M.A.R.T. Status of your drive as well as the drive temperature
I'm sure it can't hurt to check from a "different Angle"

But if you are so concerned, back up the drive, reformat it (not Quickformat!) restore it with the backup
and see if it's still funky...if so get your warranty slip and RMA the drive

-DG

I didn't see a test to run w/CD, but here is the drive status:

----------------------------------------------------------------------------
CrystalDiskInfo 3.10.0 (C) 2008-2010 hiyohiyo
Crystal Dew World : Crystal Dew World
----------------------------------------------------------------------------

OS : Windows 7 Home Premium Edition [6.1 Build 7600] (x64)
Date : 2011/01/09 12:02:30

-- Controller Map ----------------------------------------------------------
+ Intel(R) 5 Series/3400 Series Chipset Family 4 port Serial ATA Storage Controller - 3B20 [ATA]
+ ATA Channel 0 (0)
- ATAPI iHAS224 Y ATA Device
+ ATA Channel 1 (1)
- WDC WD1001FALS-00J7B0 ATA Device
+ Intel(R) 5 Series/3400 Series Chipset Family 2 port Serial ATA Storage Controller - 3B26 [ATA]
- ATA Channel 0 (0)
- ATA Channel 1 (1)
+ Standard Dual Channel PCI IDE Controller [ATA]
- ATA Channel 0 (0)
+ ATA Channel 1 (1)
- Marvell 91xx Config Device
+ Standard Dual Channel PCI IDE Controller [ATA]
- ATA Channel 0 (0)
- ATA Channel 1 (1)

-- Disk List ---------------------------------------------------------------
(1) WDC WD1001FALS-00J7B0 : 1000.2 GB [0-5-1, pd1]
(2) ST9500325AS : 500.1 GB [1-X-X, sa1] (V=059B, P=047B)
(3) ST3320820A : 320.0 GB [2-X-X, cy1] (V=059B, P=007E)

----------------------------------------------------------------------------
(1) WDC WD1001FALS-00J7B0
----------------------------------------------------------------------------
Model : WDC WD1001FALS-00J7B0
Firmware : 05.00K05
Serial Number : WD-WMATV7068715
Disk Size : 1000.2 GB (8.4/137.4/1000.2)
Buffer Size : 32767 KB
Queue Depth : 32
# of Sectors : 1953525168
Rotation Rate : Unknown
Interface : Serial ATA
Major Version : ATA8-ACS
Minor Version : ----
Transfer Mode : SATA/300
Power On Hours : 3397 hours
Power On Count : 136 count
Temparature : 43 C (109 F)
Health Status : Good
Features : S.M.A.R.T., AAM, 48bit LBA, NCQ
APM Level : ----
AAM Level : 80FEh [OFF]

-- S.M.A.R.T. --------------------------------------------------------------
ID Cur Wor Thr RawValues(6) Attribute Name
01 200 200 _51 000000000002 Read Error Rate
03 230 229 _21 000000002134 Spin-Up Time
04 100 100 __0 000000000099 Start/Stop Count
05 200 200 140 000000000000 Reallocated Sectors Count
07 200 200 __0 000000000000 Seek Error Rate
09 _96 _96 __0 000000000D45 Power-On Hours
0A 100 100 __0 000000000000 Spin Retry Count
0B 100 100 __0 000000000000 Recalibration Retries
0C 100 100 __0 000000000088 Power Cycle Count
C0 200 200 __0 00000000004A Power-off Retract Count
C1 200 200 __0 000000000099 Load/Unload Cycle Count
C2 107 102 __0 00000000002B Temperature
C4 200 200 __0 000000000000 Reallocation Event Count
C5 200 200 __0 000000000000 Current Pending Sector Count
C6 200 200 __0 000000000000 Uncorrectable Sector Count
C7 200 200 __0 000000000000 UltraDMA CRC Error Count
C8 200 200 __0 000000000000 Write Error Rate

-- IDENTIFY_DEVICE ---------------------------------------------------------
+0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F
000: 42 7A 3F FF C8 37 00 10 00 00 00 00 00 3F 00 00
010: 00 00 00 00 20 20 20 20 20 57 44 2D 57 4D 41 54
020: 56 37 30 36 38 37 31 35 00 00 FF FF 00 32 30 35
030: 2E 30 30 4B 30 35 57 44 43 20 57 44 31 30 30 31
040: 46 41 4C 53 2D 30 30 4A 37 42 30 20 20 20 20 20
050: 20 20 20 20 20 20 20 20 20 20 20 20 20 20 80 10
060: 00 00 2F 00 40 01 00 00 00 00 00 07 3F FF 00 10
070: 00 3F FC 10 00 FB 01 10 FF FF 0F FF 00 00 00 07
080: 00 03 00 78 00 78 00 78 00 78 00 00 00 00 00 00
090: 00 00 00 00 00 00 00 1F 07 06 00 00 00 44 00 40
0A0: 01 FE 00 00 74 6B 7F 61 41 23 74 69 BC 41 41 23
0B0: 20 7F 00 5E 00 5E 00 00 FF FE 00 00 80 FE 00 00
0C0: 00 00 00 00 00 00 00 00 6D B0 74 70 00 00 00 00
0D0: 00 00 00 00 00 00 00 00 50 01 4E E0 57 83 39 B3
0E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 40 10
0F0: 40 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00
100: 00 29 00 00 00 00 00 00 00 00 16 A0 00 00 00 00
110: 00 00 00 00 00 00 00 00 00 00 00 00 00 04 00 00
120: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
130: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
140: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
150: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
160: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
170: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
180: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
190: 00 00 00 00 00 00 00 00 00 00 00 00 30 37 00 00
1A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1B0: 00 00 00 00 00 00 00 00 00 00 00 00 10 0E 00 00
1C0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1D0: 00 00 00 00 00 01 10 00 00 00 00 00 00 00 00 00
1E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 8F A5

----------------------------------------------------------------------------
(2) ST9500325AS
----------------------------------------------------------------------------
Enclosure : ST950032 5AS USB Device (V=059B, P=047B, sa1)
Model : ST9500325AS
Firmware : 0002BSM1
Serial Number : 6VE21ZWN
Disk Size : 500.1 GB (8.4/137.4/500.1)
Buffer Size : 8192 KB
Queue Depth : 32
# of Sectors : 976773168
Rotation Rate : 5400 RPM
Interface : USB (Serial ATA)
Major Version : ATA8-ACS
Minor Version : ATA8-ACS version 4
Transfer Mode : SATA/150
Power On Hours : 816 hours
Power On Count : 100 count
Temparature : 33 C (91 F)
Health Status : Good
Features : S.M.A.R.T., APM, 48bit LBA, NCQ
APM Level : 8080h [ON]
AAM Level : ----

-- S.M.A.R.T. --------------------------------------------------------------
ID Cur Wor Thr RawValues(6) Attribute Name
01 117 _99 __6 0000083A751C Read Error Rate
03 _98 _98 __0 000000000000 Spin-Up Time
04 100 100 _20 000000000070 Start/Stop Count
05 100 100 _36 000000000000 Reallocated Sectors Count
07 _63 _60 _30 0000001C04B0 Seek Error Rate
09 100 100 __0 000000000330 Power-On Hours
0A 100 100 _97 000000000000 Spin Retry Count
0C 100 _37 _20 000000000064 Power Cycle Count
B8 100 100 _99 000000000000 End-to-End Error
BB 100 100 __0 000000000000 Reported Uncorrectable Errors
BC 100 _99 __0 000000000003 Command Timeout
BD 100 100 __0 000000000000 High Fly Writes
BE _67 _52 _45 000024170021 Airflow Temperature
BF 100 100 __0 000000000000 G-Sense Error Rate
C0 100 100 __0 00000000001F Power-off Retract Count
C1 _99 _99 __0 000000000C14 Load/Unload Cycle Count
C2 _33 _48 __0 000E00000021 Temperature
C3 _49 _45 __0 0000083A751C Hardware ECC recovered
C5 100 100 __0 000000000000 Current Pending Sector Count
C6 100 100 __0 000000000000 Uncorrectable Sector Count
C7 200 200 __0 000000000000 UltraDMA CRC Error Count

-- IDENTIFY_DEVICE ---------------------------------------------------------
+0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F
000: 0C 5A 3F FF C8 37 00 10 00 00 00 00 00 3F 00 00
010: 00 00 00 00 20 20 20 20 20 20 20 20 20 20 20 20
020: 36 56 45 32 31 5A 57 4E 00 00 40 00 00 04 30 30
030: 30 32 42 53 4D 31 53 54 39 35 30 30 33 32 35 41
040: 53 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20
050: 20 20 20 20 20 20 20 20 20 20 20 20 20 20 80 10
060: 00 00 2F 00 40 00 02 00 02 00 00 07 3F FF 00 10
070: 00 3F FC 10 00 FB 01 10 FF FF 0F FF 00 00 00 07
080: 00 03 00 78 00 78 00 78 00 78 00 00 00 00 00 00
090: 00 00 00 00 00 00 00 1F 05 02 00 00 00 48 00 40
0A0: 01 F0 00 29 34 6B 7D 09 61 23 34 69 BC 09 61 23
0B0: 40 7F 00 43 00 43 80 80 FF FE 00 00 FE 00 00 00
0C0: 00 00 00 00 00 00 00 00 60 30 3A 38 00 00 00 00
0D0: 00 00 00 00 00 00 00 00 50 00 C5 00 18 BD F4 C4
0E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 40 1E
0F0: 40 1C 00 00 00 00 00 00 00 00 00 00 00 00 00 00
100: 00 21 60 30 3A 38 60 30 3A 38 20 20 00 02 01 40
110: 01 00 50 00 3C 06 3C 0A 00 00 00 3C 00 00 00 08
120: 00 00 00 00 00 1F 02 80 00 00 00 00 00 08 00 00
130: 00 00 00 00 00 00 00 00 00 00 00 00 3C 00 80 00
140: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
150: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
160: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
170: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
180: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
190: 00 00 00 00 00 00 00 00 00 00 00 00 10 3B 00 00
1A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1B0: 00 00 15 18 00 00 00 00 00 00 00 00 10 10 00 00
1C0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1D0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 FE A5

----------------------------------------------------------------------------
(3) ST3320820A
----------------------------------------------------------------------------
Enclosure : ST332082 0A USB Device (V=059B, P=007E, cy1)
Model : ST3320820A
Firmware : 3.AAC
Serial Number : 5QF0WGD6
Disk Size : 320.0 GB (8.4/137.4/320.0)
Buffer Size : 8192 KB
Queue Depth : 1
# of Sectors : 625142448
Rotation Rate : Unknown
Interface : USB (Parallel ATA)
Major Version : ATA/ATAPI-7
Minor Version : ----
Transfer Mode : Ultra DMA/100
Power On Hours : 27764 hours
Power On Count : 36 count
Temparature : 51 C (123 F)
Health Status : Caution
Features : S.M.A.R.T., 48bit LBA
APM Level : ----
AAM Level : ----

-- S.M.A.R.T. --------------------------------------------------------------
ID Cur Wor Thr RawValues(6) Attribute Name
01 101 _89 __6 00000B497211 Read Error Rate
03 _96 _95 __0 000000000000 Spin-Up Time
04 100 100 _20 000000000020 Start/Stop Count
05 100 100 _36 000000000001 Reallocated Sectors Count
07 _89 _60 _30 000033A497B2 Seek Error Rate
09 _69 _69 __0 000000006C74 Power-On Hours
0A 100 100 _97 000000000000 Spin Retry Count
0C 100 100 _20 000000000024 Power Cycle Count
BB 100 100 __0 000000000000 Reported Uncorrectable Errors
BD 100 100 __0 000000000000 High Fly Writes
BE _49 _37 _45 0000362E0033 Airflow Temperature
C2 _51 _63 __0 001C00000033 Temperature
C3 _54 _46 __0 000009C1AC82 Hardware ECC recovered
C5 100 100 __0 000000000000 Current Pending Sector Count
C6 100 100 __0 000000000000 Uncorrectable Sector Count
C7 200 200 __0 00000000001D UltraDMA CRC Error Count
C8 100 253 __0 000000000000 Write Error Rate
CA 100 253 __0 000000000000 Data Address Mark Error

-- IDENTIFY_DEVICE ---------------------------------------------------------
+0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F
000: 0C 5A 3F FF C8 37 00 10 00 00 00 00 00 3F 00 00
010: 00 00 00 00 20 20 20 20 20 20 20 20 20 20 20 20
020: 35 51 46 30 57 47 44 36 00 00 40 00 00 04 33 2E
030: 41 41 43 20 20 20 53 54 33 33 32 30 38 32 30 41
040: 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20
050: 20 20 20 20 20 20 20 20 20 20 20 20 20 20 80 10
060: 00 00 2F 00 40 00 02 00 02 00 00 07 3F FF 00 10
070: 00 3F FC 10 00 FB 00 10 FF FF 0F FF 00 00 00 07
080: 00 03 00 78 00 78 00 F0 00 78 00 00 00 00 00 00
090: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0A0: 00 FE 00 00 34 6B 7D 01 40 23 34 69 3C 01 40 23
0B0: 10 3F 00 00 00 00 FE FE FF FE 40 4B D0 00 00 00
0C0: 00 00 00 00 00 00 00 00 EA B0 25 42 00 00 00 00
0D0: 00 00 00 00 40 00 00 00 00 00 00 00 00 00 00 00
0E0: 00 00 00 00 00 00 00 00 00 00 01 00 00 00 00 02
0F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
100: 00 01 EA B0 25 42 EA B0 25 42 20 20 00 02 02 B6
110: 00 00 00 8A 3C 06 3C 0A 00 00 07 C6 01 00 08 00
120: 0F 14 12 00 00 02 00 80 00 00 00 00 00 A0 02 02
130: 00 00 04 04 00 00 00 00 00 00 00 00 12 00 00 0B
140: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
150: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
160: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
170: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
180: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
190: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1C0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1D0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 DE A5

If there was anything wrong with the smart status, CD would have notified you (it simply reads out a piece of RAM which holds the readings of all sensors during the drive's life time)
Based on all the tests you ran so far I would say the hard drives (and to a certain degree the hard disk controller) are OK. The only thing I see: the Temperature your 3rd drive ST3320820A is a little high...not in an area to be concerned yet...but surely worth monitoring how it develops during a usual day.

Personally I would leave it at that for now but if you're really concerned, do what I mentioned before back it up and reformat the drive.

-DG

Yeah, I would love to leave it, but unfortunately there is definitely some corruption going on still. In the other post, there are more details on some corrupt system files. And also what about all those chkdsk errors? I'm still getting "Cleaning up indexes." What is that about? And what about the doozy of a chksdsk, part of which I'll repost here. Thoughts on trying System Restore versus a reformat?

Chkdsk:


Checking file system on C:
The type of the file system is NTFS.

One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 5)...
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x11ca34 for possibly 0x40 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x8843 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 34883.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x134845 for possibly 0x58 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x91a3 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 37283.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x1334b7 for possibly 0xa78 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0xe149 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 57673.
Attribute record of type 0x80 and instance tag 0x5 is cross linked
starting at 0x11a8b4 for possibly 0x3 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x5
in file 0xe24a is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 57930.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x11a8a8 for possibly 0xc clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0xe63f is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 58943.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x13188d for possibly 0x100 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0xf16b is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 61803.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x134719 for possibly 0x100 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0xfb3a is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 64314.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x131907 for possibly 0x115 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0xfc47 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 64583.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x134c25 for possibly 0x2c clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0xfdab is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 64939.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x1359af for possibly 0x809 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x14797 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 83863.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x134c54 for possibly 0x9 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x14ee4 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 85732.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x134c5d for possibly 0x4 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x14efe is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 85758.

****
and it goes on until it gets truncated...

You haven't filled out your sys specs yet so I ask you here..how old is your PSU and how many Amps do you have on the 12V rail?

All those cross linked clusters point towards power failure/power instability.

It just hit me...you have 3HDDs and god knows what else running so chances are your power supply is over stressed or simply at the brink...Still strong enough for POST but perhaps not stable enough anymore in the long run.
Come to think of it...it could have even been the cause for the old drive to fail (But of course that's pure speculation on my part)

-DG

OK, I'll post the specs. New build with quality parts as of this spring. I got a fairly discounted 500W CoolerMaster PSU which I thought would be more than adequate (only have one mid-low-grade Nvidia GT 240 GPU), and I did an online calc that said with some periphs plugged in I should use about 200W, so recommended at least 260W PSU (approx).

Also, I had everything unplugged for a while and was having problems, but that was probably my failed RAM that then seems likely to have corrupted the filesystem?

The two drives connected are 1 each AC/powered older Iomega and Seagate drives, and a USB-poweered newer USB iomega e-something.

I'll post specs in a sec but from what I have said, does it sound like it still would be power? I was under the impression that 400W would likely be more than I need, and I'm at 500.

OK I posted specs. I have a 500W CoolerMaster PSU that was pretty inexpensive (bad sign?). But I did an online power-req calculator and it said I was probably using 200W, and recommended like a 260W PSU. So shouldn't 500W be more than enough?

Also, I had everything unplugged when the first minor issues began, but of course they could be causing current problems. Basically all I have had plugged in is two fairly old 300GB drives that have A/C power, and a newer Iomega eGo portable USB drive with 2 USB plugs (no AC). Does that really sound like enough to cause issues?

You're right that doesn't look all that bad....so if it's not the PSU that causes those cross linked blocks...what then..the hard disk controller? I don't know...I'm running out of options, sorry.
As for your earlier question I would take re-format with backup restore. if you don't lose too much data in the process a clean install would also be a good option (it is your boot drive, we're talking about, right?)
if not then just save what you can and do a full format.

Found some info using vssadmin list shadows. Looks like this shadow copy, which is the last remaining one that continuously throws ntfs errors, was from the 19th, right about when things started to go south....

Almost definitely going to reinstall on Thursday when I have more time. I have one restore point pre-12/19, and I might think about rolling back to that one just to see what happens. I'm backed up and planning to reinst anyway...

Anyone know of a way to remove just this one shadow copy?

Contents of shadow copy set ID: {04028ce9-9c14-41e0-898d-a2073de046a9}
Contained 2 shadow copies at creation time: 12/19/2010 3:39:07 PM
Shadow Copy ID: {73f35717-2ef3-4a90-8a02-a646bee42a58}
Original Volume: (C\\?\Volume{2c3d4e5a-79c7-11df-a8e3-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy9
Originating Machine: megatron
Service Machine: megatron
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessibleWriters
Attributes: Persistent, Client-accessible, No auto release, Differential, Auto recovered

Also, that one happens to be at the same time as a Windows Backup I made. Here is a screenshot of the restore points.

I looks like that deleting my restore points would at least get rid of the ntfs error. And if that is the cause of superfetch failing, then there you go, that fixes my original problem. I am worried I still have a jacked up drive though, and might have corrupt files that I will not discover for a long time, so I probably should reinst anyway.

Before I do though, I want to either try Sys Restoring all the way back or removing the restore points, just to see if either one fixes at least some things or fail catastrophically. Torn between giving Sys Restore a shot vs just removing all shadow copies. Either one probably doesn't do me a whole lot of good, but I'd do it just pre-reinstall.

Any opinions on that?