What do WHEA-Logger Event ID 17 values 0x100000 and 0xa000 mean?

Question

What do WHEA-Logger Event ID 17 values 0x100000 and 0xa000 mean?

Dalbir Rana 0

I am seeing repeated WHEA-Logger Event ID 17 warnings on a fresh Windows 11 installation. My older machine did not used to report this at all, I have also check with family friends machines they do not see this either.

The events include:

UncorrectableErrorStatus = 0x100000
CorrectableErrorStatus   = 0xa000

From the PCIe status definitions I understand these correspond to:

0x100000 = Unsupported Request
0xa000   = Advisory Non-Fatal + Header Log Overflow

My questions are:

What does this combination mean from the Windows/WHEA point of view?
Is this considered an expected/benign corrected hardware event, or does it indicate a hardware/firmware/driver problem?
Why would Windows log this as WHEA Event 17?
Why might the same type of event appear on a newer system when my previous PC did not log these warnings?
Is there any Microsoft-supported way to determine what request triggered the Event 17 entry?

The system is otherwise booting and operating normally, so I am mainly trying to understand the meaning and reliability implications of the WHEA-17 events rather than suppressing them.

0 comments

3 answers

Your answer

Answer 1

Hi. I'm David, and I'm happy to help you.

Don't worry. If your PC is running well, without freezes or blue screens, your hardware is not malfunctioning.

To see which specific part of your PC is generating these warnings, please export and share the log:

Press Windows + X and select Event Viewer;
Expand Windows Logs and select System;
In the Actions panel on the right, select Filter Current Log;
In Event level, check the boxes Critical, Warning, and Error and click on Ok;
Again, in the Actions panel, select Save Filtered Log File As and save in an easily accessible place.

Then, upload the file to the cloud (OneDrive), choose to share it, and get the link.

Post the link to the file here so I can have a look.

Looking forward to your reply.

Answer 2

Engla Wahlberg Burlin 80

If the system is stable, I would focus on BIOS/UEFI, chipset, and device firmware updates first. Corrected PCIe AER events are often associated with firmware, compatibility, or link-management behavior rather than imminent hardware failure.

I am not aware of a Microsoft-supported method that can reliably reconstruct the original PCIe transaction that triggered a specific Event 17 entry. For that level of analysis, vendor-specific diagnostic tooling is typically required rather than Windows Event Viewer.

Dalbir Rana 0 Reputation points

2026-09-30T14:08:19.26+00:00

I started investigating these WHEA-17 events because I was experiencing intermittent system freezes. Most users never look at Event Viewer unless they're troubleshooting a problem, so I only noticed them while searching for a possible cause.

The system is fully up to date, and the manufacturer has already performed several repairs related to both the reported errors and the freezing. However, the WHEA-17 warnings continue to appear.

The freezing has been difficult to diagnose because it occurred under very heavy production workloads and was intermittent. During the first two weeks of ownership I was pushing the machine to its limits and experienced several severe freezes. Since the repairs, my workload has decreased and I have not been able to reproduce the same stress conditions, so I cannot determine whether the freezing issue still exists.

My main question is whether these WHEA-17 messages are actually significant. Could they be benign or false-positive warnings, and if so, what do they mean and why are they being logged? I'm trying to understand whether they should be considered relevant to the freezing issue at all.

Answer 3

I would not ignore the WHEA-17 events. My recommendation would be to identify the PCIe device reported in the event, compare the event timestamps with the freezes, and provide those details to the manufacturer for further investigation.

Even if the system appears stable now, repeated Event 17 entries are useful diagnostic information and should be considered alongside the freezing issue rather than evaluated in isolation.

Windows can identify the reporting device, but there is no Microsoft-supported method to reliably determine the exact PCIe request that originally triggered a specific Event 17 entry.