| Previous | Next |
| ERROR_VID_MMIO_RANGE_DESTROYED | ERROR_VID_RESERVE_PAGE_SET_IS_BEING_USED |
ERROR_VID_INVALID_CHILD_GPA_PAGE_SET
ERROR_VID_INVALID_CHILD_GPA_PAGE_SET is HRESULT 0xC0370022 in the VID child GPA page-set validation area of the Windows virtualization stack. The built-in message names the immediate result; the useful custom context is the exact boundary: the page array or guest-physical extent presented to a VID child-partition lock or unlock operation. Record the first returning operation and host-side event before a management layer retries or translates it.
What the code establishes
The request shape, pages, count, alignment, ownership, or generation is invalid before matching it against a prior lock. Validate the page-set contract at the caller boundary.
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: CHILD_GPA_PAGE_SET_CORRUPTED indicates disagreement with recorded state; INVALID_CHILD_GPA_PAGE_SET means the submitted set itself is unacceptable.
Evidence that should survive remediation
| Evidence | Why it changes the diagnosis |
|---|---|
| Page set | Record each GPA page, count, order, duplicates, alignment, and access flags. |
| Partition ownership | Keep child partition and memory-block identities. |
| Range validation | Show every page lies within the intended mapped extent. |
| Generation | Record reset, migration, or teardown between construction and submission. |
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
- Validate count and page alignment before the VID request.
- Reject duplicate or out-of-range pages explicitly.
- Keep the array immutable until completion.
- Test empty, one-page, boundary, duplicate, and cross-partition cases.
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 the page array or guest-physical extent presented to a VID child-partition lock or unlock operation 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. |
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 valid page sets lock/unlock symmetrically, and malformed controls are rejected deterministically before state changes. 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.