| Previous | Next |
| STATUS_VID_NOTIFICATION_QUEUE_ALREADY_ASSOCIATED | STATUS_VID_PAGE_RANGE_OVERFLOW |
STATUS_VID_INVALID_MEMORY_BLOCK_HANDLE
Invalid VID memory-block handle
STATUS_VID_INVALID_MEMORY_BLOCK_HANDLE identifies the object class that failed validation: the caller supplied something that is not a live VID memory-block handle.
The failure occurs before VID can act on memory-block contents because the supplied handle is not a valid live memory-block object. Trace where that handle was created, closed, and retained across reset or restore; a page-range or notification-queue handle belongs to a different object type even when it refers to related guest memory.
Differentiate it from invalid GPA-range and invalid message-queue handles. Those statuses point to different host objects and usually different cleanup paths.
What to inspect
- Check handle lifetime across memory resize, VM reset, save/restore, and worker-process restart.
- Verify that the failing call is using a memory-block handle, not a derived page-range or notification-queue handle.
- Look for use-after-close or stale handles retained after an earlier create/setup failure.
References
- Microsoft: WHvMapGpaRange
- Microsoft: Windows Hypervisor Platform API definitions
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.