BSOD when I'm gaming

#1
Hey, I'm hoping you guys can help me out! Please could someone take a look at my dump files and tell me what is up with my pc!?

I get the stop errors when playing games after maybe an hour of play. There are only two dump files because I re-installed windows to see if I could fix the problem myself - its still crashing obviously!

I'm thinking it may be a hdd problem because thats the only thing I've added recently but would at least like to know for sure. My cpu and graphics card are both factory overclocked and I use Avast!

Any light you guys can throw on this would be greatly appreciated, cheers! :confused:
 


RingAnimated

Well-Known Member
#3
Im not a pro at this, but it's not giving any file names for any of these. Please list the games you are playing with this BSOD and your Graphics Card(s). Being as you say gaming and it says in the DMP "A fatal hardware error has occurred" i think this could be the problem.


Dump 1...
******************************************************************************** *
* Bugcheck Analysis *
* *
*******************************************************************************


WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8004e06028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000005110a, Low order 32-bits of the MCi_STATUS value.


Debugging Details:
------------------


***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.




BUGCHECK_STR: 0x124_GenuineIntel


CUSTOMER_CRASH_COUNT: 1


DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT


CURRENT_IRQL: 0


STACK_TEXT:
fffff800`041a1a98 fffff800`03001a3b : 00000000`00000124 00000000`00000000 fffffa80`04e06028 00000000`be200000 : 0xfffff800`02a83c80
fffff800`041a1aa0 00000000`00000124 : 00000000`00000000 fffffa80`04e06028 00000000`be200000 00000000`0005110a : 0xfffff800`03001a3b
fffff800`041a1aa8 00000000`00000000 : fffffa80`04e06028 00000000`be200000 00000000`0005110a fffffa80`04c7bbd0 : 0x124




STACK_COMMAND: kb


FOLLOWUP_NAME: MachineOwner


MODULE_NAME: Unknown_Module


IMAGE_NAME: Unknown_Image


DEBUG_FLR_IMAGE_TIMESTAMP: 0


BUCKET_ID: CORRUPT_MODULELIST


Followup: MachineOwner
Dump 2...
******************************************************************************** *
* Bugcheck Analysis *
* *
*******************************************************************************


WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8004f3c028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.


Debugging Details:
------------------




BUGCHECK_STR: 0x124_GenuineIntel


CUSTOMER_CRASH_COUNT: 1


DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT


PROCESS_NAME: System


CURRENT_IRQL: f


STACK_TEXT:
fffff800`00ba8a98 fffff800`02a2ca3b : 00000000`00000124 00000000`00000000 fffffa80`04f3c028 00000000`be000000 : nt!KeBugCheckEx
fffff800`00ba8aa0 fffff800`02befb33 : 00000000`00000001 fffffa80`04f3dea0 00000000`00000000 fffffa80`04f3def0 : hal!HalBugCheckSystem+0x1e3
fffff800`00ba8ae0 fffff800`02a2c700 : 00000000`00000728 fffffa80`04f3dea0 fffff800`00ba8e70 fffff800`00ba8e00 : nt!WheaReportHwError+0x263
fffff800`00ba8b40 fffff800`02a2c052 : fffffa80`04f3dea0 fffff800`00ba8e70 fffffa80`04f3dea0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`00ba8c90 fffff800`02a2bf0d : 00000000`00000004 00000000`00000001 fffff800`00ba8ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`00ba8cd0 fffff800`02a1fe88 : fffffa80`05e46850 fffffa80`05e46810 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff800`00ba8d00 fffff800`02ade56c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`00ba8d30 fffff800`02ade3d3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`00ba8e70 fffff800`02ae7845 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff800`00b9c420 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiTimerWaitTest+0x55




STACK_COMMAND: kb


FOLLOWUP_NAME: MachineOwner


MODULE_NAME: hardware


IMAGE_NAME: hardware


DEBUG_FLR_IMAGE_TIMESTAMP: 0


FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE


BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE


Followup: MachineOwner
Both look very off, i have never seen or even heard of the Bug Check String "WHEA_UNCORRECTABLE_ERROR". Don't even understand what "whea" is here.
 


gerry74

New Member
#4
cheers for answering my post! The game is Saintsrow III. I have just discovered that the game seems to run fine (for now!) if I run the game in Directx 9 instead of 10 and 11. the graphics card is msi hd 6850 oc. It plays Fifa 12 with no problems so maybe gpu prob? I was hoping someone would be able to tell me exactly whats up from my dmp files before I start replacing hardware. I think whea stands for Windows Hardware Error Architecture if that helps any!
 


gerry74

New Member
#5
you guys seem inundated with stop errors on this forum, so you can close this thread now! I turned off my cpu's overclock (factory OC) and that seems to have did the trick.

If I get anymore BSOD's I'll be sure to come back and fry your heads again, cheers!
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.