BSOD Not sure why

Missfitt5555

Reputable
Mar 9, 2014
19
0
4,510
Edit: Just BSOD today the file is here ->>>>https://www.mediafire.com/?3tpyvyl2rhqxygv
Alright so recently I've been getting a BSOD the error code is pretty consistent.
7A
6fc40009850
c000000e
1137dc860
8800136a760
The BSOD only happens sometimes, while I am playing games (Fallout:New Vegas, League of Legends have been common) I freeze up and it can last from 5 seconds - a couple of minutes or the BSOD just happens. I have done a fresh install of Windows 7 home prem X64 and it is still happening. I've updated all my drivers the the most current ones and have also reverted my GPU drivers to see if it worked. (made them currentwhen it didn't) I'm completely stumped when it comes to BSOD and what not. I've checked my computer making sure everything was hooked up properly.
No overclocking has been done at all. I have constantly monitored the temps and they are average 40-60.

These are the files I found in windows/minidump
https://www.mediafire.com/?4mdad95kc4nnz7n

Computer Specs
GTX 570
2 TB seagate
Gigabyte GA-Z68A-D3H-B3
i7 2700k 3.5 GHz 4 core

If you need anything else like files or specs I would be glad to get it for you.


 
and your gaming,im mean it going to BOSD when on heavy load so we need stress test..usually BOSD shows up cause of faulty memory,but your system do freeze can be lot of other things.step by step need check every possibility.your wanna monitor temperatures under heavy load or run like prime 95 test which takes some time,gaming is good stress test.

 
edit: you can also get this bugcheck because of sleep support that is incorrect. (do BIOS and cpu chipset driver update to fix)
------
your system is only slightly overclocked. I don't think it would be the cause of this failure.
the system bugchecked in csrss.exe windows client servers runtime subsystem
This is a key windows file, if it detects that its data or code is corrupted it will call a bugcheck. It is often the target of malware. check for filesystem corruption with chkdsk /r /f
check for file corruption with the system file check utility.
(run cmd.exe as a admin, then run sfc.exe /scannow)

---------------
You could also get this error with bad physical ram. (run memtest86 to test)

I would run a malwarebytes scan, but the corruption may also be coming from another driver installed on your system.
I looked at the drivers and the only really obvious problem I see with your drivers is the very old network drivers from 2009 for your real network ethernet card. The nvidia streaming software you have installed may have problems with bugs in this very old ethernet driver. The bugs may cause memory corruption that windows detected as a malware attack and shut down.

you might also update this driver
\SystemRoot\system32\drivers\CAHS164.sys Tue Jun 29 04:06:02 2010
C-Media Electronics USB Audio Driver

various old USB drivers tend to corrupt memory

you also have a old BIOS but I don't think it is a problem but you might want to update if you can. You have a very old 2009 microcode update loaded for windows, you might want to install the current intel chipset drivers to get it updated.
https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=20775

the bugcheck code in the mini dump was
BugCheck F4, {3, fffffa8008c82b30, fffffa8008c82e10, fffff800037ca270}

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.

looks like csrss.exe attempted to access a bad memory location.


machine BIOS info:
BIOS Version F11
BIOS Release Date 10/12/2011
Manufacturer Gigabyte Technology Co., Ltd.
Product Name Z68A-D3H-B3
Processor Manufacturer Intel
Processor ID a7060200fffbebbf
Processor Version Intel(R) Core(TM) i7-2700K CPU
Processor Voltage 8ah - 1.0V
External Clock 100MHz
Max Speed 4000MHz
Current Speed 3600MHz









 

Missfitt5555

Reputable
Mar 9, 2014
19
0
4,510


I have updated my lan drivers, updated the chipset and bios, the C-Media driver I couldn't find in my drivers folder I recently uninstalled a couple of programs may have removed that with it. I have ran chkdsk /f /r while I was sleeping (does it automatically repair if it finds a problem), I also ran sfc.exe /scannow. I've ran memtest, I let it do 2 passes and 0 errors have accrued, though the problem is still there. Could it possibly be my HDD?