Weird WHEA logger event 1

[Mazer]

I never seen any of this before till this morning when checking event viewer, the thing is I haven't had any BSOD or any restarting randomly while doing anything stressful like gaming, all of my drivers are up to date, bios is latest etc.

Not sure what to do of this error if anyone has any helpful information it would be great since I never had this happen till today my system is stock for everything no OC to the cpu I checked temperatures and nothing is off that I can see

Spoiler

Event xmlns="

http://schemas.microsoft.com/win/2004/08/events/event

">- <System> <Provider Name="Microsoft-Windows-WHEA-Logger" Guid="{c26c4f3c-3f66-4e99-8f8a-39405cfed220}" /> <EventID>1</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x8000000000000002</Keywords> <TimeCreated SystemTime="2025-04-19T15:02:37.8011521Z" /> <EventRecordID>61490</EventRecordID> <Correlation ActivityID="{2a49be4f-2ea7-4512-b0f9-f4749b2b36ec}" /> <Execution ProcessID="4392" ThreadID="13736" /> <Channel>System</Channel> <Computer>DESKTOP-UOM0RQC</Computer> <Security UserID="S-1-5-19" /> </System>- <EventData> <Data Name="Length">462</Data> <Data Name="RawData">435045521002FFFFFFFF01000100000007000000CE01000024020F00130419143C60C1835215A74887D114D9467D7765000000000000000000000000000000008D7C2157665EFB4480339B74CACEDF5B03F83300702E884E992C6F26DAF3DB7ACA1E7502BEAADB01080000000000000000000000000000000000000000000000C8000000060100000003020001000000000000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000053544F52504F525401000601A4000000010003000B0000002B0E7BD1FCE7607053075643B66679B2730074006F00720061006800630069000000000000000000000000000000000057444320202020200057443130455A45582D3038574E34413000A4000000A40000007DE050020000000016000000000100003D285C0000000000000000000000000000000000630000000000000000000000000000000000000031000000FFFFFFFF000000000000000000000000000004000100000000000000000000000000000001000000000000003100000000000000650000006400000000000000000000000000000033000000310000003100000000000000000000004A040000</Data> </EventData> </Event>

CPU: Ryzen 7 5700x
Mobo: B550m motar wifi
RAM: 32gb ram
Storage: 1TB NVMe
GPU: RTX 3080
PSU: Rmx 850w
Windows 10

 

[Bill_Bright]

the thing is I haven't had any BSOD or any restarting randomly

Then what prompted you to check Event Viewer?

Are those the only 2 instances of that error? Did you make any recent hardware changes? Updated drivers? Installed new updates after which the Event errors appeared?

It should be noted that WHEA-Logger events are generic codes that only indicate there might be a hardware or HW driver problem. This is particularly true with Event ID 1, which you have. As you can see, it does not identify any specific device. These errors often happen when rebooting or when coming out of sleep and are often considered "normal" if not causing any BSODs, reboots, or freezes, etc.

If me, since there appear to be no other symptoms, I would be inclined to do nothing - for now - but watch. Then, if I see something odd happening, quickly check Event Viewer again to see if any errors, and if so, see if have the same timestamp as the oddity I witnessed.

For more information, see Fix WHEA-Logger Fatal hardware and Event ID Errors

 

[A Computer Guy]

I never seen any of this before till this morning when checking event viewer, the thing is I haven't had any BSOD or any restarting randomly while doing anything stressful like gaming, all of my drivers are up to date, bios is latest etc.

Not sure what to do of this error if anyone has any helpful information it would be great since I never had this happen till today my system is stock for everything no OC to the cpu I checked temperatures and nothing is off that I can see

Spoiler

Event xmlns="

http://schemas.microsoft.com/win/2004/08/events/event

">- <System> <Provider Name="Microsoft-Windows-WHEA-Logger" Guid="{c26c4f3c-3f66-4e99-8f8a-39405cfed220}" /> <EventID>1</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x8000000000000002</Keywords> <TimeCreated SystemTime="2025-04-19T15:02:37.8011521Z" /> <EventRecordID>61490</EventRecordID> <Correlation ActivityID="{2a49be4f-2ea7-4512-b0f9-f4749b2b36ec}" /> <Execution ProcessID="4392" ThreadID="13736" /> <Channel>System</Channel> <Computer>DESKTOP-UOM0RQC</Computer> <Security UserID="S-1-5-19" /> </System>- <EventData> <Data Name="Length">462</Data> <Data Name="RawData">435045521002FFFFFFFF01000100000007000000CE01000024020F00130419143C60C1835215A74887D114D9467D7765000000000000000000000000000000008D7C2157665EFB4480339B74CACEDF5B03F83300702E884E992C6F26DAF3DB7ACA1E7502BEAADB01080000000000000000000000000000000000000000000000C8000000060100000003020001000000000000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000053544F52504F525401000601A4000000010003000B0000002B0E7BD1FCE7607053075643B66679B2730074006F00720061006800630069000000000000000000000000000000000057444320202020200057443130455A45582D3038574E34413000A4000000A40000007DE050020000000016000000000100003D285C0000000000000000000000000000000000630000000000000000000000000000000000000031000000FFFFFFFF000000000000000000000000000004000100000000000000000000000000000001000000000000003100000000000000650000006400000000000000000000000000000033000000310000003100000000000000000000004A040000</Data> </EventData> </Event>

