| 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. It applies to installation of notifications on a memory block that has no associated message queue.
Why this result 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.
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. |
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.
Reproduce this condition 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
| Control | Interpretation | Hold constant |
|---|---|---|
| Controlled stall or burst | 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 | If it disappears with serialized ownership, the queue, handler, acknowledgement, or delivery race is implicated. | Preserve message type, partition, target VP, and queue capacity. |
| Fresh channel generation | 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 test. |
Misleading shortcuts
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.
Technical references
- Microsoft Open Specifications: HRESULT values — used to interpret this result.
- Microsoft TLFS: inter-partition communication — used to interpret this result.
- Microsoft TLFS: HV_MESSAGE — used to interpret this result.
- Microsoft: Hyper-V architecture — used to interpret this result.
Looking for a different code? Search another status or error code.