AMD Ryzen 7 2700 eventid 19 "Cache Hierarchy Error"

[McChingus]

755 G5's in stock and not a single one works.  out of the box have blue screen and performance issues with my companies image and with the OEM image (install it is shipped with).  All three display repeatedly in the event viewer "WHEA-Logger eventid: 19 Cache Hierarchy Error".

I have done a considerable amount of troubleshooting and research regarding this.  The best I can find is on gamer forums where voltage issues or BIOS versions cause this.  I have not been able to clear this out and wondering if anyone else has had a similar issue. 

A corrected hardware error has occurred.

Reported by component: Processor Core
Error Source: Corrected Machine Check
Error Type: Cache Hierarchy Error
Processor APIC ID: 4

The details view of this entry contains further information.

+ 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] 2019-03-18T15:44:20.487286500Z

      EventRecordID 72506     - Correlation

      [ ActivityID] {1D9B6EA8-B847-47EA-9E61-4D472B8FB455}

    - Execution

      [ ProcessID] 4336       [ ThreadID] 4604

      Channel System       Computer BHQ-L-3237.Oldline.com     - Security

      [ UserID] S-1-5-19

- EventData

    ErrorSource 1     ApicId 4     MCABank 1     MciStat 0xd0200000000a0151     MciAddr 0x0     MciMisc 0x0     ErrorType 9     TransactionType 0     Participation 256     RequestType 5     MemorIO 256     MemHierarchyLvl 1     Timeout 256     OperationType 256     Channel 256     Length 928     RawData 435045521002FFFFFFFF03000200000002000000A0030000132C0F00120313140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131B18BCE2DD7BD0E45B9AD9CF4EBD4F890B96B4EAD9DDDD40100000000000000000000000000000000000000000000000058010000C00000000003000001000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000002000000000000000000000000000000000000000000000018020000800000000003000000000000B0A03EDC44A19747B95B53FA242B6E1D0000000000000000000000000000000002000000000000000000000000000000000000000000000098020000080100000003000000000000011D1E8AF94257459C33565E5CC3F7E8000000000000000000000000000000000200000000000000000000000000000000000000000000007F010000000000000002010300010000100F81000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000400000000000000000000000000000000000000000000000000000000000000000000000000000007000000000000000400000000000000100F8100000808040B32D87EFFFB8B170000000000000000000000000000000000000000000000000000000000000000F50157A5EFE3DE43AC72249B573FAD2C01000000000000009F00542000000000000000000000000000000000000000000000000000000000000000000000000002000000020000008CB45273A1DDD40104000000000000000000000000000000000000000100000051010A00000020D0000000000000000000000000000000000000000004000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

[Putins]

Hi, McChingus

You're not alone.

I have a Elitebook 735G5 with Ryzen 7 pro 2700u with same problem.

Actually the problem happened since HP release BIOS update 01.03.01.

BIOS version from 01.03.01 to the latest 01.06.01 all have same bug, they didn't fix this.

If you don't want to see this error information, you can downgrade BIOS to 01.00.03.

01.00.04 has a nvme ssd running on pcie 3.0 x1 bug.

Once again, I hope HP fix this bug ASAP!

[McChingus]

Thanks for the input Putins.  Rolling back BIOS is not an option due to some of the issues newer versions address.

I will keep opening cases with HP, maybe they will fix it one day.  I have had to go with a different build for laptops since this caused so many issues for us.

[Putins]

McChingus, as I looking into the changlog of BIOS updates, didn't find anything really impact daily use if you choose rolling back to old version, and I don't have wierd issues with 01.00.03 BIOS

So I think it's a option at leaset for people who doesn't want to see the error event crazy increasing (about 3 error events per minute)

[BK_Ha]

I have exactly the same issue with Elitebook 745 G5 Ryzen 7 Pro 2700U.

Please fix this.

Whereas since those are all 'corrected errors' not causing usabilty issues so far, this causes stability concern to me.

[BK_Ha]

Fixed by BIOS 01.07.00