Question Help with WHEA Logger Error Event ID 17

[Lucasff]

So, i keep getting this error in windos log, today when i couldnt turn on the pc because cpu red light was on, i just restart the computer and it turn on just fine, besides that i cant see any error, blue screen or something, should i worry? or some one could point where the erro is? Specs, and error log below.

Z690 Aorus Elite AX DDR4
i5 12600k
RTX 2060 Super
2x8 xpg memory 3200mhz
XPG Core reactor 750w

-

System

- Provider [ Name] Microsoft-Windows-WHEA-Logger [ Guid] {c26c4f3c-3f66-4e99-8f8a-39405cfed220}

EventID 17

Version 1

Level 3

Task 0

Opcode 0

Keywords 0x8000000000000000

- TimeCreated [ SystemTime] 2022-05-29T13:58:16.6306403Z

EventRecordID 4034

- Correlation [ ActivityID] {6ce104d4-5a3c-4e10-9eb9-60d6cb835442}

- Execution [ ProcessID] 5028 [ ThreadID] 1408

Channel System

Computer DESKTOP-E26A47M

- Security [ UserID] S-1-5-19

-

EventData

ErrorSource

4

FRUId

{00000000-0000-0000-0000-000000000000}

FRUText

ValidBits

0xdf

PortType

4

Version

0x101

Command

0x10

Status

0x407

Bus

0x0

Device

0x1c

Function

0x2

Segment

0x0

SecondaryBus

0x0

SecondaryDevice

0x0

SecondaryFunction

0x0

VendorID

0x8086

DeviceID

0x7aba

ClassCode

0x30400

DeviceSerialNumber

0x0

BridgeControl

0x0

BridgeStatus

0x0

UncorrectableErrorStatus

0x0

CorrectableErrorStatus

0x1

HeaderLog

00000000000000000000000000000000

PrimaryDeviceName

PCI\VEN_8086&DEV_7ABA&SUBSYS_50011458&REV_11

SecondaryDeviceName

 

[johnbl]

log is for a intel device but the device ID 7aba is not listed
in the vendor lookup.
PCI\VEN_8086 - Intel Corporation | Device Hunt
you might go to control panel device manager and look for drivers that are not installed.

guess would be a device for the alder lake chipset.
maybe get the driver from Intel® Driver & Support Assistant
(this would update the driver if the reported error was just a driver bug)

#note: the error might be due to a bios setting relating to sleep states. (s3 or s4) you might check for a bios update.
I think microsoft got more aggressive on using deeper sleep states and problems are showing up.

 

[Lucasff]

log is for a intel device but the device ID 7aba is not listed
in the vendor lookup.
PCI\VEN_8086 - Intel Corporation | Device Hunt
you might go to control panel device manager and look for drivers that are not installed.

guess would be a device for the alder lake chipset.
maybe get the driver from Intel® Driver & Support Assistant
(this would update the driver if the reported error was just a driver bug)

So its not a hardware issue? I thought it was a mb problem or cpu lol
EDIT: It says all drivers are up to date :https://ibb.co/wWVk37m

 

[johnbl]

So its not a hardware issue? I thought it was a mb problem or cpu lol
EDIT: It says all drivers are up to date :https://ibb.co/wWVk37m

it is hard to say without knowing what the actual device that reported the problem was. My wife's 7 year old dell laptop reported a similar error and i could never get it to not report the error. In my case it was some mouse pad built into the laptop that was the source. never did get a fix and it would generate a lot of these logs (sometimes 3 each minute)
never did find anything that seemed to be wrong. In my case they were correctable errors that happened since the day we got the laptop.

in your case you might update the bios if it related to sleep functions and you really want to get rid of the log entry. Microsoft windows update increased the low power states to sleep in a deeper sleep state to save more power. Lots of people have devices that do not handle these correctly. Most will require bios updates of the machine or firmware updates some vendors provide driver updates but really are just disable the lower sleep states rather than fix the problem.

it would still be a hardware error like a checksum error during communication between devices but one that the system was able to correct. you might be able to find out what intel device ID= 7aba refers to by looking at all of the entries in window control panel device manager,
that are for intel devices.
note: when I query microsoft update catalog for 7aba
I do get a list of updates for intel other hardware devices:
(does not tell me what the device is, just the update file)

here is my query:
Microsoft Update Catalog

when I look at the docs for the catalog
device 7aba= Intel(R) PCI Express Root Port #4

now you would need to find go to device manager and find out what is connected to port 4

I guess you could just try the update catalog from that matches your windows version. download the catalog, uncompress it to your hard drive, then find the entry in device manager, right mouse click to update the driver then tell it to pick the driver you downloaded rather than search for a driver and see if your error goes away with the update. otherwise you have to find out what is on that port and update its firmware or the bios and hope there was a fix related to your log entry.

 

[Lucasff]

log is for a intel device but the device ID 7aba is not listed
in the vendor lookup.
PCI\VEN_8086 - Intel Corporation | Device Hunt
you might go to control panel device manager and look for drivers that are not installed.

guess would be a device for the alder lake chipset.
maybe get the driver from Intel® Driver & Support Assistant
(this would update the driver if the reported error was just a driver bug)

#note: the error might be due to a bios setting relating to sleep states. (s3 or s4) you might check for a bios update.
I think microsoft got more aggressive on using deeper sleep states and problems are showing up.

it is hard to say without knowing what the actual device that reported the problem was. My wife's 7 year old dell laptop reported a similar error and i could never get it to not report the error. In my case it was some mouse pad built into the laptop that was the source. never did get a fix and it would generate a lot of these logs (sometimes 3 each minute)
never did find anything that seemed to be wrong. In my case they were correctable errors that happened since the day we got the laptop.

in your case you might update the bios if it related to sleep functions and you really want to get rid of the log entry. Microsoft windows update increased the low power states to sleep in a deeper sleep state to save more power. Lots of people have devices that do not handle these correctly. Most will require bios updates of the machine or firmware updates some vendors provide driver updates but really are just disable the lower sleep states rather than fix the problem.

it would still be a hardware error like a checksum error during communication between devices but one that the system was able to correct. you might be able to find out what intel device ID= 7aba refers to by looking at all of the entries in window control panel device manager,
that are for intel devices.
note: when I query microsoft update catalog for 7aba
I do get a list of updates for intel other hardware devices:
(does not tell me what the device is, just the update file)

here is my query:
Microsoft Update Catalog

when I look at the docs for the catalog
device 7aba= Intel(R) PCI Express Root Port #4

now you would need to find go to device manager and find out what is connected to port 4

I guess you could just try the update catalog from that matches your windows version. download the catalog, uncompress it to your hard drive, then find the entry in device manager, right mouse click to update the driver then tell it to pick the driver you downloaded rather than search for a driver and see if your error goes away with the update. otherwise you have to find out what is on that port and update its firmware or the bios and hope there was a fix related to your log entry.

im not sure if i understood what to do. i took a screen of device manager, but there is no Intel(R) PCI Express Root Port #4 https://ibb.co/q9tBjSc

 

[johnbl]

im not sure if i understood what to do. i took a screen of device manager, but there is no Intel(R) PCI Express Root Port #4 https://ibb.co/q9tBjSc

it is there but it says port #3 look for the 7aba which looks like the device id.

I would first go into bios and change any setting then change it back and save the results and reboot into windows. This will force the bios to rebuild the hardware database and send a new copy to windows.
(or update the bios if you have not)

debuggers and the user interface might number things differently (some things the first entry is 0 and for others the first entry is 1)