| Previous | Next |
| ERROR_VID_MB_STILL_REFERENCED | ERROR_VID_INVALID_NUMA_SETTINGS |
ERROR_VID_CHILD_GPA_PAGE_SET_CORRUPTED
ERROR_VID_CHILD_GPA_PAGE_SET_CORRUPTED is HRESULT 0xC037000E in the VID child GPA lock bookkeeping area of the Windows virtualization stack. The built-in message names the immediate result; the useful custom context is the exact boundary: the recorded set of child guest-physical pages associated with a prior lock request. Record the first returning operation and host-side event before a management layer retries or translates it.
What the code establishes
An unlock or comparison does not match the page set originally recorded. This is bookkeeping corruption or request mismatch at the host memory-management boundary, not a statement that guest file data is corrupt.
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_CHILD_GPA_PAGE_SET rejects an invalid request shape; CORRUPTED indicates the recorded lock set and the attempted unlock no longer agree.
Evidence that should survive remediation
| Evidence | Why it changes the diagnosis |
|---|---|
| Original lock | Record GPA pages, count, ordering, access, partition, and returned range token. |
| Unlock request | Capture the exact page array and generation presented later. |
| Mutation history | Identify compaction, sorting, reuse, or concurrent writes to the page list. |
| Reset/migration boundary | Record whether partition generation changed between lock and unlock. |
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
- Treat the locked page set as immutable until unlock completes.
- Pair unlock with the exact token and count returned by lock.
- Reject arrays from another partition or generation.
- Add checksums or debug copies around page-list ownership in the caller.
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 recorded set of child guest-physical pages associated with a prior lock request 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
Every successful lock has one exact matching unlock under concurrency and failure injection, with no page-list mutation. 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.