Fix: ERROR_CRASH_DUMP 753 (0x2F1)
Disabling fast startup is the quickest fix
4 min. read
Published on
Read our disclosure page to find out how can you help Windows Report sustain the editorial team. Read more
The ERROR_CRASH_DUMP Windows system error, with code 753 (0x2F1), appears when the OS dump files for the previous crash exist in the paging file. The error message reads, Crash dump exists in paging file.
The Error Crash Dump arises due to corrupted system files, incorrect startup settings, the presence of conflicting apps, and a misconfigured virtual memory (paging file).
Before you start with the solutions, restart the PC, install pending Windows updates, and update all the drivers!
How can I fix ERROR_CRASH_DUMP in Windows?
1. Repair the corrupted system files
- Press Windows + R to open Run, type cmd, and hit Ctrl + Shift + Enter.
- Click Yes in the UAC prompt.
- Paste the following DISM commands individually and hit Enter after each:
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
- Next, run this command for the SFC scan:
sfc /scannow
- Finally, reboot the PC and check for improvements.
Since corrupted system files are the most common reason behind ERROR_CRASH_DUMP in Windows, you must run the DISM (Deployment Image Servicing and Management) and SFC (System File Checker) scans, which will replace all problematic files with their cached copies!
2. Disable fast startup
- Press Windows + S to open Search, type Control Panel in the text field, and click on the relevant result.
- Click on System and Security.
- Click on Change what the power buttons do under Power options.
- Now, click on Change settings that are currently available.
- Untick the checkbox for Turn on fast startup and click on Save changes.
- Restart the computer and check for improvements.
3. Uninstall conflicting applications
- Press Windows + R to open Run, type appwiz.cpl in the text field, and hit Enter.
- Select any conflicting app or one installed around the same time the issue first appeared, and click on Uninstall.
- Follow the on-screen instructions to complete the process and then reboot the PC.
If a quick removal doesn’t fix ERROR_CRASH_DUMP, it’s likely that the app left behind files and Registry entries that are still conflicting with Windows. In this case, using a top-rated software uninstaller will wipe all traces of the removed app.
4. Set virtual memory management to automatic
- Press Windows + S to open Search, type View advanced system settings, and click on the relevant result.
- In the Advanced tab, click on Settings under Performance.
- Go to the Advanced tab, and click on Change under Virtual memory.
- Tick the checkbox for Automatically manage paging file size for all drives and click OK to save the changes.
- Restart the computer for the changes to come into effect.
Since ERROR_CRASH_DUMP 753 (0x2F1) Crash dump exists in paging file is related to virtual memory, letting Windows manage the paging file size will help get rid of the system error.
5. Perform a system restore
- Press Windows + S to open Search, type Create a restore point, and click on the relevant result.
- Click the System Restore button.
- Select the Choose a different restore point option, if available, and click Next.
- Pick the oldest restore point from the list and click Next.
- Verify the restore details, click Finish, and confirm the change.
- Wait for the restore to complete. It will take 15-45 minutes.
A system restore will clear out any misconfigurations on the PC by reverting the recent changes. Just make sure to choose a restore point created before the system error first appeared.
If this, too, fails, the last option is to reinstall Windows. This will certainly fix the ERROR_CRASH_DUMP system error since it arises due to software-based issues.
Before you leave, discover common Windows problems and their expert solutions to fix such errors with ease! Before leaving, why don’t you take a look at our latest article on ERROR_PAGE_FAULT_PAGING_FILE?
For any queries or to share which fix worked for you, drop a comment below.
User forum
0 messages