| Previous | Next |
| STATUS_APP_INIT_FAILURE | STATUS_NO_PAGEFILE |
STATUS_PAGEFILE_CREATE_FAILED
The paging-file configuration could not be realized on the volume
Page-file creation occurs early and depends on an accessible local volume, sufficient space, valid size settings, and successful filesystem operations. The status includes context values in some message paths; preserve the underlying error because the visible NTSTATUS alone does not identify whether space, path, permissions, or storage health caused the failure.
A missing paging file reduces the system commit limit and can also prevent the configured crash-dump type. Check boot and system event logs before editing settings. Do not place the only required dump page file on storage that is unavailable during a kernel crash.
What to inspect
- Record the configured path, initial and maximum size, volume free space, and underlying creation error.
- Check filesystem and storage events for the target volume during boot.
- Recalculate commit and crash-dump capacity after the failed page file is excluded.
References
- Microsoft: Introduction to the page file
- Microsoft: Complete memory dump requirements
- Microsoft: Page-file growth and allocation failures
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.