| Previous | Next |
| ERROR_VID_INVALID_NUMA_NODE_INDEX | ERROR_VID_INVALID_MEMORY_BLOCK_HANDLE |
ERROR_VID_NOTIFICATION_QUEUE_ALREADY_ASSOCIATED
ERROR_VID_NOTIFICATION_QUEUE_ALREADY_ASSOCIATED is HRESULT 0xC0370011 in the VID memory notification binding area of the Windows virtualization stack. The built-in message names the immediate result; the useful custom context is the exact boundary: association between a VID memory block and its notification message queue. Record the first returning operation and host-side event before a management layer retries or translates it.
Why this HRESULT is specific
The memory block already has a queue association, so a second binding would create ambiguous notification ownership. Identify whether the request duplicates the same queue or tries to replace it while active.
Hyper-V architecture documentation identifies VID as the component that provides partition, virtual-processor, and memory-management services., many ERROR_VID_* values describe internal host objects rather than a public API that administrators should call directly. Accordingly, diagnose this result through the named object/state, the VMMS or Worker event chain, and the operation that produced it; do not invent a user-mode VID call from the constant name.
Neighboring result: NO_MEMORY_BLOCK_NOTIFICATION_QUEUE means the required association is absent. ALREADY_ASSOCIATED means one exists and must be examined before rebinding.
Records worth collecting
| Evidence | Why it changes the diagnosis |
|---|---|
| Memory block identity | Record handle, partition, GPA extent, and object generation. |
| Current queue | Capture associated queue handle/name, owner, and active notification types. |
| New request | Keep proposed queue identity and reason for rebinding. |
| Outstanding notifications | Record queued or unacknowledged events before teardown. |
Preserve identifiers and counts without dumping guest secrets or unrelated memory. Useful this result timestamps include the last successful operation, first failure, any automatic retry, and the object-generation change that followed.
A reproducible test plan
- Reuse the existing association only when owner and format match.
- Quiesce notifications before changing queue ownership.
- Make association state atomic with memory-block lifecycle.
- Test replacement during VM stop and migration.
Exercise this result with bounded producers and a fully instrumented consumer. Preserve message ordering, queue generation, handler ownership, target VP, and acknowledgement timestamps while changing only one concurrency condition.
Comparison matrix
Across these controls for it, preserve association between a VID memory block and its notification message queue as the boundary under test.
| Control | Interpretation | Hold constant |
|---|---|---|
| Controlled stall or burst — this result | Deliberately slow the consumer or bound the producer rate. The threshold at which it appears identifies backpressure versus lifecycle failure. | Record queue depth, oldest-item age, and acknowledgement timing. |
| Single producer and consumer — it | If it disappears with serialized ownership, the queue, handler, acknowledgement, or delivery race is implicated. | Preserve message type, partition, target VP, and queue capacity for it. |
| Fresh channel generation — it | A new queue or handler generation changing it points to stale registration, backlog, or incomplete teardown. | Keep payload, producer order, and host build unchanged in the result test. |
Misleading shortcuts
A VM or service restart can empty queues and replace handler generations, temporarily hiding it. Before clearing the result channel, capture depth, oldest item, owner, delivery sequence, and acknowledgement state.
Verification after repair
Each memory block has one unambiguous current queue, and association changes lose neither notifications nor ownership state. Repeat the original operation under the original supported conditions and retain one deliberate negative control. A management command succeeding on a different object is not sufficient to close this incident.
Technical references
These sources define it and the public Hyper-V architecture surrounding the internal state. They do not create a public user-mode VID API for the named object.
- Microsoft Open Specifications: HRESULT values — used to interpret the boundary.
- Microsoft TLFS: inter-partition communication — used to interpret the boundary.
- Microsoft TLFS: HV_MESSAGE — used to interpret the boundary.
- Microsoft: Hyper-V architecture — used to interpret the boundary.
Looking for a different code? Search another status or error code.