WHEA_UNCORRECTABLE_ERROR - Random reboots and 0x124 error

zbook said:

Post #148 indicated that the details view has further information.
Look in the event viewer for any additional information in the details view and post into the thread.

There's a lot of information here and I'm not sure what you're looking for...

In the banner on this website there is # that can be used for each post.
Please find the information for the WHEA within the event viewer in the details section and post between {code} and {/code}

The event numbers can change depending on the filters but you are looking for something similar to what was Event[13904]:

zbook said:

In the banner on this website there is # that can be used for each post.
Please find the information for the WHEA within the event viewer in the details section and post between {code} and {/code}

Let me know if this is what you're looking for...

Attachment 162796

Code:

-
System




-
Provider





[ Name]
Microsoft-Windows-Kernel-WHEA





[ Guid]
{7B563579-53C8-44E7-8236-0F87B9FE6594}







EventID
20







Version
0







Level
4







Task
0







Opcode
0







Keywords
0x4000000000000800






-
TimeCreated





[ SystemTime]
2017-11-08T15:36:10.074676100Z







EventRecordID
7829







Correlation






-
Execution





[ ProcessID]
4





[ ThreadID]
13228







Channel
Microsoft-Windows-Kernel-WHEA/Errors







Computer
Dan-PC






-
Security





[ UserID]
S-1-5-18





-
EventData




Length
928

On the right pane click on create custom view.
Then click on critical and warning.
In event logs click on the drop down arrow and check windows logs.
Click OK then OK for new view.
View the results and scroll through the warnings to the WHEA event.
Then click on details.
Then post into the thread.

zbook said:

On the right pane click on create custom view.
Then click on critical and warning.
In event logs click on the drop down arrow and check windows logs.
Click OK then OK for new view.
View the results and scroll through the warnings to the WHEA event.
Then click on details.
Then post into the thread.

Only Warnings, no Criticals:
Attachment 162799

Source: CertificateServicesClient-AutoEnrollment

Code:

-
System




-
Provider





[ Name]
Microsoft-Windows-CertificateServicesClient-AutoEnrollment





[ Guid]
{F0DB7EF8-B6F3-4005-9937-FEB77B9E1B43}





[ EventSourceName]
AutoEnrollment






-
EventID
64





[ Qualifiers]
32768







Version
0







Level
3







Task
0







Opcode
0







Keywords
0x80000000000000






-
TimeCreated





[ SystemTime]
2017-11-08T20:47:46.123848800Z







EventRecordID
2469







Correlation






-
Execution





[ ProcessID]
0





[ ThreadID]
0







Channel
Application







Computer
Dan-PC







Security





-
EventData




Context
local system

click on the 4th one from the top WHEA and then click on the details tab

zbook said:

click on the 4th one from the top WHEA and then click on the details tab

The new processor was installed after 7:36AM this morning, but here is the WHEA-Logger from that latest event

Source: WHEA-Logger

Code:

-
System




-
Provider





[ Name]
Microsoft-Windows-WHEA-Logger





[ Guid]
{C26C4F3C-3F66-4E99-8F8A-39405CFED220}







EventID
19







Version
0







Level
3







Task
0







Opcode
0







Keywords
0x8000000000000000






-
TimeCreated





[ SystemTime]
2017-11-08T15:36:10.616108700Z







EventRecordID
13905






-
Correlation





[ ActivityID]
{6FA2697A-B553-4D62-B326-1BB6E434AD12}






-
Execution





[ ProcessID]
3632





[ ThreadID]
15160







Channel
System







Computer
Dan-PC






-
Security





[ UserID]
S-1-5-19





-
EventData




ErrorSource
1




ApicId
4




MCABank
0




MciStat
0xd400004000040150




MciAddr
0x1f801e6ef50e0




MciMisc
0x0




ErrorType
9




TransactionType
0




Participation
256




RequestType
5




MemorIO
256




MemHierarchyLvl
0




Timeout
256




OperationType
256




Channel
256




Length
928

zbook said:

click on the 4th one from the top WHEA and then click on the details tab

What do you think? Am I looking OK at the moment? No hardware failure issues that I can see...

There are 2 types of WHEA errors: Uncorrected and corrected.
The uncorrected errors result in BSOD.
The hardware/firmware could not correct the error that it had encountered.
This appears to have been fixed with the CPU replacement.
It is early in the process and there have been no further BSOD.

The corrected WHEA are conditions in which an error condition was detected by the processor and the error was corrected either by by the hardware or the firmware. These are non fatal errors. So there was no BSOD.

So at this time it is unclear what is causing the errors.
The errors are being detected by the hardware and firmware and have been corrected preventing the BSOD.