| Previous | Next |
| ERROR_INTERRUPT_VECTOR_ALREADY_CONNECTED | ERROR_WAIT_FOR_OPLOCK |
ERROR_INTERRUPT_STILL_CONNECTED
an interrupt connection remains active when teardown expected it to be gone.
ERROR_INTERRUPT_STILL_CONNECTED identifies this condition: This status reveals incomplete interrupt cleanup. A device or driver is progressing through stop, removal, unload, or reconfiguration while an interrupt object is still connected.
Where the result appears
- PnP stop and remove paths.
- driver unload.
- failed-start rollback.
- device reset or resource rebalance.
What to collect
- interrupt object and vector.
- last successful connect and disconnect call sites.
- in-flight DPC and ISR counters.
- PnP state transition and device power state.
Handling and recovery
Quiesce the device, disable interrupt generation, synchronize with the ISR, drain deferred work, and disconnect the interrupt before releasing resources. Cleanup must also execute after partial initialization failures.
Common misinterpretation
Forcing resource release while the interrupt remains connected can create use-after-free crashes. The correct fix is lifecycle ordering, not suppression of the status.
References
Looking for a different code? Search another status or error code.