WHEA Logger Fatal Hardware error

[FireFox]

I've only gotten 3 of these WHEA errors, but they all mention my WD Blue HDD (WDC WD10EZEX-00RKKA0).

Where/how do you find the info that it shows it's your HDD?

 

[Gmr_Chick]

Where/how do you find the info that it shows it's your HDD?

By translating the raw data numbers hex into text.

435045521002FFFFFFFF01000100000007000000CE01000024090600190515143C60C1835215A74887D114D9467D7765000000000000000000000000000000008D7C2157665EFB4480339B74CACEDF5B03F83300702E884E992C6F26DAF3DB7A53721E69854CD701080000000000000000000000000000000000000000000000C8000000060100000003020001000000000000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000053544F52504F525401000601A4000000010003000B00000060D20B4AFF861736C778947F0DAD08EA730074006F00720061006800630069000000000000000000000000000000000057444320202020200057443130455A45582D3030524B4B413000A4000000A40000007DE05002000000001600000000010000D74A000000000000000000000000000000000000630000000000000000000000000000000000000031000000FFFFFFFF0000000000000000000000000000000101000000000000000000000000000000010000000000000031000000000000006500000064000000000000000000000000000000330000003100000031000000000000000000000028060000

In that mess of numbers, when converted to plain text, my WD drive is mentioned.

 

[FireFox]

In that mess of numbers, when converted to plain text, my WD drive is mentioned.

And i don't know how to do that

 

[Gmr_Chick]

Oh, neither do I, but I googled "hex to text converter" and found out that way

 

[FireFox]

Will give it a try, got a WHEA error yesterday.

 

[pajic]

Wow, I am so glad I stumbled upon this forum thread. I've been getting WHEA events since June and was infuriated because I didn't know what the problem is. Such a relief to find out it's the hard drive (by converting the raw hex data to a string) and not something more vital... but, there is nothing wrong with my hard drive whatsoever, I use it every day. I assume this is a bug of some sort? I saw that some people fixed it with a BIOS update but the latest BIOS for my mobo is still in Beta so I don't wanna bother. I replaced the SATA cable for the hard drive from a regular one to a one with a clip just to be safe.

Here's the string I got by converting the raw hex data if someone is interested, and big thanks to OP for figuring this out.

Spoiler

