| Previous | Next |
| ERROR_VID_NOTIFICATION_QUEUE_ALREADY_ASSOCIATED | ERROR_VID_PAGE_RANGE_OVERFLOW |
ERROR_VID_INVALID_MEMORY_BLOCK_HANDLE
ERROR_VID_INVALID_MEMORY_BLOCK_HANDLE is HRESULT 0xC0370012 in the VID memory-block handle validation area of the Windows virtualization stack. The built-in message names the immediate result; the useful custom context is the exact boundary: an opaque VID memory-block handle used for map, lock, notification, property, or destruction work. Record the first returning operation and host-side event before a management layer retries or translates it.
Object lifecycle behind the result
The token does not identify a live memory block in the current partition generation. Investigate wrong-type handles, use-after-destroy, and cross-partition reuse.
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: MB_STILL_REFERENCED means the block is valid but cannot yet be destroyed. INVALID_MEMORY_BLOCK_HANDLE means the supplied object reference itself is unacceptable.
Diagnostic evidence matrix
| Evidence | Why it changes the diagnosis |
|---|---|
| Handle provenance | Record create result, partition, size, and generation. |
| Operation type | Keep the map/lock/property/destroy request that rejected it. |
| Invalidation event | Locate destroy, rollback, worker replacement, or migration. |
| Wrapper type | Confirm the handle was not confused with GPA-range, queue, or PPM handles. |
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
- Use typed wrappers for each opaque VID handle class.
- Clear published handles before destruction begins.
- Tag references with partition generation.
- Stress concurrent destroy against map and notification setup.
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 an opaque VID memory-block handle used for map, lock, notification, property, or destruction work 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
Live handles work only in their owning generation, and stale or wrong-type tokens are rejected by the wrapper before the VID call. 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.