What does HRESULT 0xC037001A (ERROR_VID_MESSAGE_QUEUE_CLOSED) mean?

 
Could be also:
ConstantTypeOS
STATUS_VID_MESSAGE_QUEUE_CLOSEDNTSTATUSWindows
Previous Next
ERROR_VID_MBPS_ARE_LOCKED ERROR_VID_VIRTUAL_PROCESSOR_LIMIT_EXCEEDED

ERROR_VID_MESSAGE_QUEUE_CLOSED

ERROR_VID_MESSAGE_QUEUE_CLOSED is HRESULT 0xC037001A in the VID queue closure state area of the Windows virtualization stack. It applies to a known VID message queue that has entered its closed lifecycle state.

State and ownership model

The queue identity is recognized, but enqueue, receive, or notification work arrived after closure began. Determine whether shutdown ordering is correct or a producer/consumer outlived the channel.

Neighboring result: INVALID_MESSAGE_QUEUE_HANDLE means the token itself is not valid; QUEUE_FULL means the live queue lacks capacity. CLOSED is a lifecycle result.

Capture before changing anything

EvidenceWhy it changes the diagnosis
Close initiatorRecord thread, reason, and timestamp that closed the queue.
Late operationCapture enqueue/dequeue/association request and its owner.
Drain stateKeep remaining depth, outstanding acknowledgements, and final consumer result.
Generation handoffRecord replacement queue creation and publication order.

Reduce the case safely

  1. Stop producers before closing and drain or cancel according to message semantics.
  2. Publish a replacement only after its consumer is ready.
  3. Make close idempotent but reject new work immediately.
  4. Test worker crash, VM stop, and migration handoff.

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.

What comparison can tell you

ControlInterpretationHold constant
Single producer and consumerIf 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 generationA 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.
Controlled stall or burstDeliberately 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.

Do not erase the evidence

Closure criteria

Shutdown has a documented final-message boundary, no producer writes after close, and restart routes work only to the new queue.

Technical references


Looking for a different code? Search another status or error code.