WHEA-Logger Event "A corrected hardware error has occurred" Event ID 17

anuraggoswami
anuraggoswami Member Posts: 1 New User
edited November 2023 in 2020 Archives

Hi

I'm having a hard time solving this issue even after looking for the issue on multiple websites.

My laptop is unable to go to sleep and draining my battery all along every time i put it into sleep mode. This wasn't the case before.
After few weeks of uninstalling multiple apps to solve the problem. i just checked the event logger in the system and found out "WHEA-Logger Event "A corrected hardware error has occurred" appearing multiple times in the list. its like this

A corrected hardware error has occurred.

Component: PCI Express Root Port Error Source: Advanced Error Reporting (PCI Express)

Primary Bus:Device:Function: 0x0:0x1C:0x4

Secondary Bus:Device:Function: 0x0:0x0:0x0

Primary Device Name:PCI VEN_8086&DEV_ 9DBC&SUBSYS_129A1025&REV_F0
Secondary Device Name:

So i thought the issue was with some pci express device and tried to update all the drivers which were available like chipset, graphics etc. Everything has been updated and also the multiple windows updates have come since this problem started but nothing has been able to resolve it. I have looked at many different websites but nothing seems to work

PFA the screenshots. THIS same error appears multiple times within a minute and this is what i believe causing the Laptop to not go to sleep when asked to.


image

My Laptop

OS Name Microsoft Windows 10 Home Single Language

Version                    10.0.18363 Build 18363

Other OS Description Not Available

OS Manufacturer       Microsoft Corporation

System Name               ANURAG-SWIFT3

System Manufacturer Acer

System Model                Swift SF314-55G

System Type                x64-based PC

System SKU               0000000000000000

Processor              Intel(R) Core(TM) i5-8265U CPU @ 1.60GHz, 1800 Mhz, 4 Core(s), 8 Logical Processor(s)

BIOS Version/Date      American Megatrends Inc. V1.07, 24-12-2018

SMBIOS Version      3.1

Embedded Controller   Version 1.08

BIOS Mode              UEFI

Installed Physical Memory (RAM) 8.00 GB

Total Physical Memory 7.85 GB


IRQ 109 Microsoft ACPI-Compliant System
IRQ 109 I2C HID Device
I/O Port 0x00000070-0x00000070 Motherboard resources
I/O Port 0x00000070-0x00000070 System CMOS/real time clock
Memory Address 0x80000000-0xDFFFFFFF PCI Express Root Complex
Memory Address 0x80000000-0xDFFFFFFF Intel(R) UHD Graphics 620
Memory Address 0x90000000-0xA1FFFFFF Intel(R) PCI Express Root Port #5 - 9DBC
Memory Address 0x90000000-0xA1FFFFFF NVIDIA GeForce MX250
Memory Address 0xA3000000-0xA40FFFFF Intel(R) PCI Express Root Port #5 - 9DBC
Memory Address 0xA3000000-0xA40FFFFF NVIDIA GeForce MX250
Memory Address 0xA4200000-0xA42FFFFF Intel(R) PCI Express Root Port #9 - 9DB0
Memory Address 0xA4200000-0xA42FFFFF Standard NVM Express Controller

Answers

  • Hndx009
    Hndx009 Member Posts: 1 New User
    Hello, I have a similar with my Acer swift 3 55G. It shuts off unexpectedly at times. I looked at the Event viewer and saw that i had the same error coming every second. After a lot of searching, and ultimately reinstalling windows without success, i came across a forum where someone had a similar problem, and basically a response was about isolating the faulty driver. To do that, go to:
    Device Manager --> System devices --> Click on "Intel PCI Express Root Port #5" (The problem device) once.
    Then click on the "View" Panel --> Select "Device by connection"
    When you do that you will see the devices connected to the port. In my case it was the Nvidia MX150 GPU. From that i identified it as the culprit. The device was at the latest version. I tried to roll it back to the version available on the Acer website, unfortunately that didn't solved my problem (My computer shutting off randomly) but there was a reduction in the "WHEA" messages. The radical solution i found for stopping these message was to disable the GPU driver. I don't need it on all the time, and if i need to play a game i can enable it manually. That at least seemed to have stopped the message, i have none since 5-6 hours now. For you i don't know, try to disable it or update/roll back driver to see if it helps. Good luck, hope you solve your problem.