| Previous | Next |
| STATUS_VID_MB_PROPERTY_ALREADY_SET_RESET | STATUS_VID_INVALID_CHILD_GPA_PAGE_SET |
STATUS_VID_MMIO_RANGE_DESTROYED
The MMIO range no longer exists
STATUS_VID_MMIO_RANGE_DESTROYED concerns memory-mapped I/O, not ordinary RAM. The page range used for device emulation or assigned-device communication has been destroyed before the current operation completed.
This code refers to a destroyed memory-mapped I/O range, which is device-facing address space rather than ordinary guest RAM backing. Correlate the failure with virtual-device removal, MMIO unmapping, intercept handling, or partition teardown to determine which component continued using the range after it ceased to exist.
MMIO ranges are especially sensitive to ordering because device backends, intercept handling, and VM teardown can all touch the same range.
What to inspect
- Capture the MMIO base, size, device/backend identity, and partition state.
- Check whether device removal, VM stop, or reset destroyed the range while an intercept was still pending.
- Correlate with virtual-processor stop-pending or invalid GPA-range handle statuses.
References
- Microsoft: WHvCreateVirtualProcessor
- Microsoft: WHvMapGpaRange
- Microsoft: Windows Hypervisor Platform API definitions
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.