| Previous | Next |
| ERROR_NOACCESS | ERROR_STACK_OVERFLOW |
ERROR_SWAPERROR
error performing inpage operation.
ERROR_SWAPERROR means that windows could not page required data into memory from its backing store or mapped file. In this case, the decisive context is loading an executable image or DLL page on demand, together with the accompanying NTSTATUS or exception information when available.
Where the result appears
- loading an executable image or DLL page on demand.
- accessing a memory-mapped database, archive, executable, or data file.
- paging memory backed by the system page file.
- reading data through storage, filesystem, filter-driver, or network-backed mappings.
Typical causes
- the underlying disk, controller, cable, filesystem, or network path returned an I/O failure.
- a mapped file changed, disappeared, or became inaccessible after the mapping was created.
- storage corruption or bad sectors affected the requested page.
- a filter driver, antivirus product, encryption layer, or remote redirector failed the inpage request.
Evidence to collect
- the accompanying NTSTATUS or exception information when available.
- path of the mapped image or file and offset being accessed.
- System and storage event logs, SMART/health data, and filesystem diagnostics.
- whether the backing file is local, removable, compressed, encrypted, sparse, or remote.
For this condition, begin the investigation with the accompanying NTSTATUS or exception information when available. Correlate it with path of the mapped image or file and offset being accessed and check whether the underlying disk, controller, cable, filesystem, or network path returned an I/O failure. Capture the original this result immediately after the failing call so later cleanup does not replace the thread-local error value.
Handling and recovery
Preserve the underlying I/O status because it usually identifies the real cause more precisely than this result. Stop repeatedly touching the same mapped region if hardware or filesystem damage is suspected. For durable data, move recovery to a verified copy, restore, or storage-repair workflow.
Any retry policy for this Win32 error should be tied to evidence that a mapped file changed, disappeared, or became inaccessible after the mapping was created has changed. Before another attempt, verify System and storage event logs, SMART/health data, and filesystem diagnostics. If a filter driver, antivirus product, encryption layer, or remote redirector failed the inpage request still applies, stop the retry sequence and preserve the first diagnostic event.
Common misinterpretation
The word “swap” is historical and does not prove that the page file is the failing object. The backing data may come from an executable, DLL, mapped document, database, or network file.
Guidance for developers
When surfacing this result through another layer, retain its Win32 domain, numeric value, and the operation described by accessing a memory-mapped database, archive, executable, or data file. A useful telemetry record also includes whether the backing file is local, removable, compressed, encrypted, sparse, or remote. For windows-related handling, decisions must use the numeric value and documented API contract rather than localized wording.
A focused test should reproduce the condition in which storage corruption or bad sectors affected the requested page, assert this result, and confirm that the program releases resources associated with paging memory backed by the system page file. The recovery test should also verify that the accompanying NTSTATUS or exception information when available is refreshed before the operation resumes.
References
Looking for a different code? Search another status or error code.