| Previous | Next |
| ERROR_VID_EXCEEDED_MBP_ENTRY_MAP_LIMIT | ERROR_VID_CHILD_GPA_PAGE_SET_CORRUPTED |
ERROR_VID_MB_STILL_REFERENCED
ERROR_VID_MB_STILL_REFERENCED is HRESULT 0xC037000D in the VID memory-block lifetime area of the Windows virtualization stack. The built-in message names the immediate result; the useful custom context is the exact boundary: destruction or reuse of a VID memory block that still has active references. Record the first returning operation and host-side event before a management layer retries or translates it.
Object lifecycle behind the result
Another object—such as a mapping, notification association, locked page, or pending operation—still owns the block. The correct task is to find the reference, not to force deletion.
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: MBPS_ARE_LOCKED identifies locked pages; RESERVE_PAGE_SET_IS_BEING_USED identifies a reserve set. STILL_REFERENCED is broader ownership evidence at memory-block teardown.
Diagnostic evidence matrix
| Evidence | Why it changes the diagnosis |
|---|---|
| Memory block identity | Record handle, size, GPA use, partition, and generation. |
| Reference inventory | List mappings, locks, notification queues, MMIO ranges, and in-flight operations. |
| Teardown order | Keep timestamps for detach, unmap, unlock, disassociate, and destroy. |
| Leaked owner | Capture object or thread that retained the final reference. |
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
- Release child objects before destroying their memory block.
- Use reference-count diagnostics around partial initialization failure.
- Wait for asynchronous completion rather than sleeping a fixed interval.
- Test teardown with pending notifications and VP exits.
Use a controlled partition or disposable VM when a mapping, lock, or teardown test can be destructive. During the result run, keep page units, GPA boundaries, parent object, handle generation, and release order visible.
How to read the controls
Across these controls for it, preserve destruction or reuse of a VID memory block that still has active references as the boundary under test.
| Control | Interpretation | Hold constant |
|---|---|---|
| Smaller exact range — this result | Reduce only page count or mapped extent. If this result moves, range arithmetic, object limits, or reserve capacity is involved. | Keep the same block, GPA base, flags, and partition generation for it. |
| Balanced fresh lifecycle — it | Create, use, release, and destroy one object generation. A different it exposes leaked references, locks, handles, or mappings. | Preserve sizes and operation order while changing only generation. |
| Same request under lower host pressure — it | If it changes after controlled pressure is removed, quantify host/pool capacity; if not, focus on caller bookkeeping. | Do not modify guest disks or unrelated VM devices during the result comparison. |
Boundaries of this status
Restarting can release the exact lock, reference, mapping, or opaque handle behind it without fixing the lifecycle defect. Before recovering from it, preserve the object graph and acquire/release counts.
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.
Regression proof
The block reaches zero references through normal ownership release and repeated teardown leaves no retained mapping or queue. 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: WHvMapGpaRange — used to interpret the boundary.
- Microsoft: WHP memory data types — 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.