| Previous | Next |
| STATUS_FT_ORPHANING | STATUS_PARTITION_FAILURE |
STATUS_BIOS_FAILED_TO_CONNECT_INTERRUPT
The platform could not establish the device's interrupt resource
STATUS_BIOS_FAILED_TO_CONNECT_INTERRUPT concerns platform interrupt routing for a device or bus. Modern Windows Plug and Play drivers receive assigned hardware resources, including interrupt resources, during device start. Firmware descriptions can also define interrupt resources and their trigger, polarity and sharing attributes. A failure in this path is more specific than a device simply returning an I/O error after it has started.
Preserve both raw and translated resource information. The PnP manager assigns resources and drivers consume the interrupt descriptors supplied for the device. On ACPI systems, the firmware namespace and resource descriptors are part of the platform contract. A mismatch in routing data, sharing rules or firmware tables can prevent the interrupt from being connected before ordinary device traffic begins.
What to inspect
- The device instance, parent bus and the raw/translated interrupt descriptors delivered at start.
- Interrupt type, vector/message assignment, trigger mode, polarity and sharing disposition.
- Current BIOS/UEFI revision and ACPI resource descriptions for the device and its resource producer.
- Whether the failure began after a firmware update, docking/topology change or device enumeration change.
Changing an application setting cannot repair a broken platform resource assignment. Diagnose the firmware/PnP resource path before debugging the device protocol handled above it.
References
- Microsoft: Using interrupt resource descriptors
- Microsoft WDK: CM_PARTIAL_RESOURCE_DESCRIPTOR
- UEFI Forum: ACPI device configuration and resources
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.