Windows 10: WHEA-Logger EventID 17 Repeating Error

Discus and support WHEA-Logger EventID 17 Repeating Error in Windows 10 BSOD Crashes and Debugging to solve the problem; Hello all, I am currently getting an error in Event Viewer that is occurring 15x every second (just about). Here is the following error: Code: Log... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by TechGuru, May 23, 2019.

  1. TechGuru Win User

    WHEA-Logger EventID 17 Repeating Error


    Hello all,

    I am currently getting an error in Event Viewer that is occurring 15x every second (just about). Here is the following error:

    Code: Log Name: System Source: Microsoft-Windows-WHEA-Logger Date: 5/23/2019 4:04:10 PM Event ID: 17 Task Category: None Level: Warning Keywords: User: LOCAL SERVICE Computer: QUINTON-ROG Description: A corrected hardware error has occurred. Component: PCI Express Root Port Error Source: Advanced Error Reporting (PCI Express) BusWHEA-Logger EventID 17 Repeating Error :Device:Function: 0x0:0x1C:0x6 Vendor IDWHEA-Logger EventID 17 Repeating Error :Device ID: 0x8086:0xA116 Class Code: 0x30400 The details view of this entry contains further information. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-WHEA-Logger" Guid="{c26c4f3c-3f66-4e99-8f8a-39405cfed220}" /> <EventID>17</EventID> <Version>0</Version> <Level>3</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x8000000000000000</Keywords> <TimeCreated SystemTime="2019-05-23T23:04:10.905677000Z" /> <EventRecordID>347159976</EventRecordID> <Correlation ActivityID="{676c9ccc-988d-4438-b999-faf75ce49744}" /> <Execution ProcessID="3996" ThreadID="7072" /> <Channel>System</Channel> <Computer>QUINTON-ROG</Computer> <Security UserID="S-1-5-19" /> </System> <EventData> <Data Name="ErrorSource">4</Data> <Data Name="FRUId">{00000000-0000-0000-0000-000000000000}</Data> <Data Name="FRUText"> </Data> <Data Name="ValidBits">0xdf</Data> <Data Name="PortType">4</Data> <Data Name="Version">0x101</Data> <Data Name="Command">0x10</Data> <Data Name="Status">0x406</Data> <Data Name="Bus">0x0</Data> <Data Name="Device">0x1c</Data> <Data Name="Function">0x6</Data> <Data Name="Segment">0x0</Data> <Data Name="SecondaryBus">0x0</Data> <Data Name="Slot">0x0</Data> <Data Name="VendorID">0x8086</Data> <Data Name="DeviceID">0xa116</Data> <Data Name="ClassCode">0x30400</Data> <Data Name="DeviceSerialNumber">0x0</Data> <Data Name="BridgeControl">0x0</Data> <Data Name="BridgeStatus">0x0</Data> <Data Name="UncorrectableErrorStatus">0x0</Data> <Data Name="CorrectableErrorStatus">0x1</Data> <Data Name="HeaderLog">00000000000000000000000000000000</Data> <Data Name="Length">672</Data> <Data Name="RawData">435045521002FFFFFFFF02000200000002000000A00200000A041700170513140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB571311FC093CF161AFC4DB8BC9C4DAF67C10485B09E40B511D50100000000000000000000000000000000000000000000000010010000D0000000000300000100000054E995D9C1BB0F43AD91B44DCB3C6F3500000000000000000000000000000000020000000000000000000000000000000000000000000000E0010000C00000000003000000000000ADCC7698B447DB4BB65E16F193C4F3DB00000000000000000000000000000000030000000000000000000000000000000000000000000000DF0000000000000004000000010100001000060400000000868016A1000403061C00000000000000000000000000000000000000108042010180000007001100134C72074000127000B2540000004001080000000000000037080000000400000000000000000000000000000000000001000114000000000000000011000600010000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000043010000000000000002000000000000E306050000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000</Data> </EventData> </Event>[/quote] ------------------------------------------------------------
    I found the device the error is related to, and after installing some drivers and such from my manufacturer's website (chipset drivers), I found the following event item related to device A116:

    Code: Log Name: Microsoft-Windows-Kernel-PnP/Configuration Source: Microsoft-Windows-Kernel-PnP Date: 5/23/2019 3:14:11 PM Event ID: 411 Task Category: None Level: Error Keywords: User: SYSTEM Computer: QUINTON-ROG Description: Device PCI\VEN_8086&DEV_A116&SUBSYS_86941043&REV_F1\3&11583659&0&E6 had a problem starting. Driver Name: oem90.inf Class Guid: {4d36e97d-e325-11ce-bfc1-08002be10318} Service: pci Lower Filters: Upper Filters: Problem: 0x15 Problem Status: 0x0 Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Kernel-PnP" Guid="{9c205a39-1250-487d-abd7-e831c6290539}" /> <EventID>411</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x4000000000000000</Keywords> <TimeCreated SystemTime="2019-05-23T22:14:11.532056500Z" /> <EventRecordID>1634</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="10964" /> <Channel>Microsoft-Windows-Kernel-PnP/Configuration</Channel> <Computer>QUINTON-ROG</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="DeviceInstanceId">PCI\VEN_8086&amp;DEV_A116&amp;SUBSYS_86941043&amp;REV_F1\3&amp;11583659&amp;0&amp;E6</Data> <Data Name="DriverName">oem90.inf</Data> <Data Name="ClassGuid">{4d36e97d-e325-11ce-bfc1-08002be10318}</Data> <Data Name="ServiceName">pci</Data> <Data Name="LowerFilters"> </Data> <Data Name="UpperFilters"> </Data> <Data Name="Problem">0x15</Data> <Data Name="Status">0x0</Data> </EventData> </Event>[/quote] It seems the device is called "Intel(R) 100 Series/C230 Series Chipset Family PCI Express Root Port #7 - A116"

    Is there any way to fix this issue? I've been playing for a couple hours to try and fix it, to no avail. Thank you.

    :)
     
    TechGuru, May 23, 2019
    #1

  2. WHEA-Logger | Event ID 17 Issue

    Lots of people with HP laptops latest 2017 releases have the same error WHEA logger event id 17 and I have that too.....

    The WHEA logger error causes freezing whole laptop creating an error in event viewer

    Tried some settings in advance power settings

    Changing "Maximum Power savings" to "off" in PCI Express ----> LInk Power state management this fixed the error for a while but now i have spotted the error in every latest laptop that has Nvidia Geforce 940 mx graphic card

    my laptop is

    HP Pavilion x360 14-ba073tx and the same error was also repeated with my friends

    Hp Pavilion 15-cc102tx

    Can you help me ASAP

    And also please explain in detail how to disable "WHEA logger error" as you done above

    Thanks in advance
     
    VENKATA RAJUPUTRA, May 23, 2019
    #2
  3. PCR Just PCR, May 23, 2019
    #3
  4. Asaf108 Win User

    WHEA-Logger EventID 17 Repeating Error

    WHEA-Logger id 17 and Blue Screen

    Hi

    On June 10 my Yoga 910 installed the Microsoft 1803 update.

    From that moment on I've been having system crashes in the form of a system freeze and blue screen with NO description whatsoever (unlike the usual BSOD full of the error's description in white letters).

    The event viewer shows a FLOOD of "Microsoft-Windows-WHEA-Logger" with event id 17, in relation to the PCI Express Root Port.

    In addition there are a few more repetitive events but they are not in the hundreds and hundreds like the WHEA-Logger.

    Laptop model is Lenovo Yoga 910-13IKB glass.

    Here's what I've done so far:

    1. Updated bios to latest version 2JCN39WW

    2. Updated lenovo usb3 lan driver

    3. Updated intel online connect

    still the problem repeats.

    I will update a couple more things soon: the usb_c _dock_firmware and the Lenovo System Interface Foundation software.

    However I am posting this thread in case someone already got a solution and also being sceptic as to the success of these updates.

    thanks

    Asaf
     
    Asaf108, May 23, 2019
    #4
