WHEA_UNCORRECTABLE_ERROR BSoD Windows 10

[mrzephhy]

Ok everyone, so about a week and a half ago, I received the WHEA_UNCORRECTABLE_ERROR BSoD. I rebooted windows many times and tried installing all drivers, cleaning the registry, turning off cpu overclocking, doing memory debug and system file check, etc.


I have the minidump file analysis pasted here:


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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 17134 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 17134.1.amd64fre.rs4_release.180410-1804
Machine Name:
Kernel base = 0xfffff802`2ea0e000 PsLoadedModuleList = 0xfffff802`2edcb2f0
Debug session time: Tue May 29 17:48:23.241 2018 (UTC - 7:00)
System Uptime: 0 days 0:07:40.243
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000d3`01b6d018). Type ".hh dbgerr001" for details
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, ffffa704253f9028, f2000100, 10005}

Probably caused by : GenuineIntel

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

nt!KeBugCheckEx:
fffff802`2eba5650 48894c2408 mov qword ptr [rsp+8],rcx ss:ffffb881`9aca8af0=0000000000000124
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: ffffa704253f9028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000f2000100, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000010005, Low order 32-bits of the MCi_STATUS value.

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


KEY_VALUES_STRING: 1


STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 17134.1.amd64fre.rs4_release.180410-1804

SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd.

SYSTEM_PRODUCT_NAME: H170-Gaming 3

SYSTEM_SKU: Default string

SYSTEM_VERSION: Default string

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: F22e

BIOS_DATE: 03/09/2018

BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd.

BASEBOARD_PRODUCT: H170-Gaming 3

BASEBOARD_VERSION: x.x

DUMP_TYPE: 1

BUGCHECK_P1: 0

BUGCHECK_P2: ffffa704253f9028

BUGCHECK_P3: f2000100

BUGCHECK_P4: 10005

BUGCHECK_STR: 0x124_GenuineIntel

CPU_COUNT: 4

CPU_MHZ: cf0

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: C2'00000000 (cache) C2'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: CompatTelRunner.exe

CURRENT_IRQL: f

ANALYSIS_SESSION_HOST: DESKTOP-U6LLH9C

ANALYSIS_SESSION_TIME: 05-29-2018 20:58:09.0298

ANALYSIS_VERSION: 10.0.17674.1000 amd64fre

STACK_TEXT:
ffffb881`9aca8ae8 fffff802`2f3b2520 : 00000000`00000124 00000000`00000000 ffffa704`253f9028 00000000`f2000100 : nt!KeBugCheckEx
ffffb881`9aca8af0 fffff80c`8b0014ba : ffffa704`253f9028 ffffa704`24f44330 ffffa704`24f44330 ffffa704`24f44330 : hal!HalBugCheckSystem+0xd0
ffffb881`9aca8b30 fffff802`2ecd9131 : ffffa704`253f9028 00000000`00000000 ffffa704`24f44330 ffffa704`24f44330 : PSHED!PshedBugCheckSystem+0xa
ffffb881`9aca8b60 fffff802`2f3b3c60 : 00000000`00000728 00000000`00000002 00000000`00000000 00000000`00000000 : nt!WheaReportHwError+0x261
ffffb881`9aca8bc0 fffff802`2f3b3fc0 : 00000000`00000010 ffffa704`24f44380 ffffb881`9aca8d68 00000000`00000002 : hal!HalpMcaReportError+0x50
ffffb881`9aca8d10 fffff802`2f3b3eae : ffffa704`24d02890 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xe0
ffffb881`9aca8d60 fffff802`2f3b40f2 : 00000000`00000004 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xda
ffffb881`9aca8da0 fffff802`2f3b4390 : ffffa704`24d02890 ffffb881`9aca8fd0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xce
ffffb881`9aca8dd0 fffff802`2ebb57bb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
ffffb881`9aca8e00 fffff802`2ebb543f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
ffffb881`9aca8f40 00007ffd`8dfc40bc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x1bf
000000d3`018da948 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`8dfc40bc


THREAD_SHA1_HASH_MOD_FUNC: a23b7d765df95ae34e5a10fad949ea2e4c0373b0

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: e037a3865da0454475c5dbb1c08ec256b55d28c6

THREAD_SHA1_HASH_MOD: 156f1337245e21f523efe2d6f6d05bb3ab59ca82

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_MAE

PRIMARY_PROBLEM_CLASS: 0x124_GenuineIntel_PROCESSOR_MAE

TARGET_TIME: 2018-05-30T00:48:23.000Z

OSBUILD: 17134

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 784

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2018-04-10 21:04:54

BUILDDATESTAMP_STR: 180410-1804

BUILDLAB_STR: rs4_release

BUILDOSVER_STR: 10.0.17134.1.amd64fre.rs4_release.180410-1804

ANALYSIS_SESSION_ELAPSED_TIME: cb6

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x124_genuineintel_processor_mae

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

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

It's rather long, but if anybody can help me determine what error it is, I would be extremely grateful. Oh, and I use my PC for gaming and it's custom built.

EDIT: I also tried reseating the RAM.

 

[Colif]

Have you had a WhEA error since removing overclock? As they can be caused by them, as well as overclocking software

remove MSI afterburner if installed, same applies to Asus GPU Tweak 2
remove Intel Extreme Tuning utility, if installed.
Do you have the latest BIOS as these can be fixed by them.
I didn't think you could overclock on a H board? normally need Z? (I might be wrong or out of touch)

Try running this on CPU - https://downloadcenter.intel.com/download/19792/Intel-Processor-Diagnostic-Tool

If you still getting them, Can you follow option one on the following link - here
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump after the next BSOD
copy that file to documents
upload the copy from documents to a cloud server and share the link here and I will get someone to check the files for me. Convert them into a format I can read.

 

[mrzephhy]

No, you’re right. You can’t overclock an H board. I didn’t have any of those programs installed, and I will try to upload the minidump onto a onedrive server. Oh, and this BSoD is being caused by Hal.dll, ntoskrnl.exe, and PSHED.dll. This ISN’T occurring in safe mode.

 

[gardenman]

You may need to copy the minidump file(s) from the C:\Windows\minidump folder to your desktop (or documents folder) first before they will upload correctly.

 

[mrzephhy]

Would this work? http://

 

[gardenman]

Yes. I ran the dump file through the debugger and got the following information: https://pste.eu/p/nlvs.html

File: 060218-8140-01.dmp (Jun 2 2018 - 15:05:10)
BugCheck: [WHEA_UNCORRECTABLE_ERROR (124)]
Probably caused by: GenuineIntel (Process: chrome.exe)
Uptime: 0 Day(s), 0 Hour(s), 01 Min(s), and 39 Sec(s)

Remove all overclocks.
The overclocking driver "NTIOLib_X64.sys" was found on your system. (MSI Afterburner)

Motherboard: https://www.gigabyte.com/Motherboard/GA-H170-Gaming-3-rev-10#ov
You have the latest BIOS installed.

I can't help you with this. Wait for additional replies. Good luck.

 

[mrzephhy]

Yeah I dragged that file from the MSI disk into my system32, and I just removed it. I do have the latest BIOS. I'm going to run a memcheck and see what happens.

 

[Colif]

Go to MSI web site and update the gaming app as well, though its unlikely to cause WHEA errors.

You shouldn't use files off the DVD, always helps to go to MSI web site instead and get the newest versions.

try updating LAN drivers - https://www.killernetworking.com/driver-downloads/category/other-downloads

Do you have a gigabyte graphics card?

Jul 04 2013 - gdrv.sys: GIGABYTE Tools (motherboard and graphics cards) driver

as this seems out of place on a MSI motherboard. See if there is a newer version as this too old for win 10.

could update Nvidia drivers as well - http://www.nvidia.com/Download/Scan.aspx?lang=en-us

 

[mrzephhy]

My motherboard is a GIGABYTE, my GPU is an MSI.

I'll try updating the NVIDIA drivers, MSI Gaming App, and LAN drivers.

 

[Colif]

Sorry, I had just woken up... I saw the MSI gaming app and assumed it was a motherboard driver. I didn't look at web site for motherboard or I wouldn't have said that

 

[mrzephhy]

It's okay, I'm waiting for memtest to finish so I can try the other solutions, trying to make sure RAM isn't faulty, if it is I'll see which stick.

 

[mrzephhy]

I've updated all drivers and apps... it's still acting up. What should my next step be?

 

[Colif]

give us any new dumps that are created. One of them might tell us what driver is tripping it up.

Did you run the Intel scan?

1. Check the processor seating, heat sink, and the compound between the processor and the heat sink which are common causes.

Got this from here, same 3 files crashed: https://answers.microsoft.com/en-us/windows/forum/windows_10-performance/windows-10-pro-bsod-haldll-ntoskrnlexe-psheddll/e20f7e47-fa30-4755-972d-21b098e2ed91?auth=1

NTOSKRNL = windows kernel. It handles all driver requests, power management, and memory management. It sits between Hardware and Applications. It got blamed but its not the cause
HAL = Hardware Allocation Layer
PSHED.dll = Platform Specific Hardware Error Driver

all 3 parts of windows.

 

[mrzephhy]

Intel scan passed for all stages, I'll send another dump

 

[mrzephhy]

Here https://1drv.ms/u/s!AiFyb9Pv0FSZgWdPqwtq3JAw-ozB

 

[gardenman]

Hi, I ran the dump files through the debugger and got the following information: https://pste.eu/p/zxJN.html

Spoiler

File: 060218-36406-01.dmp (Jun 2 2018 - 16:37:24)
BugCheck: [WHEA_UNCORRECTABLE_ERROR (124)]
Probably caused by: GenuineIntel (Process: DriverBooster.)
Uptime: 0 Day(s), 0 Hour(s), 02 Min(s), and 19 Sec(s)

File: 060218-27750-01.dmp (Jun 2 2018 - 15:24:35)
BugCheck: [WHEA_UNCORRECTABLE_ERROR (124)]
Probably caused by: GenuineIntel (Process: chrome.exe)
Uptime: 0 Day(s), 0 Hour(s), 02 Min(s), and 57 Sec(s)

File: 060218-22046-01.dmp (Jun 2 2018 - 19:32:36)
BugCheck: [WHEA_UNCORRECTABLE_ERROR (124)]
Probably caused by: GenuineIntel (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 07 Min(s), and 25 Sec(s)

File: 060218-21718-01.dmp (Jun 2 2018 - 15:27:16)
BugCheck: [WHEA_UNCORRECTABLE_ERROR (124)]
Probably caused by: GenuineIntel (Process: chrome.exe)
Uptime: 0 Day(s), 0 Hour(s), 02 Min(s), and 15 Sec(s)

File: 060218-20453-01.dmp (Jun 2 2018 - 15:29:20)
BugCheck: [WHEA_UNCORRECTABLE_ERROR (124)]
Probably caused by: GenuineIntel (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 01 Min(s), and 37 Sec(s)

I can't help you with this. Wait for additional replies. Good luck.

 

[mrzephhy]

Alright.

 

[mrzephhy]

Would replacing the drivers/files listed above from the same exact computer with the same parts on a running windows 10 installation possibly fix the issue, or will it not affect it if they are replaced?

 

[mrzephhy]

I actually was able to run a game and several tabs open for 2 hours without a crash. This is the longest ever and I've only been able to be on for max 5-10 mins. I'll see whether it's fixed tomorrow. I might've fixed it with a few driver installations and utility updates.

 

[mrzephhy]

Speak of the devil... it crashed again. I had prime95 open in the background which I forgot I left open stress testing my cpu, and right as I closed it when about to shut down my pc, it blue screens.

 

[mrzephhy]

Update: I’ve tested RAM stick by stick and it crashes both times, so I’m assuming it’s not the ram because there are low odds of both sticks being the cause. I honestly think my cpu is causing this and I also don’t ever get this error in safe mode with networking. What do you guys think if you’re still willing to give advice?

 

[mrzephhy]

Replaced thermal paste that wore off and it didn't fix it either.

 

[Colif]

Try removing the MSI gaming app, see if a minimal install will run. Same with gigabyte tools. And MSI afterburner if its still there

The Intel scan found nothing, 90% of time I fix WHEA errors they are software, Tools like the ones above can mess with CPU settings and cause these.

WHEA errors can also be another part of PC apart from CPU, they just called by the CPU, not necessarily caused by it.

 

[mrzephhy]

I didn’t have those before and I uninstalled them. I’m still getting the error regardless if they are there.

 

[Colif]

If its caused by hardware, its really hard to find without spare parts. I would be tempted to take PC to a repair store and ask them to figure it out.

Its not CPU
Its not Ram (probably)
Whats left?

Test ssd/hdd health with HDTune? I have seen hard drives cause them before
GPU - best way to test if this is cause is to run off the IGPU and see if you still get WHEA errors. If you do, its not the GPU
Any other parts I missed yet?
Motherboard/PSU are hardest to test, only real way is to have spares you know do work and swap them out.

Cleaned inside case? CPU fan actually working? WHEA can be caused by overheating.