| Previous | Next |
| ERROR_PAGE_FAULT_PAGING_FILE | ERROR_CRASH_DUMP |
ERROR_CACHE_PAGE_LOCKED
a cached page was locked as part of the current operation.
ERROR_CACHE_PAGE_LOCKED identifies this condition: Windows uses this informational result while coordinating cache-manager and memory-manager work. It indicates that a cache page has been pinned or locked so the operation can proceed without the page disappearing from the expected state.
Where the result appears
- file-system cache operations.
- mapped-file I/O.
- filter-driver paths that cooperate with the cache manager.
- kernel traces of page locking and unlocking.
What to collect
- file object and byte range involved.
- whether the page lock is balanced by a corresponding unlock.
- thread stack showing cache-manager callbacks.
- pool, locked-page, and I/O counters around the operation.
Handling and recovery
Treat the code as state information. Driver code must preserve lock/unlock symmetry and avoid holding locked pages across unrelated waits. User-mode software normally should not see or act on it directly.
Common misinterpretation
A page being locked is not the same as a file being locked against other applications. Applying file-sharing diagnostics to this status wastes time and misses the cache lifetime issue.
References
Looking for a different code? Search another status or error code.