WHEA_UNCORRECTABLE_ERROR - Random reboots and 0x124 error

zbook said:

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.

So it's entirely possible that I'm not getting any new WHEA errors at all, since no new errors have occurred since I replaced the processor this morning... though I'm not sure what the "Operational" vs "Errors" information means

Attachment 162828

Code:

-
System




-
Provider





[ Name]
Microsoft-Windows-Kernel-WHEA





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







EventID
5







Version
0







Level
4







Task
0







Opcode
0







Keywords
0x2000000000000000






-
TimeCreated





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







EventRecordID
21







Correlation






-
Execution





[ ProcessID]
4





[ ThreadID]
8







Channel
Microsoft-Windows-Kernel-WHEA/Operational







Computer
Dan-PC






-
Security





[ UserID]
S-1-5-18





-
EventData




ErrorSourceCount
4




ErrorRecordFormat
10




ErrorSourceTableLength
4256

zbook said:

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.

Is there anything to do next? Should I try to be finding out about the corrected WHEA errors and narrowing down some other hardware component that may be failing?

Post another zip tomorrow and we will see if there are any new WHEA.
You can continue to use the computer with WHEA errors in the event viewer.
As long as they are corrected WHEA there are no BSOD.
If they were uncorrected WHEA there would be BSOD.
So at this time whatever is producing the errors are being corrected by the hardware and firmware.

If there are WHEA tomorrow then there will not be a day issue to confuse whether it occurred before or after the CPU replacement.
Then the computer could be used in safe mode for several days.
You could then report whether there is any change in performance.
And at the same time we could view the event logs to see if WHEA are or are not occurring while in safe mode.
In general safe mode may be able to remove software issues and if WHEA continue to occur they are more likely hardware related.

Attachment 162985

Latest zip! Thanks for looking, zbook.

The most recent entry on the event log was Date: 2017-11-09T06:50:57.062
The last entry for WHEA on the event logs was Date: 2017-11-08T07:36:10.616
So this is great news as in the nearly 24 hours there were no longer any WHEA posts.

Code:

Event[13904]:  Log Name: System  Source: Microsoft-Windows-WHEA-Logger  Date: 2017-11-08T07:36:10.616  Event ID: 19  Task: N/A  Level: Warning  Opcode: Info  Keyword: N/A  User: S-1-5-19  User Name: NT AUTHORITY\LOCAL SERVICE  Computer: Dan-PC  Description: A corrected hardware error has occurred.Reported by component: Processor CoreError Source: Corrected Machine CheckError Type: Cache Hierarchy ErrorProcessor APIC ID: 4The details view of this entry contains further information.

zbook said:

The most recent entry on the event log was Date: 2017-11-09T06:50:57.062
The last entry for WHEA on the event logs was Date: 2017-11-08T07:36:10.616
So this is great news as in the nearly 24 hours there were no longer any WHEA posts.

Code:

Event[13904]:  Log Name: System  Source: Microsoft-Windows-WHEA-Logger  Date: 2017-11-08T07:36:10.616  Event ID: 19  Task: N/A  Level: Warning  Opcode: Info  Keyword: N/A  User: S-1-5-19  User Name: NT AUTHORITY\LOCAL SERVICE  Computer: Dan-PC  Description: A corrected hardware error has occurred.Reported by component: Processor CoreError Source: Corrected Machine CheckError Type: Cache Hierarchy ErrorProcessor APIC ID: 4The details view of this entry contains further information.

Thanks, zbook!

So, would you assess that I have a relatively "clean bill of health" for my machine at this point?

axe0 said:

It is :)

Thanks, axe0! I'll mark this thread as solved now. I've tried "repping" you guys more but it says I need to "spread it around" more before I can.

I appreciate all the input and help.

Looks fine.
Good luck!
Your welcome.
Let's us know if you have any issues and we'll troubleshoot them.

zbook said:

Looks fine.
Good luck!
Your welcome.
Let's us know if you have any issues and we'll troubleshoot them.

Thank you, zbook! You are the man!