-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
- HP Community
- Notebooks
- Notebook Boot and Lockup
- Occasional BSOD afetr Bios update

Create an account on the HP Community to personalize your profile and ask a question
01-26-2018 10:49 AM
HP recently pushed out a bios update to my HP Pro x2 612 G1 to combat the Intel security issues. It is bios v1.42. My previous bios was v1.38. The machine boots and runs fine.However since the update I have been getting a BSOD at least once a day with messages like "whea - uncorrectable error" or "IRQ not less or Equal" This occurs even when I'm away from the keyboard.
I have checked to make sure all drivers are updated and re-installed a few. I tried reinstalling the old bios but it didn't work. After reading the faq that came with the update I realized that this was not an option, specifically said I could not go back.
Checking the events log I noticed a new warning message that occurs fairly often that i did not have before the bios update. See below:
This issue is being reported by the Windows DIagnostic Policy Service and I think it may have something to do with the SSD as the process monitor shows a Fast IO disallowed message folllowed by a buffer to small error which is corrected after 2 more tries.
Pretty sure this is an issue with the bios update but when I called HP support they didn't even know I could not revert to my previous bios. Any ideas on how to fix this and how do I file a bug report with HP over the bad bios? HP is sending me a return box but I was hoping I could fix this as I'm not in a position to lose the computer for a couple of weeks.
Thanks for any help in advance
Marty
-------------------------------------------------
Reported by component: Processor Core
Error Source: Corrected Machine Check
Error Type: Internal parity error
Processor APIC ID: 2
System
- EventData
435045521002FFFFFFFF0300020000000200000060030000252010001A0112140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131B18BCE2DD7BD0E45B9AD9CF4EBD4F8906A5EB3C06E96D30100000000000000000000000000000000000000000000000058010000C00000000003000001000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000002000000000000000000000000000000000000000000000018020000400000000003000000000000B0A03EDC44A19747B95B53FA242B6E1D0000000000000000000000000000000002000000000000000000000000000000000000000000000058020000080100000003000000000000011D1E8AF94257459C33565E5CC3F7E800000000000000000000000000000000020000000000000000000000000000000000000000000000570100000000000000020800000000005106040000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000000000000000000000030000000000000002000000000000005106040000081002BFFBDA7FFFFBEBBF000000000000000000000000000000000000000000000000000000000000000001000000010000007EC3DB46C396D30102000000000000000000000000000000000000000000000005000F00000100D0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Solved! Go to Solution.
Accepted Solutions
01-29-2018 09:29 AM
In case anybody else runs into this problem.
The problem was due to Intels's fix to the Spectre exploit. Intel's bios microcode was bad and so the bios update created problems. Microsoft issued a patch that disabled the Intel code and fixed the problem. You can read more about it here http://www.zdnet.com/article/windows-emergency-patch-microsofts-new-update-kills-off-intels-spectre-...
HP tech support had no knowledge of this. I guess no one here had info either.
01-29-2018 09:29 AM
In case anybody else runs into this problem.
The problem was due to Intels's fix to the Spectre exploit. Intel's bios microcode was bad and so the bios update created problems. Microsoft issued a patch that disabled the Intel code and fixed the problem. You can read more about it here http://www.zdnet.com/article/windows-emergency-patch-microsofts-new-update-kills-off-intels-spectre-...
HP tech support had no knowledge of this. I guess no one here had info either.