View attachment 395876

View attachment 395877

CPU: Ryzen 7 5700x
Mobo: B550m motar wifi
RAM: 32gb ram
Storage: 1TB NVMe
GPU: RTX 3080
PSU: Rmx 850w
Windows 10

View attachment 395878

If you also check the application section of the log do you also have applications crashing at the same time?

 

[Mazer]

Okay so it was my drive the old WD drive, I found it out through RawData hex to ascii conversion outputs the string WD10EZEX-08WN4A0

I will need to watch it closer since I can't reproduce the error. It's random.

If you also check the application section of the log do you also have applications crashing at the same time?

No that is what is strange to me nothing crashing or causing the pc to halt unexpectedly.

Then what prompted you to check Event Viewer?

Are those the only 2 instances of that error? Did you make any recent hardware changes? Updated drivers? Installed new updates after which the Event errors appeared?

It should be noted that WHEA-Logger events are generic codes that only indicate there might be a hardware or HW driver problem. This is particularly true with Event ID 1, which you have. As you can see, it does not identify any specific device. These errors often happen when rebooting or when coming out of sleep and are often considered "normal" if not causing any BSODs, reboots, or freezes, etc.

If me, since there appear to be no other symptoms, I would be inclined to do nothing - for now - but watch. Then, if I see something odd happening, quickly check Event Viewer again to see if any errors, and if so, see if have the same timestamp as the oddity I witnessed.

For more information, see Fix WHEA-Logger Fatal hardware and Event ID Errors

I check it out once in a while out of habit. I did not make any changes recently no.

 

[Bill_Bright]

Okay so it was my drive the old WD drive, I found it out through RawData hex to ascii conversion outputs the string WD10EZEX-08WN4A0

it was my drive the old WD drive

Nice hunting!

One thing I have noticed over the years is old hard drives occasionally take just a little longer to get up to speed. The system, expecting to see the drive, doesn't immediately so tosses up that error, then checks again and the drive is there.

Could be the issue here. All I can add at this point is to make sure all power and data cables are securely fastened and you have a current backup of any data on that drive you don't want to lose.

 

[RootinTootinPootin]

Okay so it was my drive the old WD drive, I found it out through RawData hex to ascii conversion outputs the string WD10EZEX-08WN4A0

I will need to watch it closer since I can't reproduce the error. It's random.


No that is what is strange to me nothing crashing or causing the pc to halt unexpectedly.


I check it out once in a while out of habit. I did not make any changes recently no.

check the drive health and read/write stats on it, this happened to me before with my Ryzen 9 5950x + Crosshair 8 Dark Hero, it was a bad NVME drive after all that is worn out (around 88% remaining life when this specifically happened to me)

 

[eidairaman1]

Okay so it was my drive the old WD drive, I found it out through RawData hex to ascii conversion outputs the string WD10EZEX-08WN4A0

I will need to watch it closer since I can't reproduce the error. It's random.


No that is what is strange to me nothing crashing or causing the pc to halt unexpectedly.


I check it out once in a while out of habit. I did not make any changes recently no.

Make sure to turn off automatic restarts after crashing.

 

[Mazer]

check the drive health and read/write stats on it, this happened to me before with my Ryzen 9 5950x + Crosshair 8 Dark Hero, it was a bad NVME drive after all that is worn out (around 88% remaining life when this specifically happened to me)

Yeah I checked it shows all as good.

This HDD drive is old from 2017 only use it when I need to put a bunch of unimportant files somewhere then I usually move them to my back up drives.

 

[Bill_Bright]

only use it when I need to put a bunch of unimportant files somewhere

What does that mean? It is important to understand - at least with PCs - if a hard drive is installed in the PC, the drive motor is spinning when the PC is awake. The stepper motor used to move the R/W back and forth may not do anything, but the drive motor is spinning. Also, by default, hard drives are defragged once a week, if fragmentation occurred.

So, if this drive was installed, it matters little if it has been used, or not. The motor has still be spinning. Now if this is an external drive, and not powered on until needed, then little wear and tear has occurred.

 

[Mazer]

What does that mean? It is important to understand - at least with PCs - if a hard drive is installed in the PC, the drive motor is spinning when the PC is awake. The stepper motor used to move the R/W back and forth may not do anything, but the drive motor is spinning. Also, by default, hard drives are defragged once a week, if fragmentation occurred.

So, if this drive was installed, it matters little if it has been used, or not. The motor has still be spinning. Now if this is an external drive, and not powered on until needed, then little wear and tear has occurred.

I call it a scratch disk so lets say I don't have enough space on another drive I have to uninstall a huge game to make space for the new files I want to put on my backup drive. I download it on the WD HDD and move the files to SSD.

 

[Bill_Bright]

I call it a scratch disk so lets say I don't have enough space on another drive I have to uninstall a huge game to make space for the new files I want to put on my backup drive. I download it on the WD HDD and move the files to SSD.

Okay, that makes since. I actually have a "scratch" (even named "scratch") disk too. But my point remains. If it is physically connected to power in the PC, the motor used to spin the platters is running whenever the computer is awake.

So that takes me back to my comment in my post #5 above. This could simply be a matter of the old drive taking a little longer than normal to spin up to full speed when powered on. Until it happens again and you are able to do further troubleshooting about all you can do is "hurry up and wait".

 

[Mazer]

Okay, that makes since. I actually have a "scratch" (even named "scratch") disk too. But my point remains. If it is physically connected to power in the PC, the motor used to spin the platters is running whenever the computer is awake.

So that takes me back to my comment in my post #5 above. This could simply be a matter of the old drive taking a little longer than normal to spin up to full speed when powered on. Until it happens again and you are able to do further troubleshooting about all you can do is "hurry up and wait".

What about my other SSD it too had this error shown in event viewer it's a MX500 500gb with 95% health.

 

[Bill_Bright]

What about my other SSD it too had this error shown in event viewer it's a MX500 500gb with 95% health.

Not sure what to tell you. Do both drive errors have the same (or close) time stamps? Is this a recurring problem? When I see multiple, unexplained hardware issues, I always look at power. If me, and if the problem persists, I would swap in a different, known good PSU and see what happens. This is important since EVERYTHING inside the computer case depends on good, clean, stable power.

 

[Drash]

I get this randomly maybe once every few months for one maybe 2 randomly of my drives, 1 nvme 3 sata SSD and 1 HDD. Been happening for years. Put it down to old system running crappy buggy beta bios. All drives seem ok new or old. Stopped worrying years ago, but have goodish backup strategy and don't get too trusting of w10 - I live by the mantra that I keep everything such that if I have to nuke and reinstall it's no Biggie, other than my time.

 

[A Computer Guy]

I get this randomly maybe once every few months for one maybe 2 randomly of my drives, 1 nvme 3 sata SSD and 1 HDD. Been happening for years. Put it down to old system running crappy buggy beta bios. All drives seem ok new or old. Stopped worrying years ago, but have goodish backup strategy and don't get too trusting of w10 - I live by the mantra that I keep everything such that if I have to nuke and reinstall it's no Biggie, other than my time.

I had a thought. If you have a chipset heatsink make sure the back board screws are tight to ensure good contact pressure for the chipset heatsink. If your chipset overheats devices may malfunction. This happened to me on AMD's X570.

 

[Bill_Bright]

If you have a chipset heatsink make sure the back board screws are tight

Good point. To add to this, I note some motherboards don't use chipset coolers. Some that do just use mounting screws (no backplate). And some use heatsinks that are attached with adhesive TIM (thermal interface material), either adhesive paste or double sided thermal tape. Regardless, I agree it is worth checking and if loose, then you need to completely remove the heatsink, thoroughly clean the mating surfaces of old TIM, then reapply a fresh new application of TIM.

 

[Drash]

Not to steal Mazer's thread, but i will check chipset heatsink - it is a tiny looking thing, passive. It's a cheap mobo all round. Dont have a photo of back so no idea on mounting.

Not 100% but I'm leaning towards these errors occuring after wake from sleep - stuff out of sync, and the BIOS has issues - fan stuff broken, settings saying on when off having to reset to defaults to get stuff switching again, the usual Gigabyte ...

 

[Mazer]

So It happen again yesterday twice on different drives the same ones as before that being the WD HDD and the MX500 gb SSD, I was watching a video on youtube and when I did a malwarebytes scan. I checked the cables, took a look at the chipset to see if it was loose and it wasn't. Nothing from what I can tell inside my PC is loose or anything I made absolutely sure everything cable related was in and not loose. I will tested it without the HDD at his point I haven't the slightest clue what is causing it. I did install the latest AMD chipset driver since.

 

[Drash]

Weird, I've got a WD blue and 2 mx500 that give these errors. Coincidence? I don't usually believe, but way more often than me. Mobo chipset drivers up to date?

 

[Mazer]

Weird, I've got a WD blue and 2 mx500 that give these errors. Coincidence? I don't usually believe, but way more often than me. Mobo chipset drivers up to date?

Yes I did update them.