Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

97113

January 17th, 2018 07:00

WHEA-Logger Processor Core Internal Parity Error on 9020

  • OptiPlex 9020
  • Core i7 4790
  • Windows 10 Pro

It seems that ever since the BIOS update and patches were installed for Meltdown/Spectre, I've been getting continuous WHEA-Logger events.

A corrected hardware error has occurred.

Reported by component: Processor Core

Error Source: Corrected Machine Check

Error Type: Internal parity error

Processor APIC ID: # (this number changes)

Is there any incompatibilities with the latest BIOS and the OS patches that might cause this or is my CPU slowly dying? I ran the Intel Processor Diagnostic Tool but everything passed.

February 7th, 2018 07:00

If the registry keys and values don't exist, create them. Alternately, Microsoft has released update KB4078130 to bypass the buggy microcode (I think it basically sets the registry keys for you). You may have to download it manually; I'm not sure if it comes up via Windows Update.

9 Legend

 • 

47K Posts

February 9th, 2018 05:00


Microsoft recommends manually setting the registry key as described below in order to receive the January 2018
security updates.

https://support.microsoft.com/en-us/help/4072699/january-3-2018-windows-security-updates-and-antivirus-software

Setting the Registry Key

Caution Using Registry Editor incorrectly can cause serious problems that may require you to reinstall
your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of
Registry Editor can be solved. Use Registry Editor at your own risk. For information about how to edit
the registry, view the "Changing keys and values" help topic in Registry Editor (Regedit.exe) or view the
"Add and delete information in the registry" and "Edit registry data" help topics in Regedt32.exe.

Note: Customers will not receive the January 2018 security updates (or any subsequent security updates)
and will not be protected from security vulnerabilities unless their antivirus software vendor sets the
following registry key:

Key="HKEY_LOCAL_MACHINE" Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat" **bleep**="cadca5fe-87d3-4b96-b7fb-a231484277cc" Type="REG_DWORD”
Data="0x00000000”

 

February 20th, 2019 21:00

I have been facing the same issue.
No Events found!

Top