-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
- HP Community
- Desktops
- Desktop Hardware and Upgrade Questions
- Warning WHEA-logger event 17 recorded in event viewer about ...

Create an account on the HP Community to personalize your profile and ask a question
01-17-2020 12:24 PM
I have no idea where to post this but Microsoft tech says this is a hardware problem with the motherboard. I don't know when it started because the event viewer is full and so new events are now replacing old events. I noticed it yesterday. I turned this new computer on for the first time on January 10. My computer updated and I now have Windows 10 v1909 on HP ENVY TE01-0014 and I am getting a flood of warnings from WHEA-logger.
Log Name: System
Source: Microsoft-Windows-WHEA-Logger
Date: 1/15/2020 7:28:30 PM
Event ID: 17
Task Category: None
Level: Warning
Keywords:
User: LOCAL SERVICE
Computer: DESKTOP-8I8PM5O
Description:
A corrected hardware error has occurred.
Component: PCI Express Endpoint
Error Source: Advanced Error Reporting (PCI Express)
Primary Bus:Device:Function: 0x2:0x0:0x0
Secondary Bus:Device:Function: 0x0:0x0:0x0
Primary Device Name:PCI\VEN_10EC&DEV_C822&SUBSYS_85F7103C&REV_00
Secondary Device Name:
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>1</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2020-01-16T01:28:30.099145500Z" />
<EventRecordID>5405</EventRecordID>
<Correlation ActivityID="{352d279b-e513-466e-a94d-84aba1a03b43}" />
<Execution ProcessID="4240" ThreadID="1924" />
<Channel>System</Channel>
<Computer>DESKTOP-8I8PM5O</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">0</Data>
<Data Name="Version">0x101</Data>
<Data Name="Command">0x10</Data>
<Data Name="Status">0x407</Data>
<Data Name="Bus">0x2</Data>
<Data Name="Device">0x0</Data>
<Data Name="Function">0x0</Data>
<Data Name="Segment">0x0</Data>
<Data Name="SecondaryBus">0x0</Data>
<Data Name="SecondaryDevice">0x0</Data>
<Data Name="SecondaryFunction">0x0</Data>
<Data Name="VendorID">0x10ec</Data>
<Data Name="DeviceID">0xc822</Data>
<Data Name="ClassCode">0x18000</Data>
<Data Name="DeviceSerialNumber">0xe04cfffec82201</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="PrimaryDeviceName">PCI\VEN_10EC&DEV_C822&SUBSYS_85F7103C&REV_00</Data>
<Data Name="SecondaryDeviceName">
</Data>
</EventData>
</Event>
01-17-2020 01:43 PM - edited 01-17-2020 01:47 PM
Issue 1)Reset to out of the box condition by Microsoft Support Technition. Computer has new name, Desktop-FL7840A. Nothing else changed. Microsoft-Windows-WHEA-Logger continues to fire off Warnings at the rate of hundreds per hour. He did not think this would help but I wanted to try. Hardware issue persists. I guess motherboad is broken. Need help. Computer is only one week old. I did register it Friday, January 10, but website said it would be 2-3 weeks before confirmation.
Issue 2)Microsoft technition is continuing to try to help me install HP ENVY 5540 series all-in-one printer/scanner on Windows 10 and it is not going well.
01-18-2020 04:37 AM
Hello
are there any problems with wifi?
Primary Device Name: PCI \ VEN_10EC & DEV_C822
this seems to correspond to the wifi card
Anyway, if the pc is guaranteed better contact the seller, or HP directly to have the pc repaired!
was this reply helpful , or just say thank you ? Click on the yes button
Please remember to mark the answers this can help other users
Desktop-Knowledge-Base
Windows 11 22h2 inside , user
------------------------------------------------------------------------------------------------------------
01-18-2020 05:58 AM
Thanks for the reply.
HP technical support recommended taking it back rather than repair. I squeaked under the 15 day return limit by 2 hours and Best Buy will replace it. I will pick up new computer January 29.
Meanwhile I have my trusty Pavilion from 2012 with Windows 7. BTW this computer was a replacement back in 2012. The original had hardware problems back then also.
01-18-2020 08:19 AM
ok, @mpw101 so please mark the answer here:
https://h30434.www3.hp.com/t5/Desktop-Hardware-and-Upgrade-Questions/Warning-WHEA-logger-event-17-re...
was this reply helpful , or just say thank you ? Click on the yes button
Please remember to mark the answers this can help other users
Desktop-Knowledge-Base
Windows 11 22h2 inside , user
------------------------------------------------------------------------------------------------------------
02-25-2020 01:31 PM
HP Pavilion Desktop - TP01-0050
Product number 6YQ50AA#ABA
This is my second computer with the same problem.
My previous computer (HP ENVY TE01-0014) flooded the system log with thousands of warnings from the WHEA-logger. I was advised to take it back because this was a hardware problem. I did so and now have another computer, HP Pavilion Desktop - TP01-0050 P/N 6YQ50AA#ABA.
I recently checked the Event Viewer on the replacement computer that I have now. I was upset to find this new computer is also logging the same event from the WHEA-logger.
I really don’t know what to do. It is a warning and it is not flooding the system log, but something is wrong and this is the second brand new computer with the same problem.
It was not there when I first turned on the new computer on January 28, 2020. It appears to have started on January 31st, which is when the HP Support Assistant installed two driver packages.
1) Realtek RTL8xxxSeries Wireless LAN Drivers for Microsoft Windows 10 (DCHU)
SoftPaq number: sp100552 Version: 2024.0.10.209 Size 12.91MB
2)And a Bluetooth Audio Driver which is now greyed out and a pop up says it is no longer available. (There was also a Bluetooth error until I just turned Bluetooth off.)
WHEA-logger has logged this event 112 times since January 31, 2020 when the packages were installed.
Log Name: System
Source: Microsoft-Windows-WHEA-Logger
Date: 2/25/2020 12:50:08 PM
Event ID: 17
Task Category: None
Level: Warning
Keywords:
User: LOCAL SERVICE
Computer: PC-Win10
Description:
A corrected hardware error has occurred.
Component: PCI Express Endpoint
Error Source: Advanced Error Reporting (PCI Express)
Primary Bus:Device:Function: 0x1:0x0:0x0
Secondary Bus:Device:Function: 0x0:0x0:0x0
Primary Device Name:PCI\VEN_10EC&DEV_8168&SUBSYS_8653103C&REV_16
Secondary Device Name:
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>1</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2020-02-25T18:50:08.715604400Z" />
<EventRecordID>9739</EventRecordID>
<Correlation ActivityID="{d6f454b6-af20-479c-8f96-c25aa38442bb}" />
<Execution ProcessID="4584" ThreadID="8840" />
<Channel>System</Channel>
<Computer>PC-Win10</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">0</Data>
<Data Name="Version">0x101</Data>
<Data Name="Command">0x10</Data>
<Data Name="Status">0x507</Data>
<Data Name="Bus">0x1</Data>
<Data Name="Device">0x0</Data>
<Data Name="Function">0x0</Data>
<Data Name="Segment">0x0</Data>
<Data Name="SecondaryBus">0x0</Data>
<Data Name="SecondaryDevice">0x0</Data>
<Data Name="SecondaryFunction">0x0</Data>
<Data Name="VendorID">0x10ec</Data>
<Data Name="DeviceID">0x8168</Data>
<Data Name="ClassCode">0x10000</Data>
<Data Name="DeviceSerialNumber">0x1000000684ce000</Data>
<Data Name="BridgeControl">0x0</Data>
<Data Name="BridgeStatus">0x0</Data>
<Data Name="UncorrectableErrorStatus">0x0</Data>
<Data Name="CorrectableErrorStatus">0x0</Data>
<Data Name="HeaderLog">00000000000000000000000000000000</Data>
<Data Name="PrimaryDeviceName">PCI\VEN_10EC&DEV_8168&SUBSYS_8653103C&REV_16</Data>
<Data Name="SecondaryDeviceName">
</Data>
</EventData>
</Event>
I don't know how to get rid of the driver that HP Support Assistant installed on January 31 and started all this.
02-25-2020 01:55 PM
Update
I just checked Device Manager:
Driver Provider: Realtek Semiconductor Corp.
Driver Date: 12/4/2019
Driver Version: 2014.0.10.209 (this is the same version that HPSA installed 1/31/2020)
And according to Device Manager this driver was installed 1/28/2020 7:28:24 PM which is when I turned this computer on for the first time. I do not know why the error did not start until January 31 after the update from HP Support Assistant which just tried to install the driver I already had on the computer.
02-26-2020 09:24 AM
I have been googling many different key words. No real solution but I am discovering that not all posts end in “take it back” (too late for me) or contact HP for a repair.
There is some indication that the problem arises from a Windows 10 update or an HP update for BIOS or drive.
I am on Windows 10 v1909 and all the drives present when I turned the computer on 1/28/2020. This includes Windows January 2020 updates. I have no where to go back to and restore a previous version. And anyway, whatever this is it has been going on for years across other manufactuers in addition to HP.
WHEA event 17 is a warning and it is not getting worse and it is no where near as frequent as the first computer I had. It is only happening 8-10 times a day as opposed to 450 an hour on the first computer I had when I started this thread.
My computer is working fine so I have decided to wait and see.