| 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. It applies to destruction or reuse of a VID memory block that still has active references.
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.
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. |
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 test run, keep page units, GPA boundaries, parent object, handle generation, and release order visible.
How to read the controls
| Control | Interpretation | Hold constant |
|---|---|---|
| Smaller exact range | 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. |
| Balanced fresh lifecycle | Create, use, release, and destroy one object instance. If a different result appears after recreation, investigate leaked references, locks, handles, or mappings. | Preserve sizes and operation order while changing only generation. |
| Same request under lower host pressure | 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. |
Scope of this status
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.
Technical references
- Microsoft Open Specifications: HRESULT values — used to interpret this result.
- Microsoft: WHvMapGpaRange — used to interpret this result.
- Microsoft: WHP memory data types — 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.