Sign in with
Sign up | Sign in
Your question

Blue screen just now, with report

Last response: in Components
Share
May 19, 2011 1:47:19 AM

got a blue screen and shutdown while in crysis, got this report after rebooting into windows

Problem signature:
Problem Event Name: BlueScreen

Additional information about the problem:
BCCode: 116
BCP1: FFFFFA800502C4E0
BCP2: FFFFF88003CADDCC
BCP3: 0000000000000000
BCP4: 0000000000000002
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\051811-30888-01.dmp
C:\Users\me\AppData\Local\Temp\WER-46893-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0...

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

More about : blue screen report

May 19, 2011 2:03:41 AM

could you try a memtest to see if it is the ram?
m
0
l
May 19, 2011 5:04:24 PM

i have to question the thoroughness of memtest. ive used it twice and didn't find anything. The CPU, RAM, and Vid card are the only things that havent been RMA'd to fix this problem
m
0
l
Related resources
May 19, 2011 5:18:48 PM

Blue Screen Error Code #4 – STOP 0x000000C2 or BAD_POOL_CALLER
Does it mention bad_pool_caller on your blue screen?
m
0
l
May 19, 2011 5:19:28 PM

I still think you should try to use memtest again and see how it goes.
m
0
l
May 26, 2011 11:41:50 AM

after running for 9 hours on only 2 sticks it found errors. im wondering if the mobo could give these errors
m
0
l
May 26, 2011 12:03:37 PM

from what i have found elsewhere it boiles down to your gfx card. the driver has not been able to restart after it failed. this could be caused by a hardware fault on the gfx card, whether it just be a heat issue or a voltage issue. if your gfx is overclocked remove it, if its a factory oc then drop it down to stock for that card and see if the problem persists.
if it is a failed driver you should see a refrence to it in the event logs. if there was enough time between the driver crash and the bsod.
m
0
l
!