Share via

WHEA-Logger Event 17 - PCI Express Root Port

Anonymous
2023-02-08T11:45:44+00:00

Hi, I am trying to find out what is causing the WHEA-Logger error below and it's consistently on Port 7A3B but I am unable to identify what it is connected to. It various from being fairly frequent to occasionally frequent.

My specs:

13900k

Z790 Asus Maximus Extreme

2x16GB Team Group Teamforce RGB 7600Mhz RAM

MSI RTX 4090 Supreme X

1 x Samsung 980 Pro 1tb

1 x Samsung 980 Pro 2tb

1 x Sansdisk 4TB SSD

Any help on finding out what device is using PCI Express Root Port #4 would be really helpful. Thanks,

Windows for home | Windows 11 | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

6 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-03-10T10:19:18+00:00

    In response to my previous post about this problem below:

    WHEA-Logger Event 17 - PCI Express Root Port - Microsoft Community

    I think I have the solution, and it has to do with PCI-E Native Power Management in the BIOS (for Asus Z790 motherboards). The problem goes away if you turn it off, but I don't want to turn it off.

    If you want it on without coming up with these errors:

    Set your NVIDIA GPU in the NVIDIA control panel (if it's PCI-E 4.0 or higher, like the 30 or 40 series) to prefer maximum performance.

    Change your power plan in Windows 11 to high performance.

    It seems that the Windows 11 power plan of balanced mode doesn't work correctly with recent high-performance hardware like the ROG Maximus Z790 series and NVIDIA GPUs using PCI-E 4.0 or higher.

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments
  2. Anonymous
    2023-02-09T03:02:17+00:00

    Hi

    Welcome to Microsoft community.

    I'm glad to help you.

    From your error report, it is more likely that your error report is caused by not having all the drivers installed. At present, I can't find the specific cause in your screenshot. But you can first install all your motherboard drivers (go to the official website of the motherboard to download and install all motherboard drivers, including chip drivers, etc.)

    If anything is unclear, please do not hesitate to let me know.

    Best regards

    Derrick Qian | Microsoft Community Support Specialist

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  3. Anonymous
    2023-02-10T15:59:13+00:00

    There is a thread about this on the ASUS site. It might be something to do with the Z790 boards or processor, but there is a power setting that can stop them, but it will reset after certain operations.

    You can check what is on the port in the Device Manager by selecting it then changing the view settings in Device by connection. On my system it is a SATA controller, but disabling or even moving that had no effect. Right now, I have disabled the port to stop those multiple errors. My board does not have a second Bios.

    New Z790 Hero Constant WHEA warnings (asus.com)

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. VARADHARAJAN K 9,686 Reputation points Volunteer Moderator
    2023-02-10T17:36:36+00:00

    Install the latest intel chipset driver version 10.1.19199.8340

    Install the latest intel Serial IO driver version 30.100.2221.20 from below asus official site.

    Install the latest Intel Management Engine Interface V2240.3.4.0

    ROG Maximus Z790 Extreme | Motherboards | ROG India (asus.com)

    Was this answer helpful?

    0 comments
  5. Anonymous
    2023-02-10T13:53:20+00:00

    Hi thanks for the reply, I found out it was related to the Asus motherboard BIOS and ME Update tool. I had switched to a different BIOS, as my motherboard has dual BIOS and I didn't update the above on that one. So far so good but I'll keep you updated if anything pops up again.

    Was this answer helpful?

    0 comments