Random BSOD's want to figure this out once and for all

Your external drive was in worse shape, actually. It had some bad clusters that had to be re-mapped. Hard drives come with extra sectors/clusters for this purpose. If bad clusters are found, they are replaced by the extra clusters. If a drive is mechanically failing in such a way that the head is wiping out clusters by physically running into them, eventually the extra clusters end up being used up and the drive stops being able to function properly. This results in a catastrophic hard disk failure.

In your case, it does not appear the drive is failing, but to be sure, you should run the disk check again with both boxes checked and look for the line: Adding XX bad clusters to the Bad Clusters File. Where XX is the number of bad clusters found.

Ok well here is the second disk check for my Hitachi drive. This one looks a little bit better.

Code:

Chkdsk was executed in read/write mode.  

Checking file system on F:
Volume label is Hitachi.

CHKDSK is verifying files (stage 1 of 5)...
  146176 file records processed.                                          File verification completed.
  61 large file records processed.                                      0 bad file records processed.                                        0 EA records processed.                                              0 reparse records processed.                                       CHKDSK is verifying indexes (stage 2 of 5)...
  166758 index entries processed.                                         Index verification completed.


CHKDSK is verifying security descriptors (stage 3 of 5)...
  146176 file SDs/SIDs processed.                                         Cleaning up 1 unused index entries from index $SII of file 0x9.
Cleaning up 1 unused index entries from index $SDH of file 0x9.
Cleaning up 1 unused security descriptors.
Security descriptor verification completed.
  10292 data files processed.                                            CHKDSK is verifying Usn Journal...
  34188224 USN bytes processed.                                             Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
  146160 files processed.                                                 File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
  3957342 free clusters processed.                                         Free space verification is complete.
Windows has checked the file system and found no problems.

 195350368 KB total disk space.
 179213204 KB in 132998 files.
     55676 KB in 10293 indexes.
    251996 KB in use by the system.
     65536 KB occupied by the log file.
  15829368 KB available on disk.

      4096 bytes in each allocation unit.
  48837592 total allocation units on disk.
   3957342 allocation units available on disk.

Sorry I took a while to respond, but in the meantime I installed more RAM and a new 1 Terabyte drive. I also moved some data over from my other drives so they have a lot more free space now. Hopefully this should make them a little more stable too.

What else can I do for now to try to make my system more stable?

Thanks for the help and for looking at my logs.

See how things go for now. Report back after a few days of doing your normal routine and let us know how the system is responding. More steps to improve stability may not be necessary if the system is already stable after the steps that have already been done.

Well I did have a random BlueScreen yesterday which I think shows that it's still not completely stable. And for some reason I still can't get SP1 to install.

But besides that my HDD's seem to be a little more reliable since they have a lot more free space now. I'm going to do some disk monitoring and diagnosis just to be safe though. Probably using Acronis or WD Utilities and Seatools.

By the way did my jcgriff2 report reveal any other useful information if you can recall?

The only thing that stood out was the hard disk problem of being too corrupt to be usable. Since you cannot get SP1 to install:

• Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.

writhziden said:

The only thing that stood out was the hard disk problem of being too corrupt to be usable. Since you cannot get SP1 to install:

• Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.

Running the sfc /scannow command from an elevated command prompt works but it never gets to completely finish and make it up to 100%.

It keeps geiving the error "Windows Resource Protection could not perform the requested operation."

