WHEA-Logger event id 3

nobleflame · Oct 15, 2025

Hi folks,

I very occasionally get an information event in the system section of event viewer called “WHEA-Logger event Id 3”.

This is an information event and only appears on boot very rarely. My PC is running without issue or instability. All components (see my specs below) are running stock with no OC. I’m using HWINFO64 as monitoring software and it’s not showing any events under the WHEA section.

I can’t find out anything about this online from an official source. Any idea what WHEA-Logger Id3 is?

antspants · Oct 15, 2025

WHEA stands for Windows Hardware Error Architecture, a system-level mechanism for logging hardware-related issues.
Event ID 3 is a non-critical, informational event that typically appears during boot.
Unlike Event ID 1 (which signals a fatal hardware error), ID 3 often logs corrected or benign anomalies that didn’t impact system stability 9F742443-6C92-4C44-BF58-8F5A7C53B6F1.

nobleflame · Oct 15, 2025

antspants said:
WHEA stands for Windows Hardware Error Architecture, a system-level mechanism for logging hardware-related issues.
Event ID 3 is a non-critical, informational event that typically appears during boot.
Unlike Event ID 1 (which signals a fatal hardware error), ID 3 often logs corrected or benign anomalies that didn’t impact system stability 9F742443-6C92-4C44-BF58-8F5A7C53B6F1.

Thank you - that’s really useful info.

Any idea what hardware issues could be triggering this? Benign so nothing to worry about, but would be interesting to know.

I did read on the MSI forums that it can be triggering by simply entering bios.

antspants · Oct 15, 2025

Aparently:

Transient hardware initialization quirks — e.g., PCIe devices briefly misreporting status during POST.
Firmware/driver handshakes — especially with newer chipsets or UEFI updates.
Power state transitions — rare hiccups during cold boot or resume from sleep.
Telemetry or diagnostic logging — Windows may log corrected errors for internal analysis, even if they’re harmless

If it were me I wouldn’t be concernmed but if you want to go the extra mile:

Check the raw data in Event Viewer: Sometimes it includes a device GUID or error source (e.g., CPU, PCIe, memory).
Run `sfc /scannow` and `DISM /Online /Cleanup-Image /RestoreHealth`: Just to rule out any system file inconsistencies.
However I am not sure you will stop these, if they’re benign or false positives

Some things mentioned:

