| Previous | Next |
| STATUS_CACHE_PAGE_LOCKED | STATUS_BUFFER_ALL_ZEROS |
STATUS_CRASH_DUMP
A paging file contains a captured kernel crash image
During a bug check, Windows may write dump data through the boot-volume paging-file mechanism and later convert or copy it to the configured dump file. This informational result marks the presence of that crash data; it is not itself the original bug-check cause.
Preserve the paging file and boot sequence until dump extraction completes. Reconfiguring, deleting, or encrypting the relevant storage too early can lose the evidence. The required page-file size depends on the chosen dump type, and complete dumps have stricter capacity requirements than small dumps.
What to inspect
- Check CrashControl configuration, dump type, destination, and extraction events.
- Verify the boot-volume page file or dedicated dump file met the required size at the crash.
- Analyze the resulting dump for the original bug check instead of treating this status as the fault.
References
- Microsoft: Complete memory dump requirements
- Microsoft: Active memory dumps and page states
- Microsoft: Introduction to the page file
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.