Homebuilt Random BSOD WHEA_UNCORRECTABLE_ERROR (124)

Toggle sidebar Toggle sidebar
F

fractal14

Reputable
Feb 19, 2014
3
0
4,510
Hi,

I built a new computer this week, it's only the second time I have done this, but the first time I have experienced major problems. I am experiencing a random BSOD (WHEA_UNCORRECTABLE_ERROR (124)). I am hoping someone has an idea, here is what I have done so far as well as my rig details.

Any help would be greatly appreciated.

Motherboard: MSI Z87M Gaming
CPU: Intel Core i7-4770K Haswell 3.5GHz LGA 1150 84W
RAM: 32GB kit (8GBx4), Ballistix 240-pin DIMM, DDR3 PC3-12800 memory module
PSU: Corsair RM 750
HDDs: 3
SSDs: 2 (OS is on one, other is for vm's)
GPU: Not installed
DVD/CD: yes

TESTING SO FAR
- Memtest86 (scanned twice, 10 hours, no errors)
- chckdsk - no errors
- Prime95 BSOD about 20 minutes in, one Core registering 81 degrees
- RAM - Check the computer with 1 slot, 2, 3, etc etc

DUMP FILE

Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available


************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*

************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is: srv*
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
Machine Name:
Kernel base = 0xfffff801`5228b000 PsLoadedModuleList = 0xfffff801`5254f990
Debug session time: Wed Feb 19 12:01:10.180 2014 (UTC - 8:00)
System Uptime: 0 days 0:21:46.829
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols

Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, ffffe00001e31028, bf800000, 124}

*** ERROR: Symbol file could not be found. Defaulted to export symbols for igdkmd64.sys -
Probably caused by : GenuineIntel

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

0: 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: ffffe00001e31028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000124, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR: 0x124_GenuineIntel

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: f

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

