Windows 10: WHEA-Logger A fatal hardware error has occurred...

...A record describing the condition is contained in the data section of this event.


I want to know how to decode the RawData numbers in this error. Please don't tell me how to fix it or what could be causing it or try to troubleshoot, or ask me whether or not I'm having BSOD, etc. I just want to know how to decode it. I can't find one article on the web that can tell me this. It's driving me nuts. I fix most of my own computer issues and generally don't need assistance. But when Windows is reporting an error and won't tell me what the error is and there's no obvious way to figure it out, it's infuriating.


As you can see from the RawData below, it's just a bunch of numbers. I need to know what to do with this. Thanks.


XML view Details:

-<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
-<System>
<Provider Name="Microsoft-Windows-WHEA-Logger" Guid="{c26c4f3c-3f66-4e99-8f8a-39405cfed220}" />
<EventID>1</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000002</Keywords>
<TimeCreatedSystemTime="2020-08-11T20:57:51.3842954Z" />
<EventRecordID>9922</EventRecordID>
<CorrelationActivityID="{a6cd5011-d2ef-4ff9-9d88-f41cf34fae36}" />
<Execution ProcessID="5056" ThreadID="9700" />
<Channel>System</Channel>
<Computer>DESKTOP-MRMVGE4</Computer>
<Security UserID="S-1-5-19" />
</System>
-<EventData>
<Data Name="Length">462</Data>
<Data Name="RawData">435045521002FFFFFFFF01000100000007000000CE010000323914000B0814143C60C1835215A74887D114D9467D7765000000000000000000000000000000008D7C2157665EFB4480339B74CACEDF5B03F83300702E884E992C6F26DAF3DB7ACE71BACFD56FD601080000000000000000000000000000000000000000000000C8000000060100000003020001000000000000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000053544F52504F525401000601A4000000010003000B000000970ED827D415F1A1295833C1EF57DA5B730074006F00720061006800630069000000000000000000000000000000000053414D53554E4720004844313033534A00000000000000000000A4000000A400000031E0100000000000160001000000000064EB0000000000000B000000000000000000000000000000000000001100000005000000020000005F000000AC0000000000000000000000000000000000000000000000000000000000000000000000000000000000000056000000000000006C000000640000000700000007000000000000000200000000000000000000000A000000000000003B010000</Data>
</EventData>
</Event>

:)

 

WHEA-Logger Error 19

When I installed the January 2018 cumulative update, I started getting consistent WHEA-Logger errors about every 60 seconds. Here's what's in the event viewer:

A corrected hardware error has occurred.

Reported by component: Processor Core

Error Source: Corrected Machine Check

Error Type: Internal parity error

Processor APIC ID: 2

I also started getting random blue/green screen crashes. I did a system restore to before the update, and everything went back to normal: no logger errors and no crashes. I waited for the next cumulative update (KB4058258), then installed that figuring that
the problem would be sorted out.

Nope. The logger errors are back. The system hasn't crashed yet, but I'm living in dread. Looks like I'll roll back to the pre-January state so that I can keep working without fearing for loss of data.

Does anyone know a fix/workaround for this? Please don't suggest doing clean Windows install or a reset. In addition to making a mess of things, it's not relevant. This is simple: remove the update and the problem goes away. Apply the update problem comes
back. It's the update. It's not my Windows installation. Thanks!

 

Event ID 19 WHEA-Logger

I just received two Event ID 19 WHEA-Logger's tonight, "Reported by component: Processor Core"

Google led me to a Ten forums thread that seems to indicate this Meltdown and Spectre patch related. Has anyone else had these or know anything more about it?

Event ID 19 WHEA-Logger - Hardware Error - BSOD - Meltdown Spectre - Windows 10 Forums

 

9900K WHEA LOGGER Internal parity error or cache hierarch error.

Hi my pc:

9900K OC sync all cores was 50

2x16GB DDR4 GSKILL 3000MHZ xmp

Corsair 850RmX

Asus Prime Z390-A

On 5ghz with voltage 1.320v i had very rarely Whea Logger 19 Internal Parity error during game in Metro Exodus.

So rarely like 1 pop up Whea in 1 month.

Also on Realbench on 1.320v i had Whea Logger 19 Cache Hierarchy Error.

So i bumped to 1.330v and 2 months was fine. But yesterday in Battlefield 5 Whea Logger 19 Internal Parity error pop up in Battlefield 5 on 1.330V.

1.320v - Whea 19 Internal Parity Error (1 in 3-4 months ) in Metro Exodus

1.320v - Whea 19 Cache Hierarchy Error in Realbench

1.330v - Whea 19 Internal Parity Error ( 1 in 3 months ) in Battlefield 5

1.330v - no Wheas in Realbench

I am actually 9900K on stock 4700ghz,all auto in UEFI.

And my question. Is Whea Logger 19 Internal Parity Error related to insufficent Vcore ? Cache hierarchy the same?