These WHEA-Logger errors seem quite concerning.
These WHEA-Logger errors seem quite concerning.
Hi, I'm just writing this to know if I should worry or not about these so that I can remedy before it's too late. The premise: I just upgraded to a new GPU, a 5070, and out of the box even with all the other specs compatible, my entire system would just freeze forcing me to shutdown. This would consistently happen regardless of stress after about 20 minutes. After I upgraded my BIOS these freezes went away but a friend who was helping me with this pointed out to me to check into the evets logger to see if there was any info i could use to diagnose. Sure enough there were a LOT of WHEA-Logger events with Event ID 17. Before the BIOS update these were constant, and with constant I do mean spammed multiple every second for quite a while. After the BIOS update they dropped significantly, occurring like once or twice a day. I have no idea if any occurred before the GPU swap because the registry is setup to overwrite old events when full. I had a 3060 TI before and it ran PERFECT. Zero crashes. I even applied some undervolting to it and it ran veery smooth. So should i worry and ask for an RMA or is it more a problem of the chipset? SAMPLE EXTENDED ERROR LOG: Log Name: System Source: Microsoft-Windows-WHEA-Logger Date: 01/28/2026 00:09:38 Event ID: 17 Task Category: None Level: Warning Keywords: User: LOCAL SERVICE Computer: DESKTOP-****** (it's not censored in the log) Description: A hardware error occurred and was corrected. Component: PCI Express Root Port Error source: Advanced Error Reporting (PCI Express) Primary bus: Device: Function: 0x0:0x1:0x0 Secondary bus: Device: Function: 0x0:0x0:0x0 Primary device name: PCI\VEN_8086&DEV_460D&SUBSYS_86941043&REV_02 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="2026-01-27T23:09:38.8424136Z" /> <EventRecordID>2496837</EventRecordID> <Correlation ActivityID="{80de800e-daed-4452-b849-fcb869ee7aab}" /> <Execution ProcessID="6156" ThreadID="26092" /> <Channel>System</Channel> <Computer>DESKTOP-*******</Computer> (it's not censored in the log) <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">0x407</Data> <Data Name="Bus">0x0</Data> <Data Name="Device">0x1</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">0x8086</Data> <Data Name="DeviceID">0x460d</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="PrimaryDeviceName">PCI\VEN_8086&DEV_460D&SUBSYS_86941043&REV_02</Data> <Data Name="SecondaryDeviceName"> </Data> </EventData> </Event>
Here are the additional details about your system. I’d boot into safe mode just to confirm, and if these occurrences persist in the logs, it could indicate stability once the freezing issue resolves—log entries don’t always signal a problem.
The driver was added following a DDU setup in safe mode. The system includes an ASUS B660-PLUS D4 motherboard, Intel i5 12600k processor, single tower CPU cooler, 1x120mm RGB fan, two 16GB Corsair Vengeance cards at 3200MT/s, one 512GB NVMe drive, one 1TB Crucial SATA SSD, and two HDDs.
Also, how do you include your specs in your message like they are here? It would help if you could do that so I don’t have to type them out each time. Thanks!
Review the settings and go to signature. You can separate sections using |. I’d reinsert all PCI connectors just in case there are any loose ones causing the problem. A fresh GeForce game driver was released yesterday—make sure to update it too. Let me know if you run into more issues.
I just noticed two events happening one after another within under a minute when my PC woke from idle. The process ID 6156, identified as svchost.exe, appears in the logs. This information might be useful.
svchost is merely a common Windows service. Did you encounter any issues or freezing?
Just issues popping up now and being fixed, but what if they stop getting corrected later? They could freeze again. Thanks for the hardware details—from the log entry you shared, it looks like the device is an Intel Alder Lake-S with a PCI Express 5.0 port. I’ve switched to a new chipset driver just in case it reappears tomorrow.