| Previous | Next |
| ERROR_VID_TOO_MANY_HANDLERS | ERROR_VID_HANDLER_NOT_PRESENT |
ERROR_VID_QUEUE_FULL
ERROR_VID_QUEUE_FULL is HRESULT 0xC0370003 in the VID message queue backpressure area of the Windows virtualization stack. The built-in message names the immediate result; the useful custom context is the exact boundary: a host-side VID message queue that cannot accept another item. Record the first returning operation and host-side event before a management layer retries or translates it.
Object lifecycle behind the result
Producers have outrun consumption or the consumer is blocked, stopped, or unable to acknowledge work. Queue depth and oldest-item age are more useful than generic CPU or network checks.
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 is a lifecycle end state; QUEUE_FULL means the queue still exists but has no capacity for the new message.
Diagnostic evidence matrix
| Evidence | Why it changes the diagnosis |
|---|---|
| Queue identity | Record partition, queue name/handle, producer, and consumer. |
| Depth timeline | Capture capacity, current depth, oldest item age, enqueue rate, and dequeue rate. |
| Consumer state | Keep thread wait reason, VP/worker state, and the last successfully processed message. |
| Backpressure policy | Record retry, drop, coalescing, and acknowledgement behavior. |
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.
Test one variable at a time
- Pause producers in a controlled test and verify whether the queue drains.
- Inspect the oldest unconsumed message before clearing the queue.
- Bound retries and preserve ordering for stateful messages.
- Test consumer failure and restart without losing queue ownership.
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.
How to read the controls
Across these controls for it, preserve a host-side VID message queue that cannot accept another item 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. |
Boundaries of this status
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.
Regression proof
The repair maintains bounded queue latency under expected peak load and recovers cleanly after a deliberately stalled consumer. 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.