STACK_TEXT:
fffff801`53f1ca38 fffff801`52251c9f : 00000000`00000124 00000000`00000000 ffffe000`01e31028 00000000`bf800000 : nt!KeBugCheckEx
fffff801`53f1ca40 fffff801`52442d41 : 00000000`00000001 ffffe000`004aa440 ffffe000`004aa440 ffffe000`01e31028 : hal!HalBugCheckSystem+0xcf
fffff801`53f1ca80 fffff801`5225212c : 00000000`00000728 00000000`00000000 fffff801`53f1ce70 00000000`00000000 : nt!WheaReportHwError+0x22d
fffff801`53f1cae0 fffff801`52252499 : ffffe000`00000010 ffffe000`004aa440 fffff801`53f1cc88 ffffe000`004aa440 : hal!HalpMcaReportError+0x50
fffff801`53f1cc30 fffff801`52252384 : ffffe000`004d2b40 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xe1
fffff801`53f1cc80 fffff801`522525ce : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4
fffff801`53f1ccc0 fffff801`5225274f : ffffe000`004d2b40 fffff801`53f1cef0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xce
fffff801`53f1ccf0 fffff801`523e37bb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff801`53f1cd20 fffff801`523e3571 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
fffff801`53f1ce60 fffff800`01f123a7 : fffff801`5252a100 ffffe000`0065c940 00000000`0004400c fffff800`01f121c6 : nt!KiMcheckAbort+0x171
ffffd000`24fed5f0 fffff800`01ea6b99 : ffffd000`24fed9a0 fffff800`0004400c ffffe000`007ab000 ffffe000`01d90f00 : igdkmd64!hybDriverEntry+0x6c5f7
ffffd000`24fed780 fffff800`01fea344 : 00000000`00000020 ffffe000`03055000 00000000`b0100000 fffff800`0207f9c9 : igdkmd64!hybDriverEntry+0xde9
ffffd000`24fed7b0 fffff800`02081009 : 00000000`00000020 fffff800`0207f9c9 00000000`b0100000 ffffe000`00000000 : igdkmd64!hybDriverEntry+0x144594
ffffd000`24fed7e0 fffff800`020786b9 : ffffe000`03055010 fffff800`0209ea30 ffffe000`01e36100 ffffd000`24fed9c0 : igdkmd64!hybDriverEntry+0x1db259
ffffd000`24fed830 fffff801`523d9932 : ffffe000`024c0190 ffffe000`01e36140 ffffd000`00000000 fffff800`01481c0f : igdkmd64!hybDriverEntry+0x1d2909
ffffd000`24fed860 fffff800`01481c0f : ffffe000`003f90c8 fffff800`0209ea30 ffffe000`0065c940 fffff800`01eaecec : nt!KeSynchronizeExecution+0x42
ffffd000`24fed8a0 fffff800`01fc1623 : ffffe000`02fd2ca0 ffffd000`24fed9c0 ffffe000`0065c940 ffffe000`03055010 : dxgkrnl!DpSynchronizeExecution+0xaf
ffffd000`24fed8f0 fffff800`0209e93c : fffff801`5252a1c0 00000000`00000000 4145ae50`814a22f8 c19d9cda`20425340 : igdkmd64!hybDriverEntry+0x11b873
ffffd000`24fed930 fffff800`01fbdb12 : ffffd000`24feda14 00000000`c0000001 00000000`00000000 ffffd000`24fed9e0 : igdkmd64!hybDriverEntry+0x1f8b8c
ffffd000`24fed970 fffff800`01f0d37c : 00000000`00000001 fffff801`5252a1c0 00000000`00000002 00000000`00000000 : igdkmd64!hybDriverEntry+0x117d62
ffffd000`24fed9a0 fffff800`01e778c4 : 00000000`00000000 fffff800`01e93500 ffffd000`00000002 00000000`00000001 : igdkmd64!hybDriverEntry+0x675cc
ffffd000`24fed9f0 fffff800`01e776fd : ffffe000`0077c000 ffffd000`24fedaa0 ffffe000`003f7540 ffffe000`003f7eb8 : igdkmd64+0x2f8c4
ffffd000`24feda30 fffff800`0148d3ff : ffffe000`003f7500 00000002`00000003 ffffe000`003f7540 fffff800`0147f901 : igdkmd64+0x2f6fd
ffffd000`24feda60 fffff800`0156af3c : ffffe000`003f7ed8 00000002`00000003 ffffe000`003f7540 ffffe000`003f7540 : dxgkrnl!DXGADAPTER::DdiControlInterrupt2+0x83
ffffd000`24fedab0 fffff800`0156a311 : 00000002`00000003 ffffe000`003f7540 ffffe000`02de74a0 fffff800`0141dd03 : dxgkrnl!DXGADAPTER::processVSyncPhaseTimer+0x50
ffffd000`24fedae0 fffff801`5232c1b9 : fffff800`0156a2dc 00000000`00000002 ffffe000`02de7000 ffffe000`01fff4e0 : dxgkrnl!DxgkpProcessVSyncPhaseThread+0x35
ffffd000`24fedb50 fffff801`523182e4 : 00000000`00000000 ffffe000`00552880 ffffe000`00552880 ffffe000`00480900 : nt!ExpWorkerThread+0x2b5
ffffd000`24fedc00 fffff801`523df2c6 : fffff801`52579180 ffffe000`00552880 ffffe000`0561f880 ffffd000`24fedd90 : nt!PspSystemThreadStartup+0x58
ffffd000`24fedc60 00000000`00000000 : ffffd000`24fee000 ffffd000`24fe8000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION:

FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_CACHE

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x124_genuineintel_processor_cache

FAILURE_ID_HASH: {4c8f3f5e-1af5-ed8b-df14-d42663b1dfa7}

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

0: 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: ffffe00001e31028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000124, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR: 0x124_GenuineIntel

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: f

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

STACK_TEXT:
fffff801`53f1ca38 fffff801`52251c9f : 00000000`00000124 00000000`00000000 ffffe000`01e31028 00000000`bf800000 : nt!KeBugCheckEx
fffff801`53f1ca40 fffff801`52442d41 : 00000000`00000001 ffffe000`004aa440 ffffe000`004aa440 ffffe000`01e31028 : hal!HalBugCheckSystem+0xcf
fffff801`53f1ca80 fffff801`5225212c : 00000000`00000728 00000000`00000000 fffff801`53f1ce70 00000000`00000000 : nt!WheaReportHwError+0x22d
fffff801`53f1cae0 fffff801`52252499 : ffffe000`00000010 ffffe000`004aa440 fffff801`53f1cc88 ffffe000`004aa440 : hal!HalpMcaReportError+0x50
fffff801`53f1cc30 fffff801`52252384 : ffffe000`004d2b40 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xe1
fffff801`53f1cc80 fffff801`522525ce : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4
fffff801`53f1ccc0 fffff801`5225274f : ffffe000`004d2b40 fffff801`53f1cef0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xce
fffff801`53f1ccf0 fffff801`523e37bb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff801`53f1cd20 fffff801`523e3571 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
fffff801`53f1ce60 fffff800`01f123a7 : fffff801`5252a100 ffffe000`0065c940 00000000`0004400c fffff800`01f121c6 : nt!KiMcheckAbort+0x171
ffffd000`24fed5f0 fffff800`01ea6b99 : ffffd000`24fed9a0 fffff800`0004400c ffffe000`007ab000 ffffe000`01d90f00 : igdkmd64!hybDriverEntry+0x6c5f7
ffffd000`24fed780 fffff800`01fea344 : 00000000`00000020 ffffe000`03055000 00000000`b0100000 fffff800`0207f9c9 : igdkmd64!hybDriverEntry+0xde9
ffffd000`24fed7b0 fffff800`02081009 : 00000000`00000020 fffff800`0207f9c9 00000000`b0100000 ffffe000`00000000 : igdkmd64!hybDriverEntry+0x144594
ffffd000`24fed7e0 fffff800`020786b9 : ffffe000`03055010 fffff800`0209ea30 ffffe000`01e36100 ffffd000`24fed9c0 : igdkmd64!hybDriverEntry+0x1db259
ffffd000`24fed830 fffff801`523d9932 : ffffe000`024c0190 ffffe000`01e36140 ffffd000`00000000 fffff800`01481c0f : igdkmd64!hybDriverEntry+0x1d2909
ffffd000`24fed860 fffff800`01481c0f : ffffe000`003f90c8 fffff800`0209ea30 ffffe000`0065c940 fffff800`01eaecec : nt!KeSynchronizeExecution+0x42
ffffd000`24fed8a0 fffff800`01fc1623 : ffffe000`02fd2ca0 ffffd000`24fed9c0 ffffe000`0065c940 ffffe000`03055010 : dxgkrnl!DpSynchronizeExecution+0xaf
ffffd000`24fed8f0 fffff800`0209e93c : fffff801`5252a1c0 00000000`00000000 4145ae50`814a22f8 c19d9cda`20425340 : igdkmd64!hybDriverEntry+0x11b873
ffffd000`24fed930 fffff800`01fbdb12 : ffffd000`24feda14 00000000`c0000001 00000000`00000000 ffffd000`24fed9e0 : igdkmd64!hybDriverEntry+0x1f8b8c
ffffd000`24fed970 fffff800`01f0d37c : 00000000`00000001 fffff801`5252a1c0 00000000`00000002 00000000`00000000 : igdkmd64!hybDriverEntry+0x117d62
ffffd000`24fed9a0 fffff800`01e778c4 : 00000000`00000000 fffff800`01e93500 ffffd000`00000002 00000000`00000001 : igdkmd64!hybDriverEntry+0x675cc
ffffd000`24fed9f0 fffff800`01e776fd : ffffe000`0077c000 ffffd000`24fedaa0 ffffe000`003f7540 ffffe000`003f7eb8 : igdkmd64+0x2f8c4
ffffd000`24feda30 fffff800`0148d3ff : ffffe000`003f7500 00000002`00000003 ffffe000`003f7540 fffff800`0147f901 : igdkmd64+0x2f6fd
ffffd000`24feda60 fffff800`0156af3c : ffffe000`003f7ed8 00000002`00000003 ffffe000`003f7540 ffffe000`003f7540 : dxgkrnl!DXGADAPTER::DdiControlInterrupt2+0x83
ffffd000`24fedab0 fffff800`0156a311 : 00000002`00000003 ffffe000`003f7540 ffffe000`02de74a0 fffff800`0141dd03 : dxgkrnl!DXGADAPTER::processVSyncPhaseTimer+0x50
ffffd000`24fedae0 fffff801`5232c1b9 : fffff800`0156a2dc 00000000`00000002 ffffe000`02de7000 ffffe000`01fff4e0 : dxgkrnl!DxgkpProcessVSyncPhaseThread+0x35
ffffd000`24fedb50 fffff801`523182e4 : 00000000`00000000 ffffe000`00552880 ffffe000`00552880 ffffe000`00480900 : nt!ExpWorkerThread+0x2b5
ffffd000`24fedc00 fffff801`523df2c6 : fffff801`52579180 ffffe000`00552880 ffffe000`0561f880 ffffd000`24fedd90 : nt!PspSystemThreadStartup+0x58
ffffd000`24fedc60 00000000`00000000 : ffffd000`24fee000 ffffd000`24fe8000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION:

FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_CACHE

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x124_genuineintel_processor_cache

FAILURE_ID_HASH: {4c8f3f5e-1af5-ed8b-df14-d42663b1dfa7}

Followup: MachineOwner


 
Sort by date Sort by votes
F

fractal14

Reputable
Feb 19, 2014
3
0
4,510


Hi rgd1101, thanks for the reply. I have been researching this issue for days and yes, I have been to that website several times (should have said that in my original question). I realize it appears this is a CPU issue, but if that is true or not I don't know.

I am using the stock cooler and I am not overclocking at all. Would overheating cause this BSOD? If so, what tempature would normally cause such an issue? Do I need a better heatsink? The case already has 2 120mm and one 80mm fan (not including the CPU and PSU fans).

Any help would be appreciated.
 
Upvote 0 Downvote
F

fractal14

Reputable
Feb 19, 2014
3
0
4,510
Ok, I think I have figured this out. Even though every post I have seen (as well as every tutorial about this issue) state to ensure you are not overclocking (as did rgd1101), my machine WAS overclocked. For those of you who purchase an MSI Gamming board, there is a black button in the BIOS called OC Genie. Well, either it came on by default (unlikely), or I mistakenly clicked it at some point. I figured this out by running the Intel Processor ID Utility (http://www.intel.com/p/en_US/support/highlights/processors/toolspiu) and noticed that my CPU was reporting much faster than what I purchased.

So, I went into the bios and noticed the button... Since then (about an hour) I have been running Prime95 with no issues and lower temps (by only a few degrees)

Beware of the overclock.... I will continue to test and post back if something changes
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom