| Previous | Next |
| STATUS_VID_INVALID_GPA_RANGE_HANDLE | STATUS_VID_INVALID_PPM_HANDLE |
STATUS_VID_NO_MEMORY_BLOCK_NOTIFICATION_QUEUE
No notification queue is associated with the memory block
STATUS_VID_NO_MEMORY_BLOCK_NOTIFICATION_QUEUE says that the memory block exists, but the notification path needed for the requested operation is missing.
The memory block is present, but VID has no notification queue associated with it for the requested client-notification operation. Verify whether queue creation succeeded and whether the attach step ran before page locking or notification installation; recreating guest memory is not the first diagnostic action.
The distinction matters: the fix is not to recreate guest memory blindly. First determine whether the queue association step was skipped, failed, or was removed during teardown.
What to inspect
- Find the memory-block creation and the queue-association operation for the same object.
- Check for retry paths that reused the memory block without reattaching the notification queue.
- Correlate with queue close, duplicate queue, or invalid message-queue handle statuses.
References
- Microsoft TLFS: inter-partition communication
- Microsoft TLFS: HV_MESSAGE
- Microsoft: WHvMapGpaRange
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.