CPERÿÿÿÿÎ,<`ÁƒR§H‡ÑÙF}we|!Wf^ûD€3›tÊÎß[ø3p.ˆN™,o&ÚóÛz=d<à‚×ÈSTORPORT¤ôõÈž¡(¹óßPqߘstorahciWDC WD10EZEX-08WN4A0¤¤}àP¶žc2ÿÿÿÿ1ed311“

 

[Boombastik]

As-rock z97 anniversary + a pcie sata controller with Marvell 9120 chipset (installed at the first pcie slot).
I take whea error only if i put an old western digital hard drive WD1600BEVT-22A23 in the 9120 sata-esata controller.
The only difference is that 9120 has external sata capable(from hwinfo64 details)

 

[SpazShark]

Hi all - first post here....I signed up just to contribute to this conversation.

I'm seeing the exact same thing (WHEA Logger Fatal Hardware error - Event ID 1).

Interestingly my raw data translates to this:

CPER�����1,<`��R�H���F}we�|!Wf^�D�3�t���[�3p.�N�,o&���z��i���STORPORT��O:�~'��v�CstorahciSamsung SSD 860 EVO 1TB��}�Pr[dc����cedecc�

So in my case my Samsung 860 EVO SSD (my D: drive) is identified as the culprit. This is a new build < 2 weeks old so I've only seen this error come up once.

My C: drive is actually a Western Digital NVME drive (WDS100T1X0E) and it hasn't reported this error yet.

Is anyone seeing this error with non-WD drives? Is it always a drive plugged in via SATA? Is it always a secondary drive and not the drive Windows is installed in (C: drive)?

 

[Hachi_Roku256563]

Hi all - first post here....I signed up just to contribute to this conversation.

I'm seeing the exact same thing (WHEA Logger Fatal Hardware error - Event ID 1).

Interestingly my raw data translates to this:

CPER�����1,<`��R�H���F}we�|!Wf^�D�3�t���[�3p.�N�,o&���z��i���STORPORT��O:�~'��v�CstorahciSamsung SSD 860 EVO 1TB��}�Pr[dc����cedecc�

So in my case my Samsung 860 EVO SSD (my D: drive) is identified as the culprit. This is a new build < 2 weeks old so I've only seen this error come up once.

My C: drive is actually a Western Digital NVME drive (WDS100T1X0E) and it hasn't reported this error yet.

Is anyone seeing this error with non-WD drives? Is it always a drive plugged in via SATA? Is it always a secondary drive and not the drive Windows is installed in (C: drive)?

My system is almost all wd so i only have one other drive a segate
and it does not do this

 

[Logan7]

Interesting that this came up again, I just posted about this in another thread a few days ago.

I had this issue on an older system recently, the hex to text converter showed my Samsung 860 EVO SSD as the culprit. I had no real problems, except that this error would show up once per week or so and I'd BSOD maybe once a month. It ended up being an incompatibility between the ~2010 AMD chipset and the SSD. To solve it I had to turn off Native Command Queuing (NCQ).

If this is your issue you'll see a "CRC Error Count" in SMART data above 0, even though it shows it as being Good or Healthy. If you run something like CrystalDiskMark, that error count will probably go up - mine went up by 95 in one run. I'm now sitting at an error count of 10,481 and it hasn't increased since I disabled NCQ months ago. Note that if you're disabling NCQ, the process differs depending on if you have the generic Windows 10 driver or if you have the manufacturer (AMD/Intel) driver.

Not sure if it will help anyone in this thread or if its even applicable outside of SSDs, but check your CRC error counts.

 

[SpazShark]

Interesting that this came up again, I just posted about this in another thread a few days ago.

I had this issue on an older system recently, the hex to text converter showed my Samsung 860 EVO SSD as the culprit. I had no real problems, except that this error would show up once per week or so and I'd BSOD maybe once a month. It ended up being an incompatibility between the ~2010 AMD chipset and the SSD. To solve it I had to turn off Native Command Queuing (NCQ).

If this is your issue you'll see a "CRC Error Count" in SMART data above 0, even though it shows it as being Good or Healthy. If you run something like CrystalDiskMark, that error count will probably go up - mine went up by 95 in one run. I'm now sitting at an error count of 10,481 and it hasn't increased since I disabled NCQ months ago. Note that if you're disabling NCQ, the process differs depending on if you have the generic Windows 10 driver or if you have the manufacturer (AMD/Intel) driver.

Not sure if it will help anyone in this thread or if its even applicable outside of SSDs, but check your CRC error counts.

@Logan7 thanks for the info! Does my screenshot of my Samsung SSD 860 EVA look similar to what you saw in the "CRC Error count" section? If so do you recommend that I disable NCQ?

 

[Logan7]

@Logan7 thanks for the info! Does my screenshot of my Samsung SSD 860 EVA look similar to what you saw in the "CRC Error count" section? If so do you recommend that I disable NCQ?

View attachment 211660

Yours looks to be fine in that regard actually, since its showing all 0s under "Raw Values" so I don't know that disabling NCQ would do anything
This is what mine looks like in Speccy

(28F1 in a hexadecimal to decimal converter shows 10,481)

 

[SpazShark]

Yours looks to be fine in that regard actually, since its showing all 0s under "Raw Values" so I don't know that disabling NCQ would do anything
This is what mine looks like in Speccy

View attachment 211684

(28F1 in a hexadecimal to decimal converter shows 10,481)

Ok thanks for the explanation! I guess I'll leave it for now and see....

 

[Boombastik]

I have also an old p5q with q6600.
That pc has 2 DVD, one seagate hdd, two western digital hdd and one ssd.
I see that whea errors for the two wd hard drives one a week.
The wd are green hard drives from 2010 era.

 

[Lukiez22]

Hi, i got the same WHEA error but with an I7 - 4700MQ and a ssd Samsung SSD 860 EVO 1TB. if i convert the hex i got this.
For me, i don't get a blue screen, my monitor just start glitching a lot, with different colours, (like old tv when they had low signal), after this i can't move the mouse or do anything for like a minute and then crash. I must restart like 3/4 time before i can re-use the pc. (Sometime, after the restart my pc can't even boot cause it can't find the boot file)

 

[not_a_stable_genius]

Are they being reported by a local service like mine are?

You should be able to look at the WHEA event details and find a Process ID. Then go into Details tab of Task Manager and find the active process that reported the error. Note that if you restart the computer, all the process IDs will be different and you won't be able to find it.

It's not much to go by (mine are reported by svchost.exe) but it helps gather a bit more information at least.

EDIT: I just learned that if you right-click a process in the Details tab, you can click "Go To Service(s)" and it will take you to the actual service running in the Services tab. It looks like my WHEAs were reported by "Diagnostic Policy Service". Interesting.

Thanks for the advice. I have this problems too with a ryzen 7 5700u in a convertible device. I think this machine has some kind of power state problem since this error displays shortly upon a restart or startup of the system. It was the DPS process in my case too, i figured I just kill that permanently and fight the symptoms instead of the root problem. This issue is very rare in my case as well and very hard to reproduce because it doesn't happen on every startup. I give it a few more days and if it continues to annoy me I'll have to make use of the warranty... I already tested the system stringently, cinebench, long multi tasking sessions, a bootable ram testing program which fills the ram and checks the integrity, windows storage diagnostics, and SMART logs of the SSD. I didn't find any hardware errors with my tests so far and when it runs and doesn't bsod after startup it runs very stable and fine. I already updated the bios the the newest version and updated all ryzen and chipset drivers to their respective newest versions.

 

[J_45]

Has anyone had a conclusive resolve to this.

I have exactly the same issue. Hex Converter mentions a WD Blue drive each time on the WHEA error (I have 3 of the same drives in my system though, so Im just at the stage of testing one at a time).

I too am running a Ryzen 3000 X470 build, system is completely stable. Errors appear every 3 or 4 days, most of the time when the system is idle. Since monitoring it over the last month I've noticed a lot of times the error comes up around the 36 hour mark.

 

[AlwaysHope]

Has anyone had a conclusive resolve to this.

I have exactly the same issue. Hex Converter mentions a WD Blue drive each time on the WHEA error (I have 3 of the same drives in my system though, so Im just at the stage of testing one at a time).

I too am running a Ryzen 3000 X470 build, system is completely stable. Errors appear every 3 or 4 days, most of the time when the system is idle. Since monitoring it over the last month I've noticed a lot of times the error comes up around the 36 hour mark.

I'd like to know this too. Have WHEA errors only when I'm gaming, not when benching at the same clocks. Very weird! Might try downgrade PCIe 4 to 3 & see if that still happens with my gpu.

 

[AlwaysHope]

This is not exactly a fatal hardware error but nonetheless it's a WHEA error logged by the system. After some digging in my system, I discovered the device causing this. Funny thing is it's not consistent when producing errors whilst gaming.

 

[buyukbang]

This is not exactly a fatal hardware error but nonetheless it's a WHEA error logged by the system. After some digging in my system, I discovered the device causing this. Funny thing is it's not consistent when producing errors whilst gaming.
View attachment 231639

I've exactly same error alongside the "WHEA Logger Fatal Hardware error". Can you share how did you found root cause? I tried to find a which device is connected with the mentioned (in my error log) the PCIE Root port but couldnt find a way.

 

[GerKNG]

the other happened while the computer was idle ( I think I was away RDPing it but I don't remember quite well).

As you said I didn't get any stability issues, the computer is rock solid.***

Disable Power Down mode in the Memory settings and set the PSU Idle Control from low current idle to typical current idle. (normally found within the overclocking settings either in or near of AMD CBS)

in 8/10 cases that's the problem.

 

[AlwaysHope]

I've exactly same error alongside the "WHEA Logger Fatal Hardware error". Can you share how did you found root cause? I tried to find a which device is connected with the mentioned (in my error log) the PCIE Root port but couldnt find a way.

I got the device hardware ID & systematically went through all the devices listed in device manager to marry up the names together & then WHAM! you find them. It's tedious work but if your determined you can track it down. Funny thing is though, I'm not on that motherboard anymore & since I changed to another Z590 board, so far at least with gaming I have no WHEA errors.

 

[buyukbang]

I got the device hardware ID & systematically went through all the devices listed in device manager to marry up the names together & then WHAM! you find them. It's tedious work but if your determined you can track it down. Funny thing is though, I'm not on that motherboard anymore & since I changed to another Z590 board, so far at least with gaming I have no WHEA errors.

Thank you very much for the hint. After reading your comment I noticed there is an option to see it easier Device Manager --> View --> Resourced By Connection. I found that the PCI E Root Port that I'm getting error logs is connected to a SATA AHCI Controller. So it seems as a Sata controller or HDD issue as most of the people here already reported.

 

[AlwaysHope]

Another way with device manager is too right click the device > properties > details > property > scroll down to hardware ID. Like a lot with computers there is always more than 2 ways to skin a cat.

 

[favtony]

I recently got a lot WHEA ID 1 error. Every time a suddenly reboot.
I searched a lot, and find out Microsoft has an example program called "dumprec" for dumping the WHEA data from event log. But can't find anywhere to download, so I built one.
Then I found it's output can be cross validated from my whea dmp, which may indicate that it's the memory doing all this.
sources of Microsoft's sample program

just run it in a cmd, here's the Output from my computer. Be aware that the "Primary" means the section that is used for error recovery. Don's know if it's the reason, but I think that's a hint.

============================================================
2022/4/23 8:54:17 - Machine Check Exception
Fatal (Previous Error)
------------------------------------------------------------
0 - Memory Error Section (Primary)
1 - Processor Generic Error Section
Processor type: x86/x64
Instruction set: x64
Error type: BUS
Operation: Generic
Flags:
Level: 1
CPU Version: 0x0000000000a20f10
Processor ID: 0x6
2 - XPF MCA Section
CPU Vendor: AMD
Processor Number: 0x6
MCG_STATUS: 0x0000000000000000 ()
Instruction Ptr: 0x0000000000000000
MCA Bank: 0x1
MCi_STATUS: 0xbaa00000060e0809 (VAL UC EN MISCV PCC)
Other info: 0x0200000
Model error: 0x060e
MCA error: 0000 1000 0000 1001 (binary)
Misc: 0xd01a0ffe00000000
3 - {c34832a1-02c3-4c52-a9f1-9f1d5d7723fc}

I attached my build program. Don't know what will look like when analyzing other types of error, but hope it helps.