Should I keep trying till it makes it up to 100% (which I'm sure will take me probably 50 times or so), or should I run the SFC command in the command prompt at boot using a Windows repair CD?

Or maybe a different technique is recommended?

Try sfc /verifyonly and post back the results.

It needs to be run in an Elevated Command Prompt as with the /scannow switch.

Ok well I guess it went a lot faster than I thought. I did the command with the /verifyonly switch which completed 100% and then with just the /scannow switch.

For some reason the CBS.log file is only 894 KB right now, but I could've sworn it was around 15 MB before I did the scan. Strange.

Anyway here's the current CBS.log file in its entirety

Tried to post it but I guess it was too big. Waited for the server to upload but it timed out several times so I'll just attach it instead.

Code:

2012-03-26 22:04:16, Info                  CSI    00000075 [SR] Verifying 100 (0x0000000000000064) components
2012-03-26 22:04:16, Info                  CSI    00000076 [SR] Beginning Verify and Repair transaction
2012-03-26 22:04:16, Info                  CSI    00000078 [SR] Cannot repair member file [l:20{10}]"IMJPPD.CHM" of Microsoft-Windows-Desktop_Technologies-Text_Input_Services-IME-Japanese-Help, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-03-26 22:04:17, Info                  CSI    0000007a [SR] Cannot repair member file [l:20{10}]"IMJPPD.CHM" of Microsoft-Windows-Desktop_Technologies-Text_Input_Services-IME-Japanese-Help, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-03-26 22:04:17, Info                  CSI    0000007b [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.WindowsFoundationDelivery"
2012-03-26 22:04:17, Info                  CSI    0000007e [SR] Could not reproject corrupted file [ml:520{260},l:62{31}]"\??\C:\Windows\IME\IMEJP10\HELP"\[l:20{10}]"IMJPPD.CHM"; source file in store is also corrupted
2012-03-26 22:04:18, Info                  CSI    00000080 [SR] Verify complete

2012-03-26 22:04:23, Info                  CSI    00000095 [SR] Verifying 100 (0x0000000000000064) components
2012-03-26 22:04:23, Info                  CSI    00000096 [SR] Beginning Verify and Repair transaction
2012-03-26 22:04:24, Info                  CSI    00000098 [SR] Cannot repair member file [l:20{10}]"msyhbd.ttf" of Microsoft-Windows-Font-TrueType-MicrosoftYaHeiBold, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-03-26 22:04:25, Info                  CSI    00000099 [SR] Repaired file \SystemRoot\WinSxS\Manifests\\[l:20{10}]"msyhbd.ttf" by copying from backup
2012-03-26 22:04:25, Info                  CSI    0000009b [SR] Cannot repair member file [l:20{10}]"msyhbd.ttf" of Microsoft-Windows-Font-TrueType-MicrosoftYaHeiBold, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-03-26 22:04:25, Info                  CSI    0000009c [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.WindowsFoundationDelivery"
2012-03-26 22:04:26, Info                  CSI    0000009f [SR] Could not reproject corrupted file [ml:520{260},l:40{20}]"\??\C:\Windows\fonts"\[l:20{10}]"msyhbd.ttf"; source file in store is also corrupted
2012-03-26 22:04:27, Info                  CSI    000000a3 [SR] Verify complete

2012-03-26 22:04:27, Info                  CSI    000000a4 [SR] Verifying 100 (0x0000000000000064) components
2012-03-26 22:04:27, Info                  CSI    000000a5 [SR] Beginning Verify and Repair transaction
2012-03-26 22:04:29, Info                  CSI    000000a7 [SR] Cannot repair member file [l:16{8}]"msyh.ttf" of Microsoft-Windows-Font-TrueType-MicrosoftYaHei, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-03-26 22:04:30, Info                  CSI    000000c8 [SR] Cannot repair member file [l:16{8}]"msyh.ttf" of Microsoft-Windows-Font-TrueType-MicrosoftYaHei, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-03-26 22:04:30, Info                  CSI    000000c9 [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.WindowsFoundationDelivery"
2012-03-26 22:04:31, Info                  CSI    000000cc [SR] Could not reproject corrupted file [ml:520{260},l:40{20}]"\??\C:\Windows\fonts"\[l:16{8}]"msyh.ttf"; source file in store is also corrupted
2012-03-26 22:04:32, Info                  CSI    000000ce [SR] Verify complete

2012-03-26 22:04:32, Info                  CSI    000000cf [SR] Verifying 100 (0x0000000000000064) components
2012-03-26 22:04:32, Info                  CSI    000000d0 [SR] Beginning Verify and Repair transaction
2012-03-26 22:04:33, Info                  CSI    000000d2 [SR] Cannot repair member file [l:24{12}]"daunpenh.ttf" of Microsoft-Windows-Font-TrueType-DaunPenh, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-03-26 22:04:33, Info                  CSI    000000d4 [SR] Cannot repair member file [l:16{8}]"kaiu.ttf" of Microsoft-Windows-Font-TrueType-DFKaiSB, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-03-26 22:04:36, Info                  CSI    000000d6 [SR] Cannot repair member file [l:16{8}]"kaiu.ttf" of Microsoft-Windows-Font-TrueType-DFKaiSB, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-03-26 22:04:36, Info                  CSI    000000d7 [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.WindowsFoundationDelivery"
2012-03-26 22:04:37, Info                  CSI    000000d8 [SR] Repaired file \SystemRoot\WinSxS\Manifests\\[l:24{12}]"daunpenh.ttf" by copying from backup
2012-03-26 22:04:37, Info                  CSI    000000da [SR] Repairing corrupted file [ml:520{260},l:40{20}]"\??\C:\Windows\fonts"\[l:24{12}]"daunpenh.ttf" from store
2012-03-26 22:04:37, Info                  CSI    000000dc [SR] Verify complete

2012-03-26 22:04:45, Info                  CSI    000000ef [SR] Verifying 100 (0x0000000000000064) components
2012-03-26 22:04:45, Info                  CSI    000000f0 [SR] Beginning Verify and Repair transaction
2012-03-26 22:04:47, Info                  CSI    000000f2 [SR] Cannot repair member file [l:22{11}]"PINTLGT.IMD" of Microsoft-Windows-IME-Simplified-Chinese-TrigramDictionary, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-03-26 22:04:48, Info                  CSI    000000f6 [SR] Cannot repair member file [l:22{11}]"PINTLGT.IMD" of Microsoft-Windows-IME-Simplified-Chinese-TrigramDictionary, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-03-26 22:04:48, Info                  CSI    000000f7 [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.WindowsFoundationDelivery"
2012-03-26 22:04:50, Info                  CSI    000000fa [SR] Could not reproject corrupted file [ml:520{260},l:62{31}]"\??\C:\Windows\IME\IMESC5\DICTS"\[l:22{11}]"PINTLGT.IMD"; source file in store is also corrupted
2012-03-26 22:04:50, Info                  CSI    000000fc [SR] Verify complete

2012-03-26 22:05:01, Info                  CSI    00000121 [SR] Verifying 100 (0x0000000000000064) components
2012-03-26 22:05:01, Info                  CSI    00000122 [SR] Beginning Verify and Repair transaction
2012-03-26 22:05:02, Info                  CSI    00000124 [SR] Cannot repair member file [l:24{12}]"imageres.dll" of Microsoft-Windows-imageres, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-03-26 22:05:05, Info                  CSI    00000125 [SR] Repaired file \SystemRoot\WinSxS\Manifests\\[l:24{12}]"imageres.dll" by copying from backup
2012-03-26 22:05:05, Info                  CSI    00000127 [SR] Cannot repair member file [l:24{12}]"imageres.dll" of Microsoft-Windows-imageres, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-03-26 22:05:05, Info                  CSI    00000128 [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.WindowsFoundationDelivery"
2012-03-26 22:05:06, Info                  CSI    0000012b [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:24{12}]"imageres.dll"; source file in store is also corrupted
2012-03-26 22:05:06, Info                  CSI    0000012d [SR] Verify complete

And that was only about 10% of the corruption that is occurring on your system. I strongly advise that you Repair Install Windows 7 ASAP.