| Previous | Next |
| ERROR_VID_INVALID_MESSAGE_QUEUE_HANDLE | ERROR_VID_NO_MEMORY_BLOCK_NOTIFICATION_QUEUE |
ERROR_VID_INVALID_GPA_RANGE_HANDLE
ERROR_VID_INVALID_GPA_RANGE_HANDLE is HRESULT 0xC0370015 in the VID GPA-range handle validation area of the Windows virtualization stack. The built-in message names the immediate result; the useful custom context is the exact boundary: an opaque handle representing a mapped or locked guest-physical address range. Record the first returning operation and host-side event before a management layer retries or translates it.
State and ownership model
The supplied token does not refer to a live GPA range for this partition generation. The root cause is usually lifecycle or ownership, not the bytes stored at the GPA.
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: INVALID_MEMORY_BLOCK_HANDLE concerns the parent block; INVALID_GPA_RANGE_HANDLE concerns the child range object produced from it.
Capture before changing anything
| Evidence | Why it changes the diagnosis |
|---|---|
| Range handle provenance | Record the operation that created it, GPA start, size, and parent block. |
| Owner generation | Keep partition and worker identity. |
| Unmap/unlock history | Locate the transition that ended the range lifetime. |
| Cross-object use | Check whether a queue, PPM, or block handle was passed accidentally. |
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
- Bind each range handle to its parent block and partition in the wrapper.
- Invalidate after unmap/unlock before releasing caller-visible state.
- Reject handles crossing migration or partition reset.
- Race teardown with the exact operation that failed.
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 an opaque handle representing a mapped or locked guest-physical address range 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. |
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.
A handle observed is generation-bound. Keep its parent partition and object type beside the token; never serialize it, copy it to another partition, or reuse it after the terminal transition.
Closure criteria
Current ranges remain usable until one defined terminal transition, after which stale tokens cannot reach VID. 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.