| Previous | Next |
| STATUS_BEYOND_VDL | STATUS_PTE_CHANGED |
STATUS_ENCOUNTERED_WRITE_IN_PROGRESS
A concurrent write owns part of the target range
Memory and storage paths can serialize writes while page state, checksums, copy-on-write data, or backing-store metadata are being updated. This status reports that the new operation encountered such ownership. It is not permission to issue the same write concurrently without coordination.
Use the contract of the returning API to decide whether to wait, retry, or complete asynchronously. Preserve ordering and the original buffer until ownership is resolved. An uncontrolled retry loop can starve the active writer or reorder data relative to flush and completion notifications.
What to inspect
- Record the exact byte or page range, owning request, and synchronization object.
- Determine whether the API expects caller retry, queued completion, or cancellation.
- Check overlapping asynchronous writes and cleanup paths for a request that never releases ownership.
References
- Microsoft: Memory management functions
- Microsoft: FlushViewOfFile
- ReactOS source: virtual memory manager
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.