Custom Built PC periodically crashing "WHEA_UNCORRECTABLE_ERROR"

Sam_B_

Honorable
Jun 6, 2014
7
0
10,510
Hello,
My PC keeps crashing (sometimes even when idle) and it's been going on for months.
If i increase my fan speed it won't crash as often, but still will even at maximum fan speed.
Here is the dump:
Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 16/07/2017 21:49:41
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (35184372088832),(2)
User: SYSTEM
Computer: DESKTOP-H0FM6LR
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>3</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000200000000002</Keywords>
<TimeCreated SystemTime="2017-07-16T19:49:41.909690700Z" />
<EventRecordID>14782</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>DESKTOP-H0FM6LR</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">292</Data>
<Data Name="BugcheckParameter1">0x0</Data>
<Data Name="BugcheckParameter2">0xffffe00083a50028</Data>
<Data Name="BugcheckParameter3">0xbf800000</Data>
<Data Name="BugcheckParameter4">0x124</Data>
<Data Name="SleepInProgress">0</Data>
<Data Name="PowerButtonTimestamp">0</Data>
<Data Name="BootAppStatus">0</Data>
</EventData>
</Event>
 
Solution
cpp called the bugcheck. the reason is stored in the memory dump file and can be accessed by the windows debugger via the command
!errrec 0xffffe00083a50028

this can be a overheating problem, incorrect voltages or clock rates being applied
to the CPU.

generally, you want blow out the dust from the CPU and make sure you don't have a overclock in the BIOS or overclocking drivers installed.

sometimes if you put the memory dump files from c:\windows\minidump directory onto a cloud server like Microsoft one drive, share the files for public access and post a link. a person can look at the memory dump and see the reason that the CPU told the system to shut down with a bugcheck.
cpp called the bugcheck. the reason is stored in the memory dump file and can be accessed by the windows debugger via the command
!errrec 0xffffe00083a50028

this can be a overheating problem, incorrect voltages or clock rates being applied
to the CPU.

generally, you want blow out the dust from the CPU and make sure you don't have a overclock in the BIOS or overclocking drivers installed.

sometimes if you put the memory dump files from c:\windows\minidump directory onto a cloud server like Microsoft one drive, share the files for public access and post a link. a person can look at the memory dump and see the reason that the CPU told the system to shut down with a bugcheck.
 
Solution