| Previous | Next |
| STATUS_VID_INVALID_PPM_HANDLE | STATUS_VID_MESSAGE_QUEUE_CLOSED |
STATUS_VID_MBPS_ARE_LOCKED
Memory-block pages are already locked
STATUS_VID_MBPS_ARE_LOCKED is a lock-state conflict in VID memory-block pages. The request requires a state in which notifications can be created, but the pages are already locked for another operation.
VID is refusing notification setup because memory-block pages are already in a locked state for another operation. This makes operation ordering central: identify who acquired the page locks and whether the notification association was attempted before those locks were released.
This is useful for distinguishing a missing queue from an ordering conflict: STATUS_VID_NO_MEMORY_BLOCK_NOTIFICATION_QUEUE says no queue is associated, while this status says page locks prevent the notification setup.
What to inspect
- Identify the earlier lock owner and whether it belongs to migration, device assignment, save/restore, or memory resize.
- Look for missing unlocks after failed operations.
- Check whether teardown or notification setup races with a page-lock path for the same memory block.
References
- Microsoft: WHvMapGpaRange
- Microsoft: Windows Hypervisor Platform API definitions
- Microsoft: Hyper-V live migration troubleshooting
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.