Windows 7: BSOD while playing ME3 and DOTA2

Thanks for your time. To start off i have no idea what is causing the crashes. My only guess is that my computer is overheating but when i check the temp its usually at 56-57. i have run malwarebytes and M Security essentials anti virus and both have said that there is nothing

just had a system fatal error and another BSOD ill post another ZIP. Thanks for helping me

Hello Vexile and welcome to Sevenforums.

BSOD Analyse

Windows Update

Sftfslh.sys was blamed. It's a part of the Application Virtualization. There's a hotfix for this type of driver, and you can find it right below. Also make sure that you have every update from Windows Update.

Hotfix Package 7 Microsoft Application Virtualization

Windows Update - Hide or Restore Hidden Updates

SFC /scannow

We usually ask people to do this command to check if Windows is corrupted. It's the most common one used to check if the Windows files are corrupted. If it'll find errors, it'll restore them.



Press Start | search 'cmd' | Right-click it
| open as Admin | type SFC /SCANNOW

SFC /SCANNOW Command - System File Checker

Memory // RAM

Looking at your bugcheck it's likely that a memory corruption event was triggered. Though a driver could be causing the memory to be borked, but we're usually suggesting a memory test before moving forward. Do a scan with Memtest86+. Memtest is a scanner that'll check your sticks for errors.


To ensure that we'll know if it's the slots on the motherboard that's broken, or the sticks itself - we have a little procedure we'll recommend. Remove 1 stick, scan the other with Memtest in the current slot. After 7 passes, move the stick to another slot and scan, and so on and so forth until you've scanned all the sticks, and all the slots, one by one.

Memtest86+ - Advanced Memory Diagnostic Tool

Best Regards,
Frederik.

i had hoped that my BsoD had stopped but they have now started up again. the latest one i have gotten was a USB_bugcheck one and my computer will restart after playing a game for about 10 minuets. I have run that commant propmt verify and it shows that there are some that are corrupted and even after trying the repair it was not fixed

CSI 00000209 [SR] Cannot repair member file [l:20{10}]"catsrv.dll" of Microsoft-Windows-COM-ComPlus-Runtime-QFE, 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

2012-09-03 13:02:33, Info CSI 0000020d [SR] Cannot repair member file [l:20{10}]"catsrv.dll" of Microsoft-Windows-COM-ComPlus-Runtime-QFE, 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

2012-09-03 13:02:33, Info CSI 0000020e [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery"

2012-09-03 13:02:33, Info CSI 00000211 [SR] Could not reproject corrupted file [ml:48{24},l:46{23}]"\??\C:\Windows\SysWOW64"\[l:20{10}]"catsrv.dll"; source file in store is also corrupted

I have updated my Nvidia driver to the latest stable update, no beta. So i think it might be something to do with my usb

i have made a new zip of the sf info hopefully you guys can find something and thanks

Hello again

Combining your crash dumps and the general view of BSODs culprits, I'd suggest you to have a look at your memory, the sticks. Through decades people have been using the bootable tool called Memtest86+ and it's basically very unique in these manners.
Be sure to check your warranty rules and regulations before opening your case.

* Memtest86+ is USB-ready, and can be booted directly from it. Download the flashdrive wizard.
* To ensure that either your sticks OR your motherboard slots are broken, it's necessary to do the below procedure-
* Pull out all sticks except ONE, scan it.
* If no errors, pull the scanned stick into another slot.
* Proceed like this until you've scanned all sticks individually, and all the slots.

Best Regards,
Frederik.

i have done as you have said doing runs overnight and waking up every few hours to check the progress of the tests and change the position of the ram stick. The only problem that was found was when stick #2 was placed in slot 1, at about test 6 of pass 1 alot of errors were showing up, like 4000+. i have tested this slot with the other ram stick and it was fine testing it for about 5 passes.