Whea-logger a Corrected Hardware Error Has Occurred
[SOLVED] WHEA-Logger Upshot 19 - A Corrected Hardware Error has Occurred.
- Thread starter elliot1396
- Starting time date
- Status
- Non open for further replies.
- #i
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 problems recently merely re-seated the components in my PC on the xiv/01/2021 and Information technology seems to have solved the consequence, or somewhat replaced information technology with the consequence I am now having!
I've plant these (3 identical) Warnings in Consequence Viewer (System).
- I dated to 15/01/2021
- Two dated to 17/01/2021
"A corrected hardware error has occurred.
Reported by component: Processor Core
Error Source: Unknown Error Source
Fault Blazon: No Error
Processor APIC ID: 0
The details view of this entry contains further information."
I'k writing this post as I'm unable to find whatsoever information regarding this.
The Details View is posted below:
|
|
|
|
| MciStat | 0x98004000003e0000 |
| MciMisc | 0xd01a0ffe00000000 |
| RawData | 435045521002FFFFFFFF03000200000002000000680300002F091600110115140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131B248949139377F4BA8F1E0062805C2A3ECDCA19019EDD60100000000000000000000000000000000000000000000000058010000C00000000003000001000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000002000000000000000000000000000000000000000000000018020000400000000003000000000000B0A03EDC44A19747B95B53FA242B6E1D0000000000000000000000000000000002000000000000000000000000000000000000000000000058020000100100000003000000000000011D1E8AF94257459C33565E5CC3F7E80000000000000000000000000000000002000000000000000000000000000000000000000000000057010000000000000002000000000000100F87000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000003000000000000000000000000000000100F8700000818000B32D87EFFFB8B1700000000000000000000000000000000000000000000000000000000000000000200000002000000997CAF771DEDD60100000000000000000000000000000000000000001900000000003E0000400098000000000000000000000000FE0F1AD0000000000000000000048303FF000100000000000000000079000000230000000000000000000000000000000000000000000000000010000000000000001000000000000000100000000000000010001B00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
- #9
I managed to solve it! It was indeed the RAM, running on it's XMP Contour which was causing the result. 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 and so I could be sure of the result, plus enough 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
- Oct 22, 2013
- xix,661
- 714
- 77,190
- 2,971
- #ii
Have latest drivers?
Latest windows updates?
Latest bios?
- #3
Hiya,What hardware in the pc?Take latest drivers?
Latest windows updates?
Latest bios?
All latest drivers, bios & windows update. I likewise perform regular virus checks, I also employ my caput and common sense every bit to what I download and don't....!!
Ryzen 9 3900x
Aorus Ultra x570 motherboard
32gb Ram
1x 1TB m.2 (kicking)
1x 512gb k.2 (storage)
GTX 1080 Fe
EVGA 750w fully modular gilt
No overclocks running asides from the RAM on its 3600mhz contour through bios.
Temperatures stable and monitored
Next check is to check voltage on 12v runway of PSU, haven't got round to this yet.
Spotted someone on the cyberspace mentioning that in 'power settings' setting your drive to 'Never Slumber' had helped them.
This error ONLY occurs when idle and subsequently a length of time, roughly 20-30 mins, where a ability cycle volition occur. This doesn't happen while the machine is in use. I tin can testify this because I've been using the machine for hours on finish, for the event to occur whilst I'grand away from the computer and it is idle.
No issues or anything weird whatsoever other fourth dimension whilst using the pc. Which does pb me away from the idea this could be the psu only worth a bank check anyway.
PC built back in March and was every bit proficient as golden for several months. I tin 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. Stock-still my original BSOD error (I also plant I was running in ram slot 1/three rather than 2/4).
Thanks !
Elliot
- Oct 22, 2013
- nineteen,661
- 714
- 77,190
- two,971
- #4
- #5
Hi!What ram exactly? also 2x16gb or 4x8gb. From one kit?
Information technology'southward 2x 3200mhz 16GB Corsair Vengeance LPX in slots two + 4 on the motherboard which is a x570 Gigabyte Aorus Ultra.
Elliot
- Oct 22, 2013
- 19,661
- 714
- 77,190
- 2,971
- #six
Install latest AMD drivers for the chipset earlier updating if not,
AMD Drivers and Support for Radeon, Radeon Pro, FirePro, APU, CPU, Ryzen, desktops, laptops
Besides look for latest LAN and audio drivers too on the motherboard site. Can attempt for the Intel LAN chip this every bit well,
Intel® Driver & Support Assistant
Run across if WhoCrashed can say what commuter might be an result,
WhoCrashed iii.01- Free Downloads
Recollect y'all however have bsod issues since having bugcheck 0x00000019.
Maybe an usefull vid, would skip the "restore point",
View: https://www.youtube.com/spotter?5=GCzRXMROJAI - #vii
Thanks Vic for your extensive assist!There is a new bios "F33a from 2021-01-22" have that ane 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, laptopsAlso look for latest LAN and sound drivers equally well on the motherboard site. Can endeavor for the Intel LAN chip this also,
Intel® Commuter & Support AssistantEncounter if WhoCrashed can say what driver might exist an outcome,
WhoCrashed three.01- Gratis DownloadsRetrieve you lot still take bsod issues since having bugcheck 0x00000019.
Maybe an usefull vid, would skip the "restore point",
View: https://www.youtube.com/lookout?v=GCzRXMROJAI
Just an update on my progress:
I'1000 now running F33a Bios, AMD Drivers for the chipset are on the latest.
I'1000 on the latest Sound and LAN drivers. I updated every driver on the arrangement I could mayhap notice using DriverEasy.
I've run 'WhoCrashed' and It says I have no valid crash dumps to prove, 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 non be logging these correctly?
I've followed the tutorial in the video you sent. Thank you for that.
In improver, I've removed the XMP Contour on my RAM from the bios (3200 XMP now running at 2133) which is a shame just this is a process of trial and mistake. I seem to be able to remember some kind of a link between the WHEA-logs / difficult crashes occuring since enabling the XMP setting in bios. So far then good with no errors or difficult-restarts (ii-3 hours in).
I've read a few articles about issues with OC'd ram and Ryzen processors. I'1000 non certain 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 y'all'd be able to cast your opinions on this and how it relates to my result. In my opinion, this seems fairly close to what I'g seeing:
Hope you are well and safe!
Cheers once again,
Elliot 
So at present - Fingers crossed for me!
- October 22, 2013
- nineteen,661
- 714
- 77,190
- two,971
- #8
Don't use "driver like shooting fish in a barrel" or such tools to find drivers, just await at the makers site from where the hardware is.
- #ix
I managed to solve it! It was indeed the RAM, running on it's XMP Profile which was causing the outcome. Instead, I manually set the Clock and Voltage in BIOS and I haven't had an event since. I've given it a few days clearance earlier posting this so I could be certain of the upshot, plus plenty of stress tests to ensure stability.
Noted on DriverEasy. I just wanted to be certain I wasn't missing anything.
Cheers to Vic 40 for his assist.
Elliot
- Status
- Not open up for further replies.
| Thread starter | Similar threads | Forum | Replies | Date |
|---|---|---|---|---|
| P | Question PC reboots without warning with Event ID 41 ? | Systems | 0 | |
| 10 | Question How practice I know if my PC is damaged after a serial of unfortunate events? | Systems | 0 | |
 | Question My pc faces random reboots while playing games. Mistake 41, whea logger 18 & mistake 6008 in upshot viewer. | Systems | five | |
| T | Question Kernel Power Crash Event 41 Bugcheck code 0. Driving me Basics. | Systems | iv | |
| Southward | Question Outcome Viewer Whea Logger ID xviii | Systems | 1 | |
 | Question WHEA- Logger Warning Event ID:xix ? | Systems | 0 | |
 | Question Microsoft-Windows-WHEA-Logger | Systems | 18 | |
| Y | Question The Infamous Whea-Logger Mistake | Systems | i | |
| P | Question Reckoner restarts randomly without BSOD while calorie-free gaming, not overheating, somewhat pricey 4 month erstwhile prebuilt. Generally generic Result 41s but..... | Systems | ii | |
| Southward | [SOLVED] New PC difficult crashing with WHEA Logger Result mistake ? | Systems | 1 |
- Advertising
- Cookies Policies
- Privacy
- Term & Conditions
- Topics
0 Response to "Whea-logger a Corrected Hardware Error Has Occurred"
Post a Comment