• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

WHEA Logger Fatal Hardware error

Derek12 said:
I forgot to say that I am using the same Windows install as with previous MB (H110M-K-D3) and CPU (Intel i3 6100), but could that cause this event? (I work on it and formatting would be difficult) I did Uninstall old drivers
Click to expand...
It's not supposed to with Windows 10. In the old days major hardware changes would cause massive problems.

PooPipeBoy said:
Why? Source? LPX is one of the most popular RAM kits on the market and I don't hear many complaints.

That said, I do know with Corsair that they love to make sure that no two kits are identical. You can buy two kits with the same product code, one will be Samsung and the other will be Hynix modules because the version numbers are likely to be different. So it's hard to narrow down precisely which kit has incompatibility issues because they're all bloody different. That makes it great fun when you're trying to buy an additional matched kit for a future upgrade.
Click to expand...
There are certain LPX kits that have major issues with Ryzen CPUs. The older the CPU the worse it is. I have a Corsair Vengeance LPX 3200 kit(CMK16GX4M2B32000C16) that will not even POST regularly with Ryzen 1700x. With every new Ryzen revision memory support has gotten better. That kit will POST fine at defaults with my 3800X it still will not run at XMP 3200 settings. If I mess with sub-timings and bump the voltages I can get it to run at 3200. My current kit(G.Skill FlareX DDR4-3200C14 16GB(2x8)) runs out of the box with XMP on both systems.
 
PooPipeBoy said:
Huh, no way! Maybe there's some rhyme or reason to these WHEA errors after all....

Nope I haven't had even one sign of stability issues for months now. Perfectly reliable. See, one would think that if there were a serious hardware flaw that a whole multitude of different processes would be spitting out errors, but instead it's just this one jerkbutt process in Windows. But it would explain why my system posts two WHEA errors every week like clockwork. Maybe it's just a software issue and it's not a "fatal" failure at all.

I figured I'd just disable the DPS process entirely and see if that fixes the problem. That would be nice if it does lol
Click to expand...

Just a PSA that this method was a fail. Disabling DPS doesn't prevent WHEA's at all, just the reporting of them. Back to square 1 unfortunately.

I'm back to testing some voltage settings to see if that does anything to help.
 
Mess around with VDDG voltages like I did. Turning down VDDG IOD a notch completely eliminated every WHEA.
 
Alexa said:
Mess around with VDDG voltages like I did. Turning down VDDG IOD a notch completely eliminated every WHEA.
Click to expand...
I will check it and update, Last week I got another WHEA lol. This time not related to a reboot. Again no signs of instability.
Also I saw a new BIOS update so I will install it too.
Thanks!


UPDATE
I got something interesting:

I did convert that hex string to text (didn't thought about that lol)
435045521002FFFFFFFF01000100000007000000CE01000037030800180315143C60C1835215A74887D114D9467D7765000000000000000000000000000000008D7C2157665EFB4480339B74CACEDF5B03F83300702E884E992C6F26DAF3DB7ADF7A8010C41DD701080000000000000000000000000000000000000000000000C8000000060100000003020001000000000000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000053544F52504F525401000601A4000000010003000B000000B06873F5B0486387EF62D0A1B6918DD0730074006F00720061006800630069000000000000000000000000000000000057444320202020200057443230455A525A2D30305A3548423000A4000000A40000007DE050020000000016000000000100002CFC040000000000000000000000000000000000630000000000000000000000000000000000000049000000FFFFFFFF000000000000000000000000000000200100000000000000000000000000000001000000000000003100000000000000650000006400000000000000000000000000000033000000310000003100000000000000000000003E0E0000

And Got this
CPER�����7<`��R�H���F}we�|!Wf^�D�3�t���[�3p.�N�,o&���z�z����STORPORT��hs��Hc��b����storahciWDC WD20EZRZ-00Z5HB0��}�P,�cI���� 1ed311>

The highlighted text is my data HDD. Could it be the issue??? It is present on all events The drive seems to be fine per SMART. The orange text seems to pinpoint to a SATA port (?)

EDIT 2
Saw this thread
Solved: Ryzen 9 5900x whea-logger ID:1 - AMD Community
And OP's string, when decoded, also show an WD drive!!!!
 
Last edited:
I solved the WHEA errors increasing VCCIO and VCCSA but you're using AMD so i don't know anything about it.
 
VCCIO (Voltage to I/O) is quite literally Intel's version of AMD's VDDG IOD (Voltage to I/O Die). No wonder it fixed things.
 
In light of the decoded text pointing to my data drive and/or port, could this still be caused by RAM, CPU, MB? or it could be
  1. Data drive (SMART data is fine, drive doesn't show signs of failing)
  2. SATA port (I could try to change ports, again no signs of drive malfunctions)
  3. SATA cable (I could try another cable if I have some around) but I don't notice any clear symptom (I expect they to be similar to 1, 2 and maybe 3)
  4. SATA driver (I am using the generic standard AHCI driver as AMD recommends)
  5. SATA controller, aka motherboard, but all events point to the same drive.
  6. Some Windows bug or something?

I will try 2, 3, and maybe 4 and see if it repeats, and updating UEFI.
 
Last edited:
Derek12 said:
I will check it and update, Last week I got another WHEA lol. This time not related to a reboot. Again no signs of instability.
Also I saw a new BIOS update so I will install it too.
Thanks!


UPDATE
I got something interesting:

I did convert that hex string to text (didn't thought about that lol)
435045521002FFFFFFFF01000100000007000000CE01000037030800180315143C60C1835215A74887D114D9467D7765000000000000000000000000000000008D7C2157665EFB4480339B74CACEDF5B03F83300702E884E992C6F26DAF3DB7ADF7A8010C41DD701080000000000000000000000000000000000000000000000C8000000060100000003020001000000000000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000053544F52504F525401000601A4000000010003000B000000B06873F5B0486387EF62D0A1B6918DD0730074006F00720061006800630069000000000000000000000000000000000057444320202020200057443230455A525A2D30305A3548423000A4000000A40000007DE050020000000016000000000100002CFC040000000000000000000000000000000000630000000000000000000000000000000000000049000000FFFFFFFF000000000000000000000000000000200100000000000000000000000000000001000000000000003100000000000000650000006400000000000000000000000000000033000000310000003100000000000000000000003E0E0000

And Got this
CPER�����7<`��R�H���F}we�|!Wf^�D�3�t���[�3p.�N�,o&���z�z����STORPORT��hs��Hc��b����storahciWDC WD20EZRZ-00Z5HB0��}�P,�cI���� 1ed311>

The highlighted text is my data HDD. Could it be the issue??? It is present on all events The drive seems to be fine per SMART. The orange text seems to pinpoint to a SATA port (?)

EDIT 2
Saw this thread
Solved: Ryzen 9 5900x whea-logger ID:1 - AMD Community
And OP's string, when decoded, also show an WD drive!!!!
Click to expand...

It's funny you mention a Western Digital hard drive....

1617006788311.png
 
Derek12 said:
WTF!!

Could it be some compatibility issue with Ryzen and some WD drives???
Click to expand...

It might be!

I looked at the other errors and I got some from the other WD drive as well. So I guess that means I'm getting two WHEA errors per week because I've got two WD drives?

Madness o_O

1617007364280.png
 
Last edited:
Are these uncorrectable (BSOD) or correctable (event viewer) WHEAs? If they're the latter, and the hard drive theory is to be believed, then I wouldn't worry about them. Seems like just another bug or incompatibility. Might get ironed out in a future AGESA update, who knows. Could be worth reporting this to AMD.
 
Alexa said:
Are these uncorrectable (BSOD) or correctable (event viewer) WHEAs? If they're the latter, and the hard drive theory is to be believed, then I wouldn't worry about them. Seems like just another bug or incompatibility. Might get ironed out in a future AGESA update, who knows. Could be worth reporting this to AMD.
Click to expand...

Yeah they're not BSODs, they're WHEA errors posted without any instability or hard resets. It would seem like there's some kind of scheduled maintenance process that happens every five days or so on the drives and that's what is causing the issues. Some kind of file indexing thing or something? Not sure.

Our storage be playin' mind games with us, fellas.

