Seemingly random BSOD

[NickSc]

I keep my system running 24/7 in a room with little dust and average temperatures of about 60F. I use it for general forum surfing, high end gaming, and for CAD software. I don't seem to have any other problems but every few days, whether the system is idle or I am running the processor at 100%, the computer will crash and send me to the BSOD. I have attached the dump files as instructed. (http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html) I would appreciate any tips on how to troubleshoot or hopefully fix this problem. Many thanks in advance for any help.

- Nick

View attachment 155635

 

[Maguscreed]

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: fffffa800e78a028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b26e4000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000175, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  BFBC2Game.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`02f6ca88 fffff800`035f1903 : 00000000`00000124 00000000`00000000 fffffa80`0e78a028 00000000`b26e4000 : nt!KeBugCheckEx
fffff880`02f6ca90 fffff800`03189493 : 00000000`00000001 fffffa80`0e7ec230 00000000`00000000 fffffa80`0e7ec280 : hal!HalBugCheckSystem+0x1e3
fffff880`02f6cad0 fffff800`035f15c8 : 00000000`00000728 fffffa80`0e7ec230 fffff880`02f6ce30 00000000`07248c00 : nt!WheaReportHwError+0x263
fffff880`02f6cb30 fffff800`035f0f1a : fffffa80`0e7ec230 fffff880`02f6ce30 fffffa80`0e7ec230 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`02f6cc80 fffff800`035e4e8f : 00000000`07248b80 00000000`00000001 fffff880`02f6ceb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`02f6ccc0 fffff800`03071fac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
fffff880`02f6ccf0 fffff800`03071e13 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`02f6ce30 00000000`00a5ad34 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`0c51fa00 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xa5ad34


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

Followup: MachineOwner
---------

This error is common with overclocked systems, as is the heat you are experiencing.
Do you know if your system is currently overclocked or if the values have been adjusted?

This error is almost exclusively been related to overclocking in my past experience, though it could be pointing to a failing cpu as well.

 

[NickSc]

I have done nothing manually, but when I built the system, the processor came with software that overclocks it by default. The processor is 3 GHz but I believe it is running at roughly 3.4 GHz. Like I said before though, the system has crashed while idling; the processor is usually around 40C at idle. It does run rather hot while in heavy use, sometimes as high as 57C. I didn't think this was enough to cause damage though. If that is too hot, do you suppose the damage is already done or is it something I could remedy with a better cooling system?

 

[Maguscreed]

The WHEA error always comes from a overclock issue or physically damaged hardware (at least that's been my personal experience) you either need to try and get the clock to normal or you may even be looking at replacing hardware. The state of the machine is rather moot as this particular kind of error has very few causes.

 

[NickSc]

I'll look into changing the clock back to normal and see if I still have problems. Thanks for the help.