Open Device Manager, find the unknown PCI device with a yellow warning icon, open Properties > Details, and select Hardware Ids. Copy the most specific PCI\VEN_...&DEV_... value and use it to identify the vendor, device family, and correct chipset or device driver. SIW can show the same device identity, bus, status, and driver context in a broader hardware inventory.
A PCI ID normally looks like PCI\VEN_8086&DEV_XXXX&SUBSYS_YYYY&REV_ZZ. VEN identifies the vendor and DEV identifies the device; subsystem and revision fields can distinguish a board-specific implementation. USB and ACPI IDs can also appear in Device Manager, but the PCI identifier is the useful starting point for an unknown expansion or chipset device. Treat the complete identifier as an opaque driver-matching string.
PowerShell can provide a compact list of present PCI devices whose status is not OK:
Get-PnpDevice -PresentOnly |
Where-Object { $_.InstanceId -like 'PCI\*' -and $_.Status -ne 'OK' } |
Select-Object Status, Class, FriendlyName, InstanceId
If you know the PCI instance ID, the PnP device property cmdlet can request its hardware IDs:
Get-PnpDeviceProperty -InstanceId 'PCI\VEN_8086&DEV_XXXX\...' `
-KeyName 'DEVPKEY_Device_HardwareIds'
PowerShell output depends on the device class and installed modules. Use Device Manager to confirm the exact property and to install or roll back a driver.
An unknown PCI device is not automatically a failed component. Windows may have enumerated the hardware but lack a matching driver, or the firmware may expose only a generic identifier. Common causes include a missing chipset, storage-controller, card-reader, audio, network, or expansion-card driver, a recently changed PCIe card, or hardware that is disabled in firmware.