Edit: One of the things I've noticed with these WHEA errors is that they don't specifically mention anything about the processor cores reporting the error. Just very generic information: "A fatal hardware error has occured". That's all, nothing mentioned about processor cores reporting the error like you get with a serious WHEA that crashes the computer.

1617008053311.png
 
I turned off file indexing as I just use Everything to search for files. Then again, my system is all SSDs. Didn't bother checking the logs like you guys to see what exactly caused it. Thankfully just lowering VDDG IOD solved my issues.
 
Alexa said:
I turned off file indexing as I just use Everything to search for files. Then again, my system is all SSDs. Didn't bother checking the logs like you guys to see what exactly caused it. Thankfully just lowering VDDG IOD solved my issues.
Click to expand...

Next time I get a WHEA posted I'll need to check the events that happen around that time. I haven't cross-checked with the Application events at all, which I have a suspicion might provide some more information. I've looked at other events in the System section and haven't noticed anything odd.
 
PooPipeBoy said:
Yeah they're not BSODs, they're WHEA errors posted without any instability or hard resets. It would seem like there's some kind of scheduled maintenance process that happens every five days or so on the drives and that's what is causing the issues. Some kind of file indexing thing or something? Not sure.

Our storage be playin' mind games with us, fellas.

Edit: One of the things I've noticed with these WHEA errors is that they don't specifically mention anything about the processor cores reporting the error. Just very generic information: "A fatal hardware error has occured". That's all, nothing mentioned about processor cores reporting the error like you get with a serious WHEA that crashes the computer.

View attachment 194302
Click to expand...
Yeah, exactly the same here too
Alexa said:
I turned off file indexing as I just use Everything to search for files. Then again, my system is all SSDs. Didn't bother checking the logs like you guys to see what exactly caused it. Thankfully just lowering VDDG IOD solved my issues.
Click to expand...
I will try the BIOS voltage and also updating UEFI, and wait another couple of weeks
PooPipeBoy said:
Next time I get a WHEA posted I'll need to check the events that happen around that time. I haven't cross-checked with the Application events at all, which I have a suspicion might provide some more information. I've looked at other events in the System section and haven't noticed anything odd.
Click to expand...
Same here, there is no pattern, some happen right after a boot/reboot, and sometimes they happen while idling or something, for example, this is the last of the events in system events and application events:

1617020521273.png

1617020599756.png
 
it could be the drives are asked to report something and fail to do so, they could be waking too slow from a sleep state - but this is interesting and someone needs to poke AMD and WD
 
Mussels said:
it could be the drives are asked to report something and fail to do so, they could be waking too slow from a sleep state - but this is interesting and someone needs to poke AMD and WD
Click to expand...

It's devilishly hard to report bugs to manufacturers, but I sent off information to both AMD and WD. I can't post to the AMD Community forum although I did send off a service request to customer support. Even if it takes a while to get resolved at least it's not a major issue and we don't need to worry about it.
 
I am very sure this is just bug with the Ryzen bios and as long you don't get regular crashes or other issues not really a cause for concern.
 
Came here to say I also have a whea event id 1 reported by dps and I did the same thing you guys did with that hex code and the problem was my WD40EZRZ-00GXCB0 hdd and I am on a z490 aorus elite ac and 10900 so this definitely is not an amd only problem.
 
So yesterday I got another whea event id 1 and this time the hex code when converted to text revealed the problem might be the storport driver.
 
Hello, my computer just locked 10 min ago. I found the issue was WHEA error. I checked hex and my problem was WD10EZEX-22MFCA0 hdd. I use win 10 20H2 with latest updates all drivers.
 
Last edited:
Would like to report this very same issue as well. Running a Ryzen 5 3600 and B550 Asrock PG Velocita board. I've only gotten 3 of these WHEA errors, but they all mention my WD Blue HDD (WDC WD10EZEX-00RKKA0). HWInfo, however, isn't showing any actual errors with the drive, nor imminent failures.

This is bizarre :kookoo:
 
I am really glad i dont have any WD drives, has anyone heard back from AMD or WD yet?
 
You must log in or register to reply here.
Back
Top