| Previous | Next |
| ERROR_VID_MBP_ALREADY_LOCKED_USING_RESERVED_PAGE | ERROR_VID_SAVED_STATE_CORRUPT |
ERROR_VID_MBP_COUNT_EXCEEDED_LIMIT
ERROR_VID_MBP_COUNT_EXCEEDED_LIMIT is HRESULT 0xC0370026 in the VID memory-block construction limit area of the Windows virtualization stack. The built-in message names the immediate result; the useful custom context is the exact boundary: the number of memory-block pages requested when creating a VID memory block. Record the first returning operation and host-side event before a management layer retries or translates it.
Object lifecycle behind the result
The requested block contains more pages than the platform accepts for one object. Determine whether the caller has a unit bug or must partition the supported workload into multiple blocks.
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: EXCEEDED_MBP_ENTRY_MAP_LIMIT concerns active map entries; MBP_COUNT_EXCEEDED_LIMIT applies to the page count of the memory block itself.
Diagnostic evidence matrix
| Evidence | Why it changes the diagnosis |
|---|---|
| Requested count | Record pages, bytes, page size, alignment, and integer types. |
| Platform boundary | Keep last successful and first failing counts on the same build. |
| Source size | Record VM memory or device aperture that drove the calculation. |
| Split design | Capture required contiguity and whether multiple blocks are supported. |
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
- Check bytes-to-pages rounding and overflow.
- Test the exact observed boundary with no other configuration changes.
- Split only at supported GPA/object boundaries.
- Avoid assuming limits are identical across Windows builds and architectures.
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 the number of memory-block pages requested when creating a VID memory block as the boundary under test.
| Control | Interpretation | Hold constant |
|---|---|---|
| Balanced fresh lifecycle — this result | Create, use, release, and destroy one object generation. A different this result 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. |
| Smaller exact range — it | Reduce only page count or mapped extent. If it moves, range arithmetic, object limits, or reserve capacity is involved. | Keep the same block, GPA base, flags, and partition generation for it. |
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.
Regression proof
The implementation accepts the full supported workload using valid block sizes and rejects oversized requests before allocating partial state. 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.