| Previous | Next |
| STATUS_VID_MESSAGE_QUEUE_ALREADY_EXISTS | STATUS_VID_MB_STILL_REFERENCED |
STATUS_VID_EXCEEDED_MBP_ENTRY_MAP_LIMIT
Memory-block page map limit reached
STATUS_VID_EXCEEDED_MBP_ENTRY_MAP_LIMIT points at the bookkeeping for mapped memory-block pages. It is a host-side mapping-capacity failure in VID, not a guest page-fault status.
This status is about VID's map bookkeeping for memory-block pages, not the amount of free RAM reported inside the guest. Public Windows Hypervisor Platform APIs likewise separate GPA mappings from guest memory contents, so the useful evidence is how many ranges were mapped, unmapped, or retained by the host-side memory path.
The Windows Hypervisor Platform API exposes the same conceptual boundary: guest physical address ranges are explicitly mapped to backing memory owned by the caller or host virtualization layer.
What to inspect
- Check the size and fragmentation of GPA mappings created for the VM.
- Look for a leak where ranges are mapped repeatedly but not released during retry or teardown.
- Correlate with Dynamic Memory, device assignment, or restore operations that change many GPA ranges.
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.
