| Previous | Next |
| ERROR_VID_INVALID_GPA_RANGE_HANDLE | ERROR_VID_MEMORY_BLOCK_LOCK_COUNT_EXCEEDED |
ERROR_VID_NO_MEMORY_BLOCK_NOTIFICATION_QUEUE
ERROR_VID_NO_MEMORY_BLOCK_NOTIFICATION_QUEUE is HRESULT 0xC0370016 in the VID memory notification prerequisites area of the Windows virtualization stack. The built-in message names the immediate result; the useful custom context is the exact boundary: installation of notifications on a memory block that has no associated 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 notification subscription lacks its delivery channel. Establish queue ownership and association before enabling notifications, and ensure teardown does not remove the queue first.
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: NOTIFICATION_QUEUE_ALREADY_ASSOCIATED means a queue is already bound; this status means none is available for the memory block.
Records worth collecting
| Evidence | Why it changes the diagnosis |
|---|---|
| Memory block | Record handle, partition, GPA extent, and generation. |
| Association state | Capture expected queue name/handle and association result. |
| Subscription request | Keep notification type, callback owner, and ordering. |
| Teardown sequence | Record whether queue closure preceded notification removal. |
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
- Create and associate the queue before installing notifications.
- Publish subscription readiness only after association succeeds.
- Remove subscriptions before closing the queue.
- Test partial initialization rollback after each step.
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 installation of notifications on a memory block that has no associated 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.
A handle observed is generation-bound. Keep its parent partition and object type beside the token; never serialize it, copy it to another partition, or reuse it after the terminal transition.
Verification after repair
Notifications are delivered through exactly one associated live queue, and teardown produces no late subscription work. 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.