BSOD any game for a period of time (hal.dll & ntoskrnl.exe).

I used the recommended software from this forum to gather all of the logs and post it.

I have tried using Heaven DX11 to stress test the video card and ran it for..45minutes+ allowing the GPU to get to a heat of 80C and no BSOD.

It has BSODed when playing Dota 2, or Borderlands 2. (I don't play many games)

It BSODed once when I finished playing a game and chrome opened 32 tabs on accident, but this is a beast of a machine it should be able to handle it.

Code:

*******************************************************************************
*                                                                             *
*                        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: fffffa8007290028, 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:
------------------


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`0317cb58 fffff800`03208a3b : 00000000`00000124 00000000`00000000 fffffa80`07290028 00000000`be200000 : nt!KeBugCheckEx
fffff880`0317cb60 fffff800`02d9ab13 : 00000000`00000001 fffffa80`06f2fa50 00000000`00000000 fffffa80`06f2faa0 : hal!HalBugCheckSystem+0x1e3
fffff880`0317cba0 fffff800`03208700 : 00000000`00000728 fffffa80`06f2fa50 fffff880`0317cf30 fffff880`0317cf00 : nt!WheaReportHwError+0x263
fffff880`0317cc00 fffff800`03208052 : fffffa80`06f2fa50 fffff880`0317cf30 fffffa80`06f2fa50 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`0317cd50 fffff800`03207f0d : 00000000`00000008 00000000`00000001 fffff880`0317cfb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`0317cd90 fffff800`031fbe88 : 00000000`00000000 00000000`081ece58 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`0317cdc0 fffff800`02c8b8ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`0317cdf0 fffff800`02c8b713 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`0317cf30 00000000`5d5dc7f4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`0024f2cc 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x5d5dc7f4


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

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

In the device manager make sure all device have their latest drivers

Please follow this carefully

Stop 0x124 - what it means and what to try

Thank you both for posting.

I have run a stress test on the. The fans are more than adequate.

• HDD with CHKDSK /R
• RAM with MDSCHED
• Video Card with Heaven.

Is there anyway to stress test the processor that is recommended?

All of the drivers are up to date, with the exception of the sony PS3 camera (I just installed it now)

---

In Testing it just BSODed again. Is there anyway to narrow down the component based off the logs?

upload the new dumps

There are the 2 latest crashes happened today and yesterday.

Follow this

Hardware - Stress Test With Prime95

Do you have latest chipset software?

update from here

http://www.intel.com/p/en_US/support/detect?iid=dc_iduu

Code:

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`02e58000 PsLoadedModuleList = 0xfffff800`0309c670
Debug session time: Mon Dec 17 09:55:49.199 2012 (UTC + 5:30)
System Uptime: 0 days 1:34:53.949
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800727c028, be200000, 5110a}

Probably caused by : GenuineIntel

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffffa800727c028, 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:
------------------


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  dota.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`02f6db58 fffff800`02e21a3b : 00000000`00000124 00000000`00000000 fffffa80`0727c028 00000000`be200000 : nt!KeBugCheckEx
fffff880`02f6db60 fffff800`02fe4b13 : 00000000`00000001 fffffa80`06f1da10 00000000`00000000 fffffa80`06f1da60 : hal!HalBugCheckSystem+0x1e3
fffff880`02f6dba0 fffff800`02e21700 : 00000000`00000728 fffffa80`06f1da10 fffff880`02f6df30 fffff880`02f6df00 : nt!WheaReportHwError+0x263
fffff880`02f6dc00 fffff800`02e21052 : fffffa80`06f1da10 fffff880`02f6df30 fffffa80`06f1da10 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`02f6dd50 fffff800`02e20f0d : 00000000`00000008 00000000`00000001 fffff880`02f6dfb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`02f6dd90 fffff800`02e14e88 : 00000000`0d20b6b8 00000000`0d204000 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`02f6ddc0 fffff800`02ed58ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`02f6ddf0 fffff800`02ed5713 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`02f6df30 00000000`6276c7e0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`1242f838 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6276c7e0


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

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

The only thing that had a newer version available was a network driver, I am doing the prime95 stress tests now.

prime95 caused it to BSOD in less than 30 seconds.

Called Intel, they are trying to tell me that the 2133 muskin ram is to blame not the processor because it is not fully supported. I have a second computer with the same ram and no issue.

It also seems like this "Intel Processor Diagnostic Tool" is bunk, because it only tests 5% of the total load on the processor.