Check hardware health
Run diagnostics on CPU, RAM, and storage (especially if you're using NVMe or RAID). Use tools like MemTest86, CrystalDiskInfo, or Intel Processor Diagnostic Tool.

Review system event logs
Use Event Viewer to inspect the full details of the WHEA-Logger entry. Look for any device GUIDs or error sources that might indicate which component reported the event.

Update BIOS and chipset drivers
Ensure your motherboard firmware and chipset drivers are current. This can reduce spurious WHEA logs during boot.

Run system file checks
Use `sfc /scannow` and `DISM /Online /Cleanup-Image /RestoreHealth` to verify and repair system files.
Disable fast startup (optional)
Some users report fewer boot-time anomalies with fast startup disabled. You can toggle this in Control Panel > Power Options > Choose what the power buttons do.

nobleflame · Oct 15, 2025

Just found out that my Intel Management Engine driver was about a year out of date - forgot to update it after a Windows 11 reinstall.

Could this be the issue?

zbook · Mar 2, 2026

When available please update.

PerpetualCycle · Mar 3, 2026

nobleflame said:
Just found out that my Intel Management Engine driver was about a year out of date - forgot to update it after a Windows 11 reinstall.

Could this be the issue?

More likely a firmware or hardware issue but I believe not something to worry about.

nobleflame · Mar 3, 2026

Found the issue - this is caused by MSI bios. When you enter bios and make changes there is chance this event viewer log will appear. It’s harmless and not related to any hardware fault. It just shows that a hardware change has been made and can be safely ignored.

zbook · Mar 3, 2026

BIOS caused WHEA?

If there was any instability during the past 30 days then run the V2 log collector > post a share link

BSOD - Posting Instructions

BSOD - Posting Instructions This will show you how to help provide needed information about your system and dump files. It will not contain any personal or sensitive information about you or your data. To get better help with your Windows BSOD issue, please read these instructions and follow...

www.elevenforum.com

PerpetualCycle · Mar 3, 2026

zbook said:
BIOS caused WHEA?

If there was any instability during the past 30 days then run the V2 log collector > post a share link

BSOD - Posting Instructions

BSOD - Posting Instructions This will show you how to help provide needed information about your system and dump files. It will not contain any personal or sensitive information about you or your data. To get better help with your Windows BSOD issue, please read these instructions and follow...

www.elevenforum.com

Yes. I've had an informational WHEA on boots. A bios re-flash fixed it. It can happen.

nobleflame · Mar 3, 2026

zbook said:
BIOS caused WHEA?

If there was any instability during the past 30 days then run the V2 log collector > post a share link

BSOD - Posting Instructions

BSOD - Posting Instructions This will show you how to help provide needed information about your system and dump files. It will not contain any personal or sensitive information about you or your data. To get better help with your Windows BSOD issue, please read these instructions and follow...

www.elevenforum.com

No BSODs or instability. This is purely a bug in the MSI bios. Others reporting the same issue here: Reddit - The heart of the internet

It’s caused when entering bios.

zbook · Mar 3, 2026

If possible, post a V2 share link for scanning.

nobleflame · Mar 3, 2026

zbook said:
If possible, post a V2 share link for scanning.

Sorry for being dim, how do I do this? I can post it later this evening. I should add that I cleared my event viewer recently.

zbook · Mar 3, 2026

Get the latest version of the v2 log collector from the following link - V2 Log Collector.

View the menu area > click Extract All > click extract > when the box reappears > click log-collector > click enter > click run > when it completes > view the desktop > post a share link into the newest post

For share links make sure that they are available without logon or sign in.

Drop box

Google drive

GoFile.io

How to use Google Drive - Computer - Google Drive Help

Want advanced Google Workspace features for your business?

support.google.com

BSOD - Posting Instructions

BSOD - Posting Instructions This will show you how to help provide needed information about your system and dump files. It will not contain any personal or sensitive information about you or your data. To get better help with your Windows BSOD issue, please read these instructions and follow...

www.elevenforum.com

nobleflame · Mar 3, 2026

Thanks - will do later for you.

bo elam · Mar 3, 2026

nobleflame said:
I can’t find out anything about this online from an official source. Any idea what WHEA-Logger Id3 is?

Hi @nobleflame I don't know what Event id 3 is but I can tell you where the clue is. Look in the Event for the line like the one below:

Primary Device Name

CI\VEN_1E0F&DEV_001A&SUBSYS_001A1E0F&REV_01

The clue are the four digits between VEN_ and &DEV_. In the example above, the digits are 1E0F. In my case the message is related to how the SSD talks to the AMD processor. There is a fraction of a second delay during boot and it causes the Warning. The message also states that A corrected hardware error has occurred. You probably have that too. My ID is 17, a lot of HP'S have that warning. I think HP ignores the message which I think gives us user a clue also, that is meaningless and can be ignored. I only get it at boot, some people gets many. Bottom line, you only get it at boot and no noticeable issues, you can forget about it. Mine came with the computer. My computer is 6 months old and only took a look at them last week. They mean nothing.

Bo

nobleflame · Mar 3, 2026

bo elam said:
Hi @nobleflame I don't know what Event id 3 is but I can tell you where the clue is. Look in the Event for the line like the one below:

Primary Device NameCI\VEN_1E0F&DEV_001A&SUBSYS_001A1E0F&REV_01

The clue are the four digits between VEN_ and &DEV_. In the example above, the digits are 1E0F. In my case the message is related to how the SSD talks to the AMD processor. There is a fraction of a second delay during boot and it causes the Warning. The message also states that A corrected hardware error has occurred. You probably have that too. My ID is 17, a lot of HP'S have that warning. I think HP ignores the message which I think gives us user a clue also, that is meaningless and can be ignored. I only get it at boot, some people gets many. Bottom line, you only get it at boot and no noticeable issues, you can forget about it. Mine came with the computer. My computer is 6 months old and only took a look at them last week. They mean nothing.

Bo

Hey mate, thanks for this! I suspected as much. Mine only occurs when I go into bios so I am assuming this slows one particular process down on boot (say the way an ssd talks to a processor as in your eg) and it spits out an erroneous hardware fault.

It also seems to be agnostic of system (can be Intel, AMD, etc etc).

Basically, our PCs are a little bit sensitive.

I’m going to leave this thread up as a google search reference point for future people looking to troubleshoot, but I think it’s fair to say this is benign.

nobleflame · Mar 3, 2026

@zbook here's a link to the zip file GAMING-PC-2-(2026-03-03_17-23-44).zip

Thanks for your time.

zbook · Mar 3, 2026

nobleflame said:
I should add that I cleared my event viewer recently.

There were approximately twelve hours of look back time to scan.

There were no WHEA seen in that very short time period.

nobleflame · Mar 3, 2026

zbook said:
There were approximately twelve hours of look back time to scan.

There were no WHEA seen in that very short time period.

Hey, I really appreciate you taking the time to do that. Very kind. I think I’m in the clear based on others advice in this thread.

WHEA-Logger event id 3

Well-known member

My Computer My Computer

At a glance

Like a rolling drone.

My Computers My Computers

At a glance

At a glance

Well-known member

My Computer My Computer

At a glance

Like a rolling drone.

My Computers My Computers

At a glance

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Syzygy

My Computers My Computers

At a glance

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Syzygy

My Computers My Computers

At a glance

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Active member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Similar threads

My Computer

My Computers

My Computer

My Computers

My Computer

My Computer

My Computers

My Computer

My Computer

My Computers

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer