Random freezes and/or BSOD with general use

aritra2116 said:

Ok, so if it has to do with system files, then I guess repair install is the best thing to do but before that, have you done malware scans recently? If yes, then do a Custom Scan with Malwarebytes and select all the drives. If it finds anything, quarantine it and post the log it makes. After that, do this.

Repair Install

Oddly enough Malwarebytes won't install on my laptop. I have attached 2 screen captures of the errors I get while installing. After installation is complete and I go to launch the program it immediately crashes.

NoelDP said:

There is NO obvious need for a repair install - or worse, a clean install.

The SFC scan showed the following problem...

Code:

2014-07-21 11:37:53, Info                  CSI    00000304 [SR] Repairing 1 components
2014-07-21 11:37:53, Info                  CSI    00000305 [SR] Beginning Verify and Repair transaction
2014-07-21 11:37:53, Info                  CSI    00000306 Manifest hash for component [ml:280{140},l:184{92}]"amd64_a69ab2e06a57e0c36f0741338d888e44_31bf3856ad364e35_7.1.7601.18351_none_168d02fc611e1de8" does not match expected value. 
 Expected:{l:32 b:8571f9bcf4e096687cf1401f625f0e93afa381a54da316375ed2fad5290781ae}
 Found:{l:32 b:1c56c84448dec77bece6d3d7b129c32479b966d5d0d2187e52f63778750cda4e}.
2014-07-21 11:37:53, Info                  CSI    00000307 Unable to load manifest for component [ml:280{140},l:184{92}]"amd64_a69ab2e06a57e0c36f0741338d888e44_31bf3856ad364e35_7.1.7601.18351_none_168d02fc611e1de8"
2014-07-21 11:37:53, Info                  CSI    00000308 [SR] Cannot verify component files for a69ab2e06a57e0c36f0741338d888e44, Version = 7.1.7601.18351, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
2014-07-21 11:37:53, Info                  CSI    00000309 Repair results created:
POQ 129 starts:
 
POQ 129 ends.
2014-07-21 11:37:53, Info                  CSI    0000030a [SR] Repair complete
2014-07-21 11:37:53, Info                  CSI    0000030b [SR] Committing transaction

This may be the tip of the iceberg -


Please download and save the CheckSUR tool from http://support.microsoft.com/kb/947821
(you'll need to look in the details for Windows 7, downloading from the Microsoft Download Center)

Run it - The tool can take anywhere from 5 mins to a couple of hours to run (or 'Install') depending on how much it has to do, and may exit silently - it may appear to freeze for most of that time, but be patient.
The result is logged in the C:\Windows\Logs\CBS\CheckSUR.log file - and an archive …\checksur.persist.log file

Then zip the CheckSUR.log and upload it to your reply.

I don't mind doing a repair/clean install but if you suggest it is soemthing else I will do this and report back shortly.

NoelDP said:

There is NO obvious need for a repair install - or worse, a clean install.

The SFC scan showed the following problem...

Code:

2014-07-21 11:37:53, Info                  CSI    00000304 [SR] Repairing 1 components
2014-07-21 11:37:53, Info                  CSI    00000305 [SR] Beginning Verify and Repair transaction
2014-07-21 11:37:53, Info                  CSI    00000306 Manifest hash for component [ml:280{140},l:184{92}]"amd64_a69ab2e06a57e0c36f0741338d888e44_31bf3856ad364e35_7.1.7601.18351_none_168d02fc611e1de8" does not match expected value. 
 Expected:{l:32 b:8571f9bcf4e096687cf1401f625f0e93afa381a54da316375ed2fad5290781ae}
 Found:{l:32 b:1c56c84448dec77bece6d3d7b129c32479b966d5d0d2187e52f63778750cda4e}.
2014-07-21 11:37:53, Info                  CSI    00000307 Unable to load manifest for component [ml:280{140},l:184{92}]"amd64_a69ab2e06a57e0c36f0741338d888e44_31bf3856ad364e35_7.1.7601.18351_none_168d02fc611e1de8"
2014-07-21 11:37:53, Info                  CSI    00000308 [SR] Cannot verify component files for a69ab2e06a57e0c36f0741338d888e44, Version = 7.1.7601.18351, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
2014-07-21 11:37:53, Info                  CSI    00000309 Repair results created:
POQ 129 starts:
 
POQ 129 ends.
2014-07-21 11:37:53, Info                  CSI    0000030a [SR] Repair complete
2014-07-21 11:37:53, Info                  CSI    0000030b [SR] Committing transaction

This may be the tip of the iceberg -


Please download and save the CheckSUR tool from http://support.microsoft.com/kb/947821
(you'll need to look in the details for Windows 7, downloading from the Microsoft Download Center)

Run it - The tool can take anywhere from 5 mins to a couple of hours to run (or 'Install') depending on how much it has to do, and may exit silently - it may appear to freeze for most of that time, but be patient.
The result is logged in the C:\Windows\Logs\CBS\CheckSUR.log file - and an archive …\checksur.persist.log file

Then zip the CheckSUR.log and upload it to your reply.

Here is CheckSUR.log file

NoelDP said:

Great - CheckSUR fixed a few problems - all that it could find, anyhow.
Now run the SFC /SCANNOW again, and post the now CBS.log file (copy it to the desktop, then compress it before uploading it to your reply) - the sfcdetails file you posted earlier doesn't contain any of the background detail we may need.

SFC /SCANNOW reported that nothing is wrong. Attached is the compressed CBS.log file.

EDIT: Malwarebytes still crashes upon opening.

NoelDP said:

The CBS.log looks fine to me.

If we're lucky, then that's fixed the underlying problem, and the BSOD guys can take over and sort the rest

Back to you, guys

Thanks a ton!! Everything seems to be working just fine for right now. No random freezes or lockups and haven't encountered any BSODs. Am going to run DV for another 24 hours straight to do some more testing. Will check back shortly.