ntoskrnl.exe WHEA UNCONTROLLABLE ERROR

[tony1987]

So this problem has been going on for a few months, where my PC would reboot without warning while in the middle of something. Normally it was in the middle of playing Overwatch or just sitting back watching a stream on Twitch. And the timing is erratic, it could go a couple days of heavy use between events, to even a few weeks inbetween events.

I've tried these various troubleshooting methods, to no avail:
1. MemTest - No issues found
2. Overclocking - None
3. BIOS - Up to date according to manufacturer's website
4. Graphics Driver - Clean uninstall and reinstall of drivers
5. Device Manager - No outdated drivers as far as I can tell.

Parts:
- nVidia GTX 950 GPU
- Rosewill 800W PSU
- Gigabyte mobo ga-78lmt-s2 rev 1.20
- AMD FX-4300 Vishera 3.8ghz (no overclock)

I managed to grab some stuff from WhoCrashed, and it came up with this:

On Mon 2018-02-19 11:02:20 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\021918-31171-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75E9F3)
Bugcheck code: 0x124 (0x0, 0xFFFFD10D453EC8F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Windows Event Viewer comes up with this data:

Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 2018-02-19 11:02:21 AM
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (70368744177664),(2)
User: SYSTEM
Computer: DESKTOP-IMQHR7N
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>6</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000400000000002</Keywords>
<TimeCreated SystemTime="2018-02-19T15:02:21.587692100Z" />
<EventRecordID>5062</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>DESKTOP-IMQHR7N</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">0</Data>
<Data Name="BugcheckParameter1">0x0</Data>
<Data Name="BugcheckParameter2">0x0</Data>
<Data Name="BugcheckParameter3">0x0</Data>
<Data Name="BugcheckParameter4">0x0</Data>
<Data Name="SleepInProgress">0</Data>
<Data Name="PowerButtonTimestamp">0</Data>
<Data Name="BootAppStatus">0</Data>
<Data Name="Checkpoint">0</Data>
<Data Name="ConnectedStandbyInProgress">false</Data>
<Data Name="SystemSleepTransitionsToOn">1</Data>
<Data Name="CsEntryScenarioInstanceId">0</Data>
<Data Name="BugcheckInfoFromEFI">true</Data>
<Data Name="CheckpointStatus">0</Data>
</EventData>
</Event>

I also have the dump file on my dropbox account for anyone who wants to take a gander and see if they can see something I missed: https://www.dropbox.com/s/1q3yb630wqjvafo/021918-31171-01.dmp?dl=0

Any help is much appreciated. It gets annoying when it happens without warning.

 

[Colif]

I will get someone to look at logs. WHEA errors normally only caused by hardware or Overclocking drivers.

Remove MSI Afterburner if installed

 

[gardenman]

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

File: 021918-31171-01.dmp (Feb 19 2018 - 10:02:20)
BugCheck: [WHEA_UNCORRECTABLE_ERROR (124)]
Probably caused by: AuthenticAMD (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 00 Min(s), and 13 Sec(s)

BIOS information was not included in the dump file which can sometimes mean an outdated BIOS. Check for any updates.

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

 

[johnbl]

system rebooted because of a power problem, then on the reboot the cpu got a bus error and called a bugcheck. (most likely because the power was not stable yet, system up time was 13 seconds

I would be looking at the power supply and the age of the machine. IE, look for overheating of the cpu or GPU or even the PSU. blow out any dust, check the age of the machine (date of the BIOS is a good indicator)
check the power connections from the power supply to the motherboard and from the power supply to the GPU. make sure the GPU is not overclocked.