Question Thousands of "Event ID 17, WHEA-Logger" warnings in Event Viewer ?

[ashala2202]

I registered that behaviour after larger Cummulative updates, the ones that require you to restart and I meant "Windows Update" as a service, no a particular one.

The updates installed that last time were KB5041580 and KB5042352.

At the moment I'm not getting any WHEAs after the driver reinstall and I've cleared the log prior, but I posted earlier about it and gave the event ID and lots of other stuff.

Reliability Monitor states a certain HD-Player.exe to have stopped working that could be connected to the behaviour. It's supposedly a part of Bluestacks emulator I use from time to time.

Anyway, I'll keep an eye out for any signs again and see what happens.

 

[ashala2202]

An update

It's been a few days now since that last update and I haven't gotten a single WHEA warning and the PC has been reliable and as fast as it can be. I've been using it just the same as ever. No weird behaviour whatsoever, let alone crashes or failing to boot. Really, really interesting.

The only conclusion I can draw is that either something that updated in that last large update did the trick or the GPU driver fixed it 'cause it looks like it was a more recent version than the one I had before.

It's been a really unpleasant experience altogether, so I'll keep a lookout for some time now.

 

[ashala2202]

As a round-up and for eventual future reference: after an extended period of using the computer, doing research and paying attention to processes, I came to a conclusion that the WHEA-Loggers on my PC were somehow related to me using the Bluestacks Android emulator which triggered the errors that had an impact on other things in the aftermath.

I still get my usual HDD disk errors from time to time as I have been for years prior to WHEAs, so I think it's safe to say that it was not about the faulty HDD after all.

 

[ubuysa]

Well done for isolating BlueStacks as the probable cause. That doesn't surprise me TBH.

I'm concerned that you talk about 'normal' HDD errors. Would you share the logs for these?

 

[ashala2202]

Here goes:

The device, \Device\Harddisk0\DR0, has a bad block.

Log Name: System
Source: disk
Date: 27.11.2024. 8:05:54
Event ID: 7
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP-PR08HBO
Description:
The device, \Device\Harddisk0\DR0, has a bad block.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="disk" />
<EventID Qualifiers="49156">7</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2024-11-27T07:05:54.9207861Z" />
<EventRecordID>1017731</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="7280" />
<Channel>System</Channel>
<Computer>DESKTOP-PR08HBO</Computer>
<Security />
</System>
<EventData>
<Data>\Device\Harddisk0\DR0</Data>
<Binary>030080000100000000000000070004C0000100009C0000C00000000000000000001C7BC60000000061663B0100000000FFFFFFFF00000000580000840200000000200A1240032000000000004100000000BC7F440C80FFFFF8C9CA4D0C80FFFF00000000000000001040F04F0C80FFFF1040AB4A0C80FFFF8E3D630000000000280000633D8E00000100000000000000F00003000000000B00000000000000000000000000000000</Binary>
</EventData>
</Event>

 

[ubuysa]

If you keep getting these bad block errors then do the following - AFTER you have backed-up all user data on the volume.

If it's an HDD then run a chkdsk /f /r /x on each volume on the disk. If any errors are found and not repaired then replace the drive ASAP.

If it's an SSD then either run a chkdsk /f /x and check for unrepaired errors, or better still, look for a diagnostic tool from the vendor of the SSD and use that to test the drive. If either show unrepaired errors then replace the drive ASAP.