Thema:

WHEA-Logger EventID 17 Repeating Error

Loading...
  1. WHEA-Logger EventID 17 Repeating Error - Similar Threads - WHEA Logger EventID

  2. whea logger event 17 fixed

    in Windows 10 Drivers and Hardware
    whea logger event 17 fixed: I had this problem with literally thousands of warnings per hour clogging up the log. After reading other discussion I gleaned that the device id in the error message is the key. in my case it was 8086 9D13,the 8086 means it is intel. I looked in device manager and...
  3. Internal Parity Whea Logger 19

    in Windows 10 Drivers and Hardware
    Internal Parity Whea Logger 19: Hello. Today i was checking for no reason event logs and find, WHEA-LOGGER 19 Internal Parity warnings, My pc: 9900K 5G OC PROFILE 2x16GB DDR4 3000MHZ GSKILL Asus Prime Z390-A Corsair 850RmX Pc is rock stable. But that warnings can pop out of the blue. Also get this...
  4. Internal Parity Whea Logger 19

    in Windows 10 Drivers and Hardware
    Internal Parity Whea Logger 19: Hello. Today i was checking for no reason event logs and find, WHEA-LOGGER 19 Internal Parity warnings, My pc: 9900K 5G OC PROFILE 2x16GB DDR4 3000MHZ GSKILL Asus Prime Z390-A Corsair 850RmX Pc is rock stable. But that warnings can pop out of the blue. Also get this...
  5. WHEA-Logger event ID 17, Windows 10

    in Windows 10 BSOD Crashes and Debugging
    WHEA-Logger event ID 17, Windows 10: i'm using "ASUS Vivobook 15 X542UN" Laptop.And in event viewer. i can see that there is as warning showing me which is WHEA-Loger Event ID 17. and i need proper and absolute solution about that warning.please resolve my problem as soon as you can.and confirm me if i need to...
  6. WHEA-Logger warning

    in Windows 10 Drivers and Hardware
    WHEA-Logger warning: WHEA-Logger warning constantly How to fix https://answers.microsoft.com/en-us/windows/forum/all/whea-logger-warning/cb9bbf23-5515-42ed-b463-d44e0f9ef77f
  7. WHEA Logger entries 8700K

    in Windows 10 BSOD Crashes and Debugging
    WHEA Logger entries 8700K: Hello. I was checking event logs on 25.10.2018 and had spam of WHEA-LOGGER 19 entries. They happened when system was idling from 23.10 - 25.10 , so nothing happening in system only spam. Is this reason to worry? My actually Windows 10 is 1803. Ah and i remember i had them...
  8. WHEA Logger entries 8700K

    in Windows 10 BSOD Crashes and Debugging
    WHEA Logger entries 8700K: Hello. I was checking event logs on 25.10.2018 and had spam of WHEA-LOGGER 19 entries. They happened when system was idling from 23.10 - 25.10 , so nothing happening in system only spam. Is this reason to worry? My actually Windows 10 is 1803. Ah and i remember i had them...
  9. WHEA-Logger Event ID 17 flooding System Events

    in Windows 10 BSOD Crashes and Debugging
    WHEA-Logger Event ID 17 flooding System Events: Hello, For you guys it's probably the same old story. For me is something completely new, even though I'm using computers since about 21 years ago. Can someone identify this particular WHEA problem? I just bought an ASUS Ultrabook (Ultrabook ASUS 14'' VivoBook S14 S406UA,...
  10. Whea-logger event 19

    in Windows 10 Drivers and Hardware
    Whea-logger event 19: I am getting these warnings in the event viewer for about 1 day started at 3:00 at night, now seems that these errors have stopped when I updated Windows 10 to newest version 16299.214. Look at the photo, apcid,errortype [img] Why I am get those warnings in 21...