WHEA_UNCORRECTABLE_ERROR Windows 8.1 Pro

xaceaaron

Reputable
Dec 31, 2014
6
0
4,510
Whea_UNCORRECTABLE_ERROR

It freezes and then repeats a god awful noise like say I was on teamspeak with someone while playing a game and it'll repeat their voice in this robotic stream.

I just recently built a pc and I keep getting this error. I've refreshed once. Reset once. I don't know what the issue is.

These are the specs: http://pcpartpicker.com/user/aceaaron/saved/R2v2FT

Dmp file:
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols

************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols

Microsoft (R) Windows Debugger Version 6.3.9600.17298 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*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Executable search path is:
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`a141b000 PsLoadedModuleList = 0xfffff801`a16df990
Debug session time: Wed Dec 31 18:21:41.982 2014 (UTC - 5:00)
System Uptime: 0 days 3:34:33.620
Loading Kernel Symbols
...............................................................
..........................................................Page 13d102 not present in the dump file. Type ".hh dbgerr004" for details
......
.....................Page 347ea7 not present in the dump file. Type ".hh dbgerr004" for details
...
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`fef7e018). Type ".hh dbgerr001" for details
Loading unloaded module list
...................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, ffffe00002a75028, be000000, 800400}

Page 413655 not present in the dump file. Type ".hh dbgerr004" for details
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: ffffe00002a75028, 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:
------------------

Page 413655 not present in the dump file. Type ".hh dbgerr004" for details

BUGCHECK_STR: 0x124_GenuineIntel

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: OBS.exe

CURRENT_IRQL: f

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

STACK_TEXT:
ffffd000`20457d78 fffff801`a1bd1c9f : 00000000`00000124 00000000`00000000 ffffe000`02a75028 00000000`be000000 : nt!KeBugCheckEx
ffffd000`20457d80 fffff801`a15d2d41 : 00000000`00000001 ffffe000`003b1310 ffffe000`003b1310 ffffe000`02a75028 : hal!HalBugCheckSystem+0xcf
ffffd000`20457dc0 fffff801`a1bd212c : 00000000`00000728 00000000`00000002 ffffd000`204581b0 00000000`00000000 : nt!WheaReportHwError+0x22d
ffffd000`20457e20 fffff801`a1bd2499 : ffffe000`00000010 ffffe000`003b1310 ffffd000`20457fc8 ffffe000`003b1310 : hal!HalpMcaReportError+0x50
ffffd000`20457f70 fffff801`a1bd2384 : ffffe000`003b0ca0 00000000`00000001 00000000`00000002 00000000`00000000 : hal!HalpMceHandlerCore+0xe1
ffffd000`20457fc0 fffff801`a1bd25ce : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4
ffffd000`20458000 fffff801`a1bd274f : ffffe000`003b0ca0 ffffd000`20458230 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xce
ffffd000`20458030 fffff801`a15737bb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
ffffd000`20458060 fffff801`a1573571 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
ffffd000`204581a0 00000000`59134b23 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171
00000000`0fb4a930 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x59134b23


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_MAE

BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_MAE

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x124_genuineintel_processor_mae

FAILURE_ID_HASH: {7c95de0c-286c-8226-45c2-422b4de101d6}

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

___________________________________________________________________________




Update 1/1/15

It crashed 3 times today. 2 crashes in a row. memtest86 passed.








heres another dump file:

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

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: f

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

STACK_TEXT:
ffffd001`bfb11df8 fffff801`2e9db203 : 00000000`00000124 00000000`00000000 ffffe001`6a1d7028 00000000`be000000 : nt!KeBugCheckEx
ffffd001`bfb11e00 fffff801`2e3db825 : 00000000`00000001 ffffe001`67cab1a0 ffffe001`67cab1a0 ffffe001`6a1d7028 : hal!HalBugCheckSystem+0xcf
ffffd001`bfb11e40 fffff801`2e9db68c : 00000000`00000728 00000000`00000001 ffffd001`bfb12230 00000000`00000000 : nt!WheaReportHwError+0x22d
ffffd001`bfb11ea0 fffff801`2e9dba11 : ffffe001`00000010 ffffe001`67cab1a0 ffffd001`bfb12048 ffffe001`67cab1a0 : hal!HalpMcaReportError+0x50
ffffd001`bfb11ff0 fffff801`2e9db8f4 : ffffe001`67caabf0 00000000`00000001 00000000`00000001 00000000`00000000 : hal!HalpMceHandlerCore+0xe1
ffffd001`bfb12040 fffff801`2e9dbb4e : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4
ffffd001`bfb12080 fffff801`2e9dbcd7 : ffffe001`67caabf0 ffffd001`bfb122b0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xce
ffffd001`bfb120b0 fffff801`2e379abb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
ffffd001`bfb120e0 fffff801`2e379871 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
ffffd001`bfb12220 fffff800`c99dbd62 : fffff800`c99db1f7 00000000`00000000 ffffe001`6a80e8e0 ffffd001`bfb32a20 : nt!KiMcheckAbort+0x171
ffffd001`bfb328e8 fffff800`c99db1f7 : 00000000`00000000 ffffe001`6a80e8e0 ffffd001`bfb32a20 ffffd001`bfb08180 : intelppm!C1Halt+0x2
ffffd001`bfb328f0 fffff801`2e2d171a : ffffd001`bfb08180 ffffd001`bfb32a00 ffffe001`6a80e8e0 00000000`00000000 : intelppm!AcpiCStateIdleExecute+0x17
ffffd001`bfb32920 fffff801`2e2d118a : ffffd001`bfb08180 ffffd001`bfb32b4c ffffd001`bfb32b50 ffffd001`bfb32b58 : nt!PpmIdleExecuteTransition+0x3da
ffffd001`bfb32b10 fffff801`2e372abc : ffffd001`bfb08180 ffffd001`bfb08180 ffffd001`bfb143c0 00000000`0000124f : nt!PoIdle+0x27a
ffffd001`bfb32c60 00000000`00000000 : ffffd001`bfb33000 ffffd001`bfb2d000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c


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_MAE

BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_MAE

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x124_genuineintel_processor_mae

FAILURE_ID_HASH: {7c95de0c-286c-8226-45c2-422b4de101d6}

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

 

xaceaaron

Reputable
Dec 31, 2014
6
0
4,510


I downloaded a memtest from memtest86.com and put it on an usb. This should work correct?
 

xaceaaron

Reputable
Dec 31, 2014
6
0
4,510


Hardware checks out ok. Passed memtest. What voltages would be bad voltages? note: all my components are new.
 

TRENDING THREADS