| Previous | Next |
| STATUS_VID_EXCEEDED_MBP_ENTRY_MAP_LIMIT | STATUS_VID_CHILD_GPA_PAGE_SET_CORRUPTED |
STATUS_VID_MB_STILL_REFERENCED
The memory block is still referenced
STATUS_VID_MB_STILL_REFERENCED is a teardown ordering failure. VID refused to destroy a memory block because some page range, notification queue, mapping, or client still owns a reference to it.
VID still has at least one reference to the memory block when destruction is requested, so teardown cannot complete safely. Follow dependent GPA ranges, mappings, notification associations, and clients back to their owners to find the reference that outlived the block's intended lifetime.
Do not treat it as ordinary low memory. The important question is who still references the block after the higher layer decided it should be destroyed.
What to inspect
- Trace memory-block create, map, lock, notification association, and close operations for the same VM.
- Check whether an earlier device or worker-process path failed before releasing its mapping.
- Look for outstanding GPA-range handles when VM teardown or memory resize begins.
References
- Microsoft: WHvMapGpaRange
- Microsoft: WHvUnmapGpaRange
- Microsoft: Windows Hypervisor Platform API definitions
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.