| Previous | Next |
| ERROR_VID_INVALID_PPM_HANDLE | ERROR_VID_MESSAGE_QUEUE_CLOSED |
ERROR_VID_MBPS_ARE_LOCKED
ERROR_VID_MBPS_ARE_LOCKED is HRESULT 0xC0370019 in the VID locked memory-block pages area of the Windows virtualization stack. It applies to an operation that requires memory-block pages to be unlocked while one or more MBPs remain locked.
Where the result originates
The requested transition conflicts with active page locks. Identify the lock owner and purpose; forcing the transition can violate DMA, mapping, or notification assumptions.
Neighboring result: LOCK_COUNT_EXCEEDED is a capacity failure while acquiring locks. MBPS_ARE_LOCKED is a state conflict encountered by another operation.
Build an incident record
| Evidence | Why it changes the diagnosis |
|---|---|
| Locked page set | Record GPA/pages, lock flags, owner, and acquisition time. |
| Conflicting operation | Keep property, notification, destroy, or remap request that needs unlocked pages. |
| Completion dependency | Identify I/O, VP exit, or asynchronous work holding the lock. |
| Unlock path | Capture whether cancellation and error handling release it. |
Run narrow checks
- Wait for the owning operation to complete or cancel through its supported path.
- Do not reuse the block while DMA or mapping work is active.
- Add lock-owner diagnostics and maximum age alerts.
- Inject cancellation at each asynchronous stage.
Use a controlled partition or disposable VM when a mapping, lock, or teardown test can be destructive. During the test run, keep page units, GPA boundaries, parent object, handle generation, and release order visible.
Interpret three controls
| Control | Interpretation | Hold constant |
|---|---|---|
| Balanced fresh lifecycle | Create, use, release, and destroy one object instance. If a different result appears after recreation, investigate leaked references, locks, handles, or mappings. | Preserve sizes and operation order while changing only generation. |
| Same request under lower host pressure | If it 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 | 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. |
Keep neighboring states separate
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.
Prove the correction
The conflicting operation runs only after all intended locks release, and no lock survives cancellation or teardown.
Technical references
- Microsoft Open Specifications: HRESULT values — used to interpret this result.
- Microsoft: WHvMapGpaRange — used to interpret this result.
- Microsoft: WHP memory data types — used to interpret this result.
- Microsoft: Hyper-V architecture — used to interpret this result.
Looking for a different code? Search another status or error code.