| Previous | Next |
| ERROR_VID_INVALID_MEMORY_BLOCK_HANDLE | ERROR_VID_INVALID_MESSAGE_QUEUE_HANDLE |
ERROR_VID_PAGE_RANGE_OVERFLOW
ERROR_VID_PAGE_RANGE_OVERFLOW is HRESULT 0xC0370013 in the VID GPA range arithmetic area of the Windows virtualization stack. The built-in message names the immediate result; the useful custom context is the exact boundary: calculation of a page range within a VID memory block or guest-physical extent. Record the first returning operation and host-side event before a management layer retries or translates it.
What the code establishes
The requested start plus page count exceeds the valid memory-block range or overflows the range representation. Preserve both page and byte forms to expose unit and arithmetic errors.
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: RESERVE_PAGE_SET_TOO_SMALL is capacity of a reserve set; PAGE_RANGE_OVERFLOW is invalid range arithmetic relative to the memory block.
Evidence that should survive remediation
| Evidence | Why it changes the diagnosis |
|---|---|
| Range tuple | Record block page count, start page, requested pages, and computed end. |
| Unit conversion | Keep page size, byte offset, alignment, and checked multiplication results. |
| Integer widths | Record 32/64-bit types and language-binding conversions. |
| Boundary cases | Test zero, last valid page, exact-end range, and one-page overflow. |
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.
Controlled diagnostic sequence
- Use checked addition before comparing end against block size.
- Normalize all values to pages or bytes once, not repeatedly.
- Reject negative/signed-to-unsigned conversions at the API boundary.
- Fuzz range calculations near UINT32 and UINT64 limits.
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.
Read the comparison tests
Across these controls for it, preserve calculation of a page range within a VID memory block or guest-physical extent as the boundary under test.
| Control | Interpretation | Hold constant |
|---|---|---|
| Same request under lower host pressure — this result | If this result 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. |
| 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. |
Avoid the wrong recovery
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.
Acceptance test
All in-range boundaries succeed, every out-of-range request fails deterministically, and arithmetic sanitizers report no overflow. 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.