| 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. It applies to an opaque handle representing a mapped or locked guest-physical address range.
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.
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. |
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 test run, keep page units, GPA boundaries, parent object, handle generation, and release order visible.
What comparison can tell you
| Control | Interpretation | Hold constant |
|---|---|---|
| Same request under lower host pressure | 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 | 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. |
| Balanced fresh lifecycle | Create, use, release, and destroy one object instance. If a different result appears after recreation, investigate leaked references, locks, handles, or mappings. | Preserve sizes and operation order while changing only generation. |
Do not erase the evidence
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.
Technical references
- Microsoft Open Specifications: HRESULT values — used to interpret this result.
- Microsoft: WHvMapGpaRange — used to interpret this result.
- Microsoft: WHP memory data types — used to interpret this result.
- Microsoft: Hyper-V architecture — used to interpret this result.
Looking for a different code? Search another status or error code.