Windows 7 x64 BSOD every couple of hours when idling.

Shift209

Honorable
Aug 17, 2013
10
0
10,510
Hi, I've been getting blue screened every couple of hours when my computer is idle and it just happened for the first time while in game. Not very savvy when it comes to these sort of things so I was hoping for some help on here, it would be much appreciated :).

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF800032CF85E
BCP3: FFFFF8800C8B5F40
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\011014-4602-01.dmp
C:\Users\Omar\AppData\Local\Temp\WER-5959-0.sysdata.xml



i7-4770k
16gb 2133ddr3 1.65v ram
Gtx 780
Corsair RM750
MSI G45 Motherboard

 

FreezeRay

Honorable
Jan 1, 2014
126
0
10,710
3b is a graphics driver problem if I remember right. Pop open your case, and remove all devices in your PCI/e slots, clean any dust off them, and firmly reseat them in the lanes. After you do that make sure you have the LATEST drivers installed for all your PCI/e devices.
 

Shift209

Honorable
Aug 17, 2013
10
0
10,510


Cleaned em off, firmly reseated them, did a clean removal of my drivers then updated to the latest ones. My PC's restarted once in game (no bluescreen or problem details on reboot) then blue screened again today while just browsing the internet

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 50
BCP1: FFFFF900C4227CF0
BCP2: 0000000000000000
BCP3: FFFFF9600030C69D
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

The BCCode's different this time it seems
 

FreezeRay

Honorable
Jan 1, 2014
126
0
10,710
I'm pretty sure that BCCode indicates hardware failure, defective hardware, or possibly faulty RAM. Very odd. Is it possible for you to remove individual components and test with known good hardware to see if you could possibly isolate the issue? I'd also suggest running Memtest86 for a few hours to see if there is any problem with you RAM sticks, to at least eliminate that as a possible problem.