WHEA-Logger Error 19

Question

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!

Answer 1

Hi,

The issue you appear to be having is discussed in the following link;

https://www.dell.com/community/Optiplex/WHEA-Logger-Processor-Core-Internal-Parity-Error-on-9020/td-p/5668927

You may have to disable mitigation against Spectre, Variant 2.

You could use InSpectre to analyze the situation:

https://www.grc.com/inspectre.htm

Answer 2

The script referenced in this workaround appears to have done the trick. I've been running for about a half hour with not WHEA-Logger errors. After the update, the events would start immediately and continue every 60 seconds. I've flagged your note as the answer. Thank you.

Answer 3

I'm getting ready to test this workaround. What looks helpful is that the Dell workaround is derived from a Lenovo discussion. (I'm using a ThinkPad.) Even better, the workaround appears to have been tested and results posted. Always a good sign. I will let you know how this turns out.

Phil

Answer 4

Sorry, the release notes for the update aren't helpful.

This isn't a device manager error. It is a WHEA-Logger error stored in the system events. Everything functions fine until either update is applied, then the error shows up basically every minute, on the minute. I pasted a copy of the error message in my original message. I can add the detail, too, if that would be helpful. Thanks.

Answer 5

Hi,

For known issues and possible workaround for the  KB4058258 update, kindly refer to this link. Meanwhile, for the error 19 that you're getting, there are several steps that you can do to troubleshoot this. Click this linkand follow the methods provided.

Get back to us if you need further assistance.