Solved!
Go to SolutionM
MarcLaflamme
1 Rookie
•
20 Posts
0
99107
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.
94476
0
Posted January 17th, 2018 07:00
A CPU hardware error is very possible. I had a "WHEA" error that kept coming up on an Intel CPU (i7 3770) and it passed all hardware tests, including the Intel CPU test. I do some PC support and repair and had spare parts. I swapped everything except the CPU and still had the problem. I didn't have another spare i7 3770 but I had an i5 3550 and installed that and no more problems. I sent the i7 to Intel for warranty service and they sent a replacement i7 and I installed that.
However, a BIOS error can also cause this. Clear the CMOS (BIOS) memory (with the PC powered off) by opening the case and removing the CR2032 CMOS Memory backup battery for AT LEAST 10 minutes. Replace the battery and power on. If there were any customized BIOS settings they will have to be re-entered.
Aside from the possibility of a CPU hardware problem, see this from Microsoft
Inspiron 16 5630 Laptop and WD22TB4 Docking StationSelf-built desktop for recording studio application94462
0
Posted January 17th, 2018 13:00
Thanks I'll give your suggestions a try.
94416
0
Posted January 18th, 2018 05:00
Thank you so much for this information! It was a little harder to find because I was restricting my searches to Dell yet these issues are happening on all other vendors systems.
93994
0
Posted January 20th, 2018 00:00
Does this workaround also apply to the Optiplex 9020M?
93857
0
Posted January 20th, 2018 21:00
I can confirm that the solution has solved the problem on my 9020M.
Kudos to Marc-CED for this solution. Many thanks.
93155
0
Posted January 23rd, 2018 07:00
We have encountered the same issues with several OptiPlex 7020 systems. I have not yet tested the solutions on them.
92957
0
Posted January 24th, 2018 03:00
Many thanks Marc-CED
This solution also worked for Precision M4800.
56324
1
Posted January 25th, 2018 18:00
A more user friendly way to disable and enable the Microsoft fixes for the Meltdown Spectre security bug is to download InSpectre from Gibson Research Corp. This tiny program verfies if you have the flaws, the status of your current configuration and performance impact. It also has the ability to disable and enable from Windows the fixes Microsoft has issued. Word of caution make sure you download this only direct from the official Gibson Research Corp. website.
9407
1
Posted January 30th, 2018 12:00
Microsoft now admits the bug and is offering an optional update to disable one of the mitigations:
https://www.bleepingcomputer.com/news/microsoft/microsoft-issues-windows-out-of-band-update-that-disables-spectre-mitigations/
Marc-CED
15 Posts
94456
3
Posted January 17th, 2018 15:00
Same Issue. Dell Precision Workstations. All 10 of them. Blue Screen on one.
Cause: Microsoft Meltdown and Spectre Mitigations
Here is the Workaround -
First make a Windows System Restore Point.
https://www.computerhope.com/issues/ch001334.htm
Run this script (as administrator) to disable the Meltdown and Spectre Mitigations by Microsoft - reboot required. Save as a .bat file:
https://www.manageengine.com/products/desktop-central/script-templates/others/disable-mitigations-for-meltdown-spectre.html
First Determinate if you are at risk if you disable the mitigations. Opinion: The risk is very low for the vast majority of users.
https://www.networkworld.com/article/3245813/security/meltdown-and-spectre-exploits-cutting-through-the-fud.html
Also determine if you only need to disable only one of the two mitigations:
https://forums.lenovo.com/t5/ThinkPad-T400-T500-and-newer-T/KB4056892-multiple-problems-on-T440s/m-p/3938695
0 = Both CVE-2017-5715 and CVE-2017-5754 enabled (WHEA Errors)
1 = CVE-2017-5754 Enabled Only (No WHEA Errors)
2 = CVE-2017-5715 Enabled Only (WHEA Errors)
3 = Both Disabled (No WHEA Errors)
Note: I have not yet tested downgrading the bios and leaving the Microsoft mitigation enabled.
To Turn it Back On, see: https://support.microsoft.com/en-us/help/4072698/windows-server-guidance-to-protect-against-the-speculative-execution
Also Read Carefully: https://support.microsoft.com/en-us/help/4072699/january-3-2018-windows-security-updates-and-antivirus-software
-----------------------
Intel says new firmware patches trigger reboots in Haswell and Broadwell systems:
https://www.computerworld.com/article/3247788/computer-hardware/intel-says-new-firmware-patches-trigger-reboots-in-haswell-and-broadwell-systems.html
Issue: Thousands of Event ID 19 - random blue screens.
Event ID 19 WHEA-Logger
A corrected hardware error has occurred.
Reported by component: Processor Core
Error Source: Corrected Machine Check
Error Type: Internal parity error
Processor APIC ID: 0
-------------------