Windows 11 64bit receiving repeatedly the Event 17 WHEA-Logger in System event logs

[DLCazes]

Windows 11 Pro receiving repeatedly Event 17 WHEA-Logger in System event logs:  

A corrected hardware error has occurred.
Component: PCI Express Endpoint
Error Source: Advanced Error Reporting (PCI Express)
Primary Bus:Device:Function: 0x3:0x0:0x0
Secondary Bus:Device:Function: 0x0:0x0:0x0
Primary Device Name:PCI\VEN_10EC&DEV_C822&SUBSYS_85F7103C&REV_00
Secondary Device Name:
I ran a Windows 7 backup but it hung at 97% and still receiving the above errors.
My system hardware is an HP ENVY TE01-1xxx:
Device name DLCA-PC
Processor Intel(R) Core(TM) i7-10700F CPU @ 2.90GHz 2.90 GHz
Installed RAM 32.0 GB (31.9 GB usable)
Device ID 680F5AD0-0E70-46AE-B55F-C2D6AFC981E0
Product ID 00330-80000-00000-AA897
System type 64-bit operating system, x64-based processor
HP Diag Fast Test ran with no errors.
SFC and DISM has no issues.

Also ran HP Hardware Diagnostic Windows 2.6.4.0 Fast Test (passed).  Continued to run Device checks (components) and all passed with drivers being up to date.  This error started occuring after successfully installing Windows 11 24H2.  

[A_Gayathri]

Hi @DLCazes,

Welcome to The HP Support Community.  

Thank you for posting your query, I will be glad to help you.

I understand you are getting the Event 17 WHEA-Logger error you're encountering indicates a corrected hardware error related to the PCI Express Endpoint. Specifically, the error source is Advanced Error Reporting (AER) for the PCI Express device, which typically refers to communication issues between your system's processor and connected PCIe devices (like graphics cards, network cards, or storage controllers).

Given that this error started after the Windows 11 24H2 update and you've already performed diagnostics with no detected hardware issues, there are a few potential causes and troubleshooting steps to consider:

1. PCIe Device Driver Issues

• Update Drivers: Even though your drivers are up-to-date, it’s worth ensuring that the specific PCIe device (with the ID PCI\VEN_10EC&DEV_C822&SUBSYS_85F7103C&REV_00) has the latest drivers. The device ID seems to correspond to a Realtek PCIe network or audio controller, depending on your system configuration.
• Reinstall Drivers: Uninstall the device driver via Device Manager, then reinstall it from the Hp website or the device’s driver package. 
• Check Device Manager for Errors: Look for any warnings or errors related to the PCIe device or other hardware components in the Device Manager.

2. BIOS Update

• Check for BIOS Updates: Since the issue started after the Windows 11 24H2 update, it may be related to the BIOS. Ensure that your BIOS is updated to the latest version available from HP's support page for your HP ENVY TE01-1177c.
• Reset BIOS Settings: Sometimes, after a major Windows update, BIOS settings can become incompatible. Resetting the BIOS to its default settings can resolve such issues.

3. Power Management Settings

• PCIe Link State Power Management: In Windows, there are power management settings that can affect the PCIe bus, which may be causing the error. To check this:
  1. Open Device Manager.
  2. Right-click the PCI Express Root Port under System Devices.
  3. Select Properties > Power Management tab.
  4. Uncheck Allow the computer to turn off this device to save power if it’s checked.
• You can also adjust power settings via Control Panel > Power Options > Change Plan Settings > Change advanced power settings. Look for the PCI Express option and set Link State Power Management to Off.

4. Hardware Compatibility Issues Post-Update

• Since the issue began after installing Windows 11 24H2, it's possible that there could be a compatibility issue between this update and your hardware, specifically with how PCIe devices are handled. You could try rolling back to the previous version of Windows 11 if the issue persists.
  1. Settings > System > Recovery > Go back to previous version.

5. Event Viewer Analysis

• You may want to look deeper into the Event Viewer logs to gather more information about the specific time and circumstances of these errors. Check for any related warnings or critical events before or after the Event 17 error to identify a possible cause.

I hope this helps. 

Take care and have a good day.

Please click “Accepted Solution” if you feel my post solved your issue, it will help others find the solution. Click the “Kudos/Thumbs Up" on the bottom right to say “Thanks” for helping!