Question Constant random restarts - WHEA-Logger event 19

Apr 30, 2023
2
0
10
Hey all,

Wondering if anyone can offer any advice,
over the past month my computer has been black screening repeatedly ( 2-4 times a day or 15-20 times a day, seems random) and restarting without a BSOD, this can be at complete idle, or at a decent to high load.

In event viewer I'm constantly getting recurring WHEA-Logger Event 19 errors , which I'll post below. this can occur almost every second or stop for 5-10 minutes before occurring.
The restarting is always immediately after a WHEA-Logger event 19 ID error,

PC Built: 24/01/2023 (all parts new apart 2 SSD's )
OS: Windows 10 Pro 64-bit
CPU: AMD Ryzen 9 5900X 12-Core Processor
MOBO: Gigabyte B550 GAMING X V2 (Rev 1.2)
RAM: 2x 16 GB sticks of Kingston 3200Mhz
Graphics: RX6650 XT (8Gb)
Storage: 1* HDD(new) 1* NVME (new) 2* SSD (old)
PSU: 800W

CPU TEMPS - IDLE = 35C / High load = 75C
GPU TEMPS - IDLE = 53C / High load = 69C

What tests have i done?
Memtest64 - no errors
AV: clean pc
multiple Prime95: no errors on cpu testing
multiple Furmark for Gpu load, no errors
Multiple Cpu and GPU stress test at the same time to simulate high PSU load

What have i tried to fix this?
SFC checker- No change
DISM repair - No change
Updated CPU and Graphics drivers - no change
Some threads mentions disabling C-State to stop potential crashes, - Disabled - No change
Some threads mentions disabling XMP on Ram, Disabled and then further underclocked ram to 3000Mhz (just in case)- No Change
In Windows safe mode - No change

Fresh install of windows (with windows drivers only) - No Change
Fresh install of windows with full amd / gigabyte drivers - No change

Updated Bios to latest release and now left on basic bios, with C-State disabled and left RAM in under frequency-ed state at 2400Mhz - No Change.

Windows logs not generating so I'm unable to provide crash dumps. Sorry

Recurring error is below:

Log Name: System
Source: Microsoft-Windows-WHEA-Logger
Date: 30/04/2023 12:18:43
Event ID: 19
Task Category: None
Level: Warning
Keywords:
User: LOCAL SERVICE
Computer: DESKTOP-0RMN3M7
Description:
A corrected hardware error has occurred.

Reported by component: Processor Core
Error Source: Unknown Error Source
Error Type: Cache Hierarchy Error
Processor APIC ID: 0

The details view of this entry contains further information.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WHEA-Logger" Guid="{c26c4f3c-3f66-4e99-8f8a-39405cfed220}" />
<EventID>19</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2023-04-30T11:18:43.2573221Z" />
<EventRecordID>4991</EventRecordID>
<Correlation ActivityID="{56b4793e-c339-4f9a-b61b-45c2477bdf3c}" />
<Execution ProcessID="4748" ThreadID="5148" />
<Channel>System</Channel>
<Computer>DESKTOP-0RMN3M7</Computer>
<Security UserID="S-1-5-19" />
</System>
<EventData>
<Data Name="ErrorSource">0</Data>
<Data Name="ApicId">0</Data>
<Data Name="MCABank">14</Data>
<Data Name="MciStat">0x9c2040000404010b</Data>
<Data Name="MciAddr">0x320d7e0</Data>
<Data Name="MciMisc">0xd01a0ffe00000000</Data>
<Data Name="ErrorType">9</Data>
<Data Name="TransactionType">2</Data>
<Data Name="Participation">256</Data>
<Data Name="RequestType">0</Data>
<Data Name="MemorIO">256</Data>
<Data Name="MemHierarchyLvl">3</Data>
<Data Name="Timeout">256</Data>
<Data Name="OperationType">256</Data>
<Data Name="Channel">256</Data>
<Data Name="Length">936</Data>
<Data Name="RawData">435045521002FFFFFFFF03000200000002000000A80300002A120B001E0417140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131B248949139377F4BA8F1E0062805C2A34E107033557BD90100000000000000000000000000000000000000000000000058010000C00000000003000001000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000002000000000000000000000000000000000000000000000018020000800000000003000000000000B0A03EDC44A19747B95B53FA242B6E1D0000000000000000000000000000000002000000000000000000000000000000000000000000000098020000100100000003000000000000011D1E8AF94257459C33565E5CC3F7E8000000000000000000000000000000000200000000000000000000000000000000000000000000007F010000000000000002010000030000120FA2000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000007000000000000000000000000000000120FA200000818000B32F87EFFFB8B170000000000000000000000000000000000000000000000000000000000000000F50157A5EFE3DE43AC72249B573FAD2C03000000000000009F00C20000000000E0D7200300000000000000000000000000000000000000000000000000000000020000000200000058064685557BD90100000000000000000000000000000000000000000E0000000B0104040040209CE0D720030000000000000000FE0F1AD0000000000000000000073520B00007000D02471A72C50000FF010000250000000000000000000000000000000000000000000000000010000000000000001000000000000000100000000000000010003B00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000</Data>
</EventData>
</Event>
 
Error Type: Cache Hierarchy Error
Some of the main hardware problems which cause machine check exceptions include:

  1. System bus errors (error communicating between the processor and the motherboard)
  2. Memory errors that may include parity and error correction code (ECC) problems. Error checking ensures that data is stored correctly in the RAM; if the information is corrupted, then random errors occur.
  3. Cache errors in the processor; the cache stores important data and code. If this is corrupted, errors often occur.
  4. Poor voltage regulation (i.e. power supply problem, voltage regulator malfunction, capacitor degradation)
  5. Damage due to power spikes
  6. Static damage to the motherboard
  7. Incorrect processor voltage setting in the BIOS (too low or too high)
  8. Overclocking
  9. Permanent motherboard or power supply damage caused by prior overclocking
  10. Excessive temperature caused by insufficient airflow (possibly caused by fan failure or blockage of air inlet/outlet)
  11. Improper BIOS initialization (the BIOS configuring the motherboard or CPU incorrectly)
  12. Installation of a processor that is too much for your motherboard to handle (excessive power requirement, incompatibility)
  13. Defective hardware that may be drawing excessive power or otherwise disrupting proper voltage regulation
 

Aeacus

Titan
Ambassador
The power supply was new, bought in Jan 2023
Sorry i misspoke 750W

AeroCool Integrator Mod Xt 750W Power Supply, Semi-Modular, 80 Plus Bronze

Part no:

ACPB-IT75AKC​


Your hardware, the rest of it, is quite expensive. So, why oh why did you cheap out on a PSU? :??: Do you really do not care if the borderline crap quality PSU fries your system? :rolleyes:
Also, you should know that the PSU is the most important component inside the PC, since it powers everything, right?

And yes, your Aerocool unit is terrible, borderline crap. For 2nd opinion;
PSU Tier List: https://forums.tomshardware.com/thr...er-list-rev-14-8-final-update-jul-21.3624094/
Look under Tier D, low priority unit (named as Aerocool Integrator).

That being said, i'd throw out the crap PSU you have, buy good quality PSU (no cheaping out this time :no: ) and cross the fingers that your Aerocool unit didn't damage anything else (albeit, that hope is slim, based on symptoms you're experiencing).

For good quality PSU, look towards Seasonic Focus/PRIME or Corsair RM/RMe/RMi/RMx/HX/HXi/AX/AXi, in 750W range (all these units are Tier A).

Once you have proper PSU, then look if you still get your issues.
If you don't, great.
if you do, time to open up the wallet and replace the components damaged by your Aerocool PSU. I'd start with CPU replacement, since many symptoms point towards damaged CPU.