• ×
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
  • ×
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
Guidelines
Do you need help resolving ACPI Errors ACPI\VEN_BOOT&DEV_0000 and ACPI\VEN_PRP&DEV_0001 on HP Chromebook G2? Click here for the troubleshooting steps.
HP Recommended

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

    - Provider
      [ Name] Microsoft-Windows-WHEA-Logger       [ Guid] {C26C4F3C-3F66-4E99-8F8A-39405CFED220}
      EventID 19       Version 0       Level 3       Task 0       Opcode 0       Keywords 0x8000000000000000     - TimeCreated
      [ SystemTime] 2018-01-26T16:32:38.549269500Z
      EventRecordID 13792     - Correlation
      [ ActivityID] {ED19A5BC-06AB-43DA-9FEF-A1E3AAB75B55}
    - Execution
      [ ProcessID] 11316       [ ThreadID] 7176
      Channel System           - Security
      [ UserID] S-1-5-19

- EventData

    ErrorSource 1    
ApicId 2    MCABank 0     MciStat 0xd0000100000f0005     MciAddr 0x0     MciMisc 0x0     ErrorType 12     TransactionType 256     Participation 256     RequestType 256     MemorIO 256     MemHierarchyLvl 256     Timeout 256     OperationType 256     Channel 256     Length 864    
 
RawData

435045521002FFFFFFFF0300020000000200000060030000252010001A0112140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131B18BCE2DD7BD0E45B9AD9CF4EBD4F8906A5EB3C06E96D30100000000000000000000000000000000000000000000000058010000C00000000003000001000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000002000000000000000000000000000000000000000000000018020000400000000003000000000000B0A03EDC44A19747B95B53FA242B6E1D0000000000000000000000000000000002000000000000000000000000000000000000000000000058020000080100000003000000000000011D1E8AF94257459C33565E5CC3F7E800000000000000000000000000000000020000000000000000000000000000000000000000000000570100000000000000020800000000005106040000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000000000000000000000030000000000000002000000000000005106040000081002BFFBDA7FFFFBEBBF000000000000000000000000000000000000000000000000000000000000000001000000010000007EC3DB46C396D30102000000000000000000000000000000000000000000000005000F00000100D0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

1 ACCEPTED SOLUTION

Accepted Solutions
HP Recommended

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.

View solution in original post

1 REPLY 1
HP Recommended

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.

† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the <a href="https://www8.hp.com/us/en/terms-of-use.html" class="udrlinesmall">Terms of Use</a> and <a href="/t5/custom/page/page-id/hp.rulespage" class="udrlinesmall"> Rules of Participation</a>.