| 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.
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.
What 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.
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.
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.
References
Looking for a different code? Search another status or error code.