Install the app
How to install the app on iOS

Follow along with the video below to see how to install our site as a web app on your home screen.

Note: This feature may not be available in some browsers.

W10 Event Viewer Event ID: 19 error

BORIKKEN21

Member
Joined
Nov 3, 2020
Messages
7
Hi guys!

I’ve got a system built with a i5-4460 for some years now, I’ve formatted windows 10 and for 5 days now it reboots out of nowhere, on Event viewer it gives me this error

"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 ID: 19

I’ve upgraded the asus HB1M-R motherboard firmware to 3602 that has a fix for the 1. Update CPU Microcode 2. Improve system security and stability.

I’ve used the debloat script from ChrisTitus that disables the mitigation Spectre and Meltdown, and followed this workaround post.

Nothing makes the Event Viewer Event 19, WHEA-Logger go away, and I didn’t get a change to test another CPU from the same architecture.
 
Nothing makes the Event Viewer Event 19, WHEA-Logger go away, and I didn’t get a change to test another CPU from the same architecture.
Well that would be a great start. Were you ever naughty to your i5? It's kind of rare to see an Intel CPU failure unless they are mistreated. The big question becomes this is not some bleeding edge hardware we are talking about. So from your post it looks like the problem showed up after your fresh Win 10 install. What prompted you to do that refresh in the first place? I am just grabbing at straws here trying to figure out what direction you were coming from b/c I think that may hold the answer.
 
Well that would be a great start. Were you ever naughty to your i5? It's kind of rare to see an Intel CPU failure unless they are mistreated. The big question becomes this is not some bleeding edge hardware we are talking about. So from your post it looks like the problem showed up after your fresh Win 10 install. What prompted you to do that refresh in the first place? I am just grabbing at straws here trying to figure out what direction you were coming from b/c I think that may hold the answer.

The psu got replaced because it wouldn't turn on, after it came back from the MSP it didn't boot, corrupted windows install with various errors, and it haven't been refreshed for years. So that's why I reinstalled W10
 
Sorry to be Mr. Happy but at first glance given the symptoms I'd guess the PSU took out the mobo when it failed. Given a PSU failure is pretty rare these days since the bogus electrolytic capacitor problem is pretty much done ( I haven't seen a swollen cap in years now) who knows if it didn't send a voltage spike into the mobo and fried selective systems.
If at all possible test all the anticillary components in a working system and work backwards from there. My money is still unfortunately on the mobo.
 
Sorry to be Mr. Happy but at first glance given the symptoms I'd guess the PSU took out the mobo when it failed. Given a PSU failure is pretty rare these days since the bogus electrolytic capacitor problem is pretty much done ( I haven't seen a swollen cap in years now) who knows if it didn't send a voltage spike into the mobo and fried selective systems.
If at all possible test all the anticillary components in a working system and work backwards from there. My money is still unfortunately on the mobo.
This might be really possible, but since I don't have extra parts to test with, and they cannot be without the PC. I might just propose a new pc acquisition, since the MSP could and would take days to give an answer, and probably can't figured it out.
 

Latest posts

Back
Top