What does BSOD 192 (PCI_CONFIG_SPACE_ACCESS_FAILURE) mean?

 
Could be also:
ConstantTypeOS
ERROR_EXE_MARKED_INVALIDWin32 errorWindows
STATUS_USER_APCNTSTATUSWindows
Previous Next
MUTEX_ALREADY_OWNED SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION

PCI_CONFIG_SPACE_ACCESS_FAILURE

PCI configuration-space access failure for PCI_CONFIG_SPACE_ACCESS_FAILURE

PCI_CONFIG_SPACE_ACCESS_FAILURE is bug check code 0x000000C0. PCI configuration space contains device identity, BARs, capabilities, interrupt configuration, and power-management fields. This bug check indicates that a kernel path could not access or validate that configuration state.

How to read it in a dump for PCI_CONFIG_SPACE_ACCESS_FAILURE

  • The affected bus, device, and function are usually found from the stack, device object, or platform firmware context.
  • Failures can involve firmware, chipset, hot-plug, power transition, virtualization, or a driver touching config space incorrectly.
  • It is not a normal PCI device-start failure unless the dump shows the PnP start path.

What to check for PCI_CONFIG_SPACE_ACCESS_FAILURE

  • Check firmware/BIOS updates, PCIe device seating, hot-plug events, virtualization pass-through, and chipset drivers.
  • Audit drivers that read or write PCI configuration space directly.
  • Correlate with WHEA PCIe events and power-management transitions.

References for PCI_CONFIG_SPACE_ACCESS_FAILURE

Dump evidence for PCI_CONFIG_SPACE_ACCESS_FAILURE

For PCI_CONFIG_SPACE_ACCESS_FAILURE, preserve the complete dump, the four bug-check parameters, the exact Windows build, loaded-module list, and the event timeline immediately before the stop. For PCI_CONFIG_SPACE_ACCESS_FAILURE, allStat summarizes the condition as “An attempt to access PCI configuration space failed.”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.

Analysis order for PCI_CONFIG_SPACE_ACCESS_FAILURE

  • Run WinDbg !analyze -v, then inspect the documented meaning of each PCI_CONFIG_SPACE_ACCESS_FAILURE parameter instead of relying only on the probably-caused-by line.
  • For PCI_CONFIG_SPACE_ACCESS_FAILURE, find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with pci / config / space / access.
  • For PCI_CONFIG_SPACE_ACCESS_FAILURE, keep third-party filter, security, storage, graphics, and virtualization drivers in the module inventory; removing evidence before dump analysis can obscure the responsible path.

Do not repeatedly reboot a machine affected by PCI_CONFIG_SPACE_ACCESS_FAILURE before collecting the dump and event logs. For PCI_CONFIG_SPACE_ACCESS_FAILURE, recovery actions should follow the component identified by the stack and parameters, not merely the symbolic stop-code name.

Dump evidence for PCI_CONFIG_SPACE_ACCESS_FAILURE

For PCI_CONFIG_SPACE_ACCESS_FAILURE, preserve the complete dump, the four bug-check parameters, the exact Windows build, loaded-module list, and the event timeline immediately before the stop. For PCI_CONFIG_SPACE_ACCESS_FAILURE, allStat summarizes the condition as “An attempt to access PCI configuration space failed.”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.

Analysis order for PCI_CONFIG_SPACE_ACCESS_FAILURE

  • Run WinDbg !analyze -v, then inspect the documented meaning of each PCI_CONFIG_SPACE_ACCESS_FAILURE parameter instead of relying only on the probably-caused-by line.
  • For PCI_CONFIG_SPACE_ACCESS_FAILURE, find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with pci / config / space / access.
  • For PCI_CONFIG_SPACE_ACCESS_FAILURE, keep third-party filter, security, storage, graphics, and virtualization drivers in the module inventory; removing evidence before dump analysis can obscure the responsible path.

Do not repeatedly reboot a machine affected by PCI_CONFIG_SPACE_ACCESS_FAILURE before collecting the dump and event logs. For PCI_CONFIG_SPACE_ACCESS_FAILURE, recovery actions should follow the component identified by the stack and parameters, not merely the symbolic stop-code name.

Looking for a different code? Search another status or error code.