| Previous | Next |
| ERROR_VID_MB_PROPERTY_ALREADY_SET_RESET | ERROR_VID_INVALID_CHILD_GPA_PAGE_SET |
ERROR_VID_MMIO_RANGE_DESTROYED
ERROR_VID_MMIO_RANGE_DESTROYED is HRESULT 0xC0370021 in the VID MMIO range lifetime area of the Windows virtualization stack. The built-in message names the immediate result; the useful custom context is the exact boundary: a memory-mapped I/O range associated with a guest page range that no longer exists. Record the first returning operation and host-side event before a management layer retries or translates it.
Object lifecycle behind the result
The operation retained or used an MMIO range after its destruction. Treat this as device/range lifecycle and generation ownership, not ordinary guest RAM mapping.
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_GPA_RANGE_HANDLE can describe an unrecognized range token; MMIO_RANGE_DESTROYED specifically indicates that the MMIO object once existed and reached a terminal state.
Diagnostic evidence matrix
| Evidence | Why it changes the diagnosis |
|---|---|
| MMIO range | Record GPA base, size, device, access type, and generation. |
| Destroy event | Keep initiator, reason, and completion time. |
| Late access | Capture VP exit, device callback, or mapping request that used the range afterward. |
| Device teardown order | Record callback quiesce, interrupt disable, range removal, and object release. |
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.
Test one variable at a time
- Stop device callbacks and VP access before destroying the range.
- Version cached range descriptors across hot-remove and restore.
- Cancel pending MMIO emulation work during teardown.
- Test device remove while the guest actively accesses the range.
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.
How to read the controls
Across these controls for it, preserve a memory-mapped I/O range associated with a guest page range that no longer exists 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. |
Boundaries of this status
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.
Regression proof
No callback or VP path references the range after destruction, and a recreated device publishes a distinct current-generation range. 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.