| Previous | Next |
| ERROR_VID_PAGE_RANGE_OVERFLOW | ERROR_VID_INVALID_GPA_RANGE_HANDLE |
ERROR_VID_INVALID_MESSAGE_QUEUE_HANDLE
ERROR_VID_INVALID_MESSAGE_QUEUE_HANDLE is HRESULT 0xC0370014 in the VID queue handle validation area of the Windows virtualization stack. The built-in message names the immediate result; the useful custom context is the exact boundary: an opaque message-queue handle passed to a VID queue operation. Record the first returning operation and host-side event before a management layer retries or translates it.
Locate the failing boundary
The handle is not valid in the current host, partition, or queue generation. Common causes are use-after-close, wrong object type, cross-partition reuse, and serialization of an opaque handle.
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: MESSAGE_QUEUE_CLOSED can be returned for a known queue that reached closed state. INVALID_HANDLE indicates the supplied token cannot be accepted as the intended live queue object.
Build an incident record
| Evidence | Why it changes the diagnosis |
|---|---|
| Handle value and source | Record where it was obtained and whether it crossed process or IPC boundaries. |
| Owner identity | Keep partition, worker, queue name, and generation. |
| Close/delete timeline | Locate the first transition that invalidated the handle. |
| Type checks | Confirm the wrapper did not confuse memory-block, GPA-range, or queue handles. |
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.
Run narrow checks
- Never persist or serialize opaque VID handles.
- Clear shared handle state before closing the queue.
- Use generation-tagged wrappers and reject cross-partition use.
- Race close against enqueue/dequeue under instrumentation.
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.
Interpret three controls
Across these controls for it, preserve an opaque message-queue handle passed to a VID queue operation as the boundary under test.
| Control | Interpretation | Hold constant |
|---|---|---|
| Single producer and consumer — this result | 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. |
| Controlled stall or burst — it | 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. |
Keep neighboring states separate
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.
Prove the correction
All queue operations use live current-generation handles, and deliberate stale or wrong-type handles fail before state mutation. 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.