| Previous | Next |
| ERROR_VID_RESERVE_PAGE_SET_IS_BEING_USED | ERROR_VID_MBP_ALREADY_LOCKED_USING_RESERVED_PAGE |
ERROR_VID_RESERVE_PAGE_SET_TOO_SMALL
ERROR_VID_RESERVE_PAGE_SET_TOO_SMALL is HRESULT 0xC0370024 in the VID reserve page-set capacity 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 reserve pages available for a requested memory-block lock. Record the first returning operation and host-side event before a management layer retries or translates it.
State and ownership model
The selected reserve set cannot cover the requested lock. Compare requested pages with usable reserve capacity after alignment and any platform overhead.
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: PAGE_RANGE_OVERFLOW means the target range is invalid; TOO_SMALL means the range may be valid but the chosen reserve set lacks capacity.
Capture before changing anything
| Evidence | Why it changes the diagnosis |
|---|---|
| Requested lock size | Record GPA start, page count, alignment, and access. |
| Reserve capacity | Keep total and currently available reserve pages. |
| Concurrent borrowers | Identify other locks using the same set. |
| Sizing policy | Record how the reserve size was calculated from maximum request shape. |
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.
Reduce the case safely
- Size the reserve set for the maximum supported lock, not an average request.
- Reject requests exceeding the declared capacity before borrowing.
- Separate concurrent operations or allocate independent reserves.
- Test exact-capacity and one-page-over controls.
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.
What comparison can tell you
Across these controls for it, preserve the number of reserve pages available for a requested memory-block lock 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. |
Do not erase the evidence
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.
Closure criteria
The maximum supported lock succeeds at exact capacity, while larger requests fail early without partially consuming the set. 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.