| Previous | Next |
| STATUS_VID_INVALID_NUMA_NODE_INDEX | STATUS_VID_INVALID_MEMORY_BLOCK_HANDLE |
STATUS_VID_NOTIFICATION_QUEUE_ALREADY_ASSOCIATED
A notification queue is already attached to the memory block
STATUS_VID_NOTIFICATION_QUEUE_ALREADY_ASSOCIATED means the memory block already has the queue association the caller is trying to create.
The memory block already owns a notification-queue association, and VID is rejecting a second association attempt. Review the first attach operation and any subsequent rollback: a later setup failure may leave the queue relationship intact even when higher-level code assumes the whole sequence was undone.
This is a duplicate-association state, not a missing-queue state. It often appears when retry logic assumes that a failed later step rolled back the earlier queue association, but it did not.
What to inspect
- Find the first successful queue association for the memory block.
- Check whether the later retry uses the same queue or accidentally tries to attach a second queue.
- Correlate with message-queue lifecycle statuses if the associated queue was closed or replaced.
References
- Microsoft TLFS: inter-partition communication
- Microsoft TLFS: HV_MESSAGE
- Microsoft: WHvMapGpaRange
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.