[SOLVED] WHEA-Logger Event 19 - A Corrected Hardware Error has Occurred.

Status
Not open for further replies.
Jan 17, 2021
7
0
20
Hello!

I've had two Power cycles this evening which logged as a Kernel Power Error. These happened within the space of an hour and were clean, cut outs and restarts without BSOD.

I've been having intermittent BSOD issues recently but re-seated the components in my PC on the 14/01/2021 and It seems to have solved the issue, or somewhat replaced it with the issue I am now having!

I've found these (three identical) Warnings in Event Viewer (System).
  • One dated to 15/01/2021
  • Two dated to 17/01/2021

WHEA-Logger Event 19:

"A corrected hardware error has occurred.

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

The details view of this entry contains further information."

I'm writing this post as I'm unable to find any information regarding this.

The Details View is posted below:

+System

-Provider
[ Name] Microsoft-Windows-WHEA-Logger
[ Guid] {c26c4f3c-3f66-4e99-8f8a-39405cfed220}

EventID19

Version0

Level3

Task0

Opcode0

Keywords0x8000000000000000

-TimeCreated
[ SystemTime] 2021-01-17T22:09:48.1932654Z

EventRecordID367255

-Correlation
[ ActivityID] {f43627bf-3a62-4a70-ad90-f987342e3b34}

-Execution
[ ProcessID] 5144
[ ThreadID] 6224

ChannelSystem

ComputerElliot-Primary

-Security
[ UserID] S-1-5-19

-EventData

ErrorSource0

ApicId0

MCABank25

MciStat0x98004000003e0000

MciAddr0x0

MciMisc0xd01a0ffe00000000

ErrorType0

TransactionType256

Participation256

RequestType256

MemorIO256

MemHierarchyLvl256

Timeout256

OperationType256

Channel256

Length872

RawData435045521002FFFFFFFF03000200000002000000680300002F091600110115140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131B248949139377F4BA8F1E0062805C2A3ECDCA19019EDD60100000000000000000000000000000000000000000000000058010000C00000000003000001000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000002000000000000000000000000000000000000000000000018020000400000000003000000000000B0A03EDC44A19747B95B53FA242B6E1D0000000000000000000000000000000002000000000000000000000000000000000000000000000058020000100100000003000000000000011D1E8AF94257459C33565E5CC3F7E80000000000000000000000000000000002000000000000000000000000000000000000000000000057010000000000000002000000000000100F87000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000003000000000000000000000000000000100F8700000818000B32D87EFFFB8B1700000000000000000000000000000000000000000000000000000000000000000200000002000000997CAF771DEDD60100000000000000000000000000000000000000001900000000003E0000400098000000000000000000000000FE0F1AD0000000000000000000048303FF000100000000000000000079000000230000000000000000000000000000000000000000000000000010000000000000001000000000000000100000000000000010001B00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
 
Solution
An Update on the Issue:

I managed to solve it! It was indeed the RAM, running on it's XMP Profile which was causing the issue. Instead, I manually set the Clock and Voltage in BIOS and I haven't had an issue since. I've given it a few days clearance before posting this so I could be sure of the result, plus plenty of stress tests to ensure stability.

Noted on DriverEasy. I just wanted to be sure I wasn't missing anything.

Thanks to Vic 40 for his help.

Elliot
Jan 17, 2021
7
0
20
What hardware in the pc?

Have latest drivers?
Latest windows updates?
Latest bios?

Hiya,

All latest drivers, bios & windows update. I also perform regular virus checks, I also use my head and common sense as to what I download and don’t....!!

Ryzen 9 3900x
Aorus Ultra x570 motherboard
32gb Ram
1x 1TB m.2 (boot)
1x 512gb m.2 (storage)
GTX 1080 FE
EVGA 750w fully modular gold

No overclocks running asides from the RAM on its 3600mhz profile through bios.

Temperatures stable and monitored

Next check is to check voltage on 12v rail of PSU, haven’t got round to this yet.

Spotted someone on the internet mentioning that in ‘power settings’ setting your drive to ‘Never Sleep’ had helped them.

This error ONLY occurs when idle and after a length of time, roughly 20-30 mins, where a power cycle will occur. This doesn’t happen while the machine is in use. I can prove this because I’ve been using the machine for hours on end, for the event to occur whilst I’m away from the computer and it is idle.

No issues or anything weird any other time whilst using the pc. Which does lead me away from the idea this could be the psu but worth a check anyway.

PC built back in March and was as good as gold for several months. I can roughly link this error from when I gave my pc a service a few weeks ago, updated bios, chipset drivers, system drivers, reseated all the components and cleaned them. Fixed my original BSOD error (I also found I was running in ram slot 1/3 rather than 2/4).

Thanks !
Elliot
 

Vic 40

Titan
Ambassador
There is a new bios "F33a from 2‎021-01-22" have that one already?
Install latest AMD drivers for the chipset before updating if not,
AMD Drivers and Support for Radeon, Radeon Pro, FirePro, APU, CPU, Ryzen, desktops, laptops

Also look for latest LAN and sound drivers as well on the motherboard site. Can try for the Intel LAN chip this as well,
Intel® Driver & Support Assistant

See if WhoCrashed can say what driver might be an issue,
WhoCrashed 3.01- Free Downloads

Think you still have bsod issues since having bugcheck 0x00000019.

Maybe an usefull vid, would skip the "restore point",
View: https://www.youtube.com/watch?v=GCzRXMROJAI
 
Jan 17, 2021
7
0
20
There is a new bios "F33a from 2‎021-01-22" have that one already?
Install latest AMD drivers for the chipset before updating if not,
AMD Drivers and Support for Radeon, Radeon Pro, FirePro, APU, CPU, Ryzen, desktops, laptops

Also look for latest LAN and sound drivers as well on the motherboard site. Can try for the Intel LAN chip this as well,
Intel® Driver & Support Assistant

See if WhoCrashed can say what driver might be an issue,
WhoCrashed 3.01- Free Downloads

Think you still have bsod issues since having bugcheck 0x00000019.

Maybe an usefull vid, would skip the "restore point",
View: https://www.youtube.com/watch?v=GCzRXMROJAI
Thanks Vic for your extensive help!

Just an update on my progress:

I'm now running F33a Bios, AMD Drivers for the chipset are on the latest.
I'm on the latest Sound and LAN drivers. I updated every driver on the system I could possibly find using DriverEasy.

I've run 'WhoCrashed' and It says I have no valid crash dumps to show, despite them being enabled with a valid directory listed. I wonder if this is due to the hard system crashes as apposed to a BSOD which may not be logging these correctly?

I've followed the tutorial in the video you sent. Thank you for that.

In addition, I've removed the XMP Profile on my RAM from the bios (3200 XMP now running at 2133) which is a shame but this is a process of trial and error. I seem to be able to remember some kind of a link between the WHEA-logs / hard crashes occuring since enabling the XMP setting in bios. So far so good with no errors or hard-restarts (2-3 hours in).

I've read a few articles about issues with OC'd ram and Ryzen processors. I'm not sure how relatable this is seeing as (from what I remember) an overclock is considered from 3600 mhz +, I'm only getting to 3200 Max.

I did come accross this fairly interesting article. I wonder if you'd be able to cast your opinions on this and how it relates to my issue. In my opinion, this seems fairly close to what I'm seeing:

Hope you are well and safe!

Thanks again,
Elliot :)



So now - Fingers crossed for me!
 
Jan 17, 2021
7
0
20
An Update on the Issue:

I managed to solve it! It was indeed the RAM, running on it's XMP Profile which was causing the issue. Instead, I manually set the Clock and Voltage in BIOS and I haven't had an issue since. I've given it a few days clearance before posting this so I could be sure of the result, plus plenty of stress tests to ensure stability.

Noted on DriverEasy. I just wanted to be sure I wasn't missing anything.

Thanks to Vic 40 for his help.

Elliot
 
Solution
Status
Not open for further replies.