| Previous | Next |
| STATUS_FSFILTER_OP_COMPLETED_SUCCESSFULLY | STATUS_INTERRUPT_STILL_CONNECTED |
STATUS_INTERRUPT_VECTOR_ALREADY_CONNECTED
The interrupt was registered twice
A physical-device driver registers its ISR after PnP assigns an interrupt resource. The returned interrupt object represents that connection. This status indicates that the same vector or connection context is already active, commonly because start logic ran twice, rollback missed a disconnect, or two layers both assumed ownership of the resource.
Do not treat a second registration as harmless. Duplicate setup can leave inconsistent spin-lock, affinity or message information even if interrupts appear to work. Track registration as part of the device PnP state and pair each successful connect with exactly one disconnect during stop, surprise removal or failed-start cleanup.
What to inspect
- Log the translated interrupt descriptor, connect version and returned interrupt object.
- Check repeated IRP_MN_START_DEVICE and error-unwind paths for a missing ownership flag.
- For MSI/MSI-X, compare message count and connection context rather than only the legacy vector number.
References
- Microsoft: Interrupt service routines
- Microsoft: Registering an ISR
- Microsoft: Interrupt resource descriptors
- Microsoft: IRP_MN_START_DEVICE
- Microsoft Open Specifications: NTSTATUS values
- ReactOS source: PnP device action processing
Looking for a different code? Search another status or error code.