Windows is a rather stable OS for the most part, but that doesn’t guarantee smooth operation every time you use your computer. As much as Microsoft works on fixing any bugs Windows users might face, there are still hidden bugs and glitches that keep showing up randomly.
In this article, we’re taking a look at the “dump file creation failed due to an error during dump creation” error and giving you a few fixes to solve the problem.
Why does this happen?
While there’s no single cause for this issue, here are a few popular reasons why you might face this problem.
- Intrusive third-party cleanup programs: More often than not, intrusive third-party cleanup programs will delete logs and dump files in order to save space on your PC.
- System files are corrupted: Corrupted system files can cause all sorts of different errors, including randomly deleting log and dump files.
- Outdated or corrupt BIOS: A corrupt BIOS will often cause a number of problems on your PC, including errors like BSODs and this.
Also read: What is $Windows.bt? Can you delete the folder?
How to fix this?
Here are a few solutions for you to try out.
Uninstall recently installed programs
First up, try removing any programs you may have installed recently. Often a program installed with admin privileges can cause conflicts with Windows’ functioning leading to a BSOD or other less severe errors.
Programs like Virtual CloneDrive, CiscoVPN, Xsplit, MSI Live Update, Asus GameFirst Service and even antivirus like McAfee and BitDefender can trigger this error.
Run the Windows Memory Diagnostics tool
If your RAM is seated properly but is failing, it can trigger this error. To check if there’s an issue with your RAM, follow these steps.
Step 1: Press the Windows key and search for Windows Memory Diagnostics. Then, click the corresponding search result.
Step 2: Run the tool and click the Restart now button to check for problems.
If you see some issues, try running the auto-troubleshoot to resolve the error.
Also read: How to make Adobe DC Reader default to scrolling?
Run the Check Disk utility
Corrupt or bad sectors on the storage drive can also cause these issues. Run the Check Disk utility to ensure your storage drive is alright.
You can refer to our detailed guide here on how to run the check disk utility.
Disable automatic restart
Disabling automatic restart on your PC can also help get rid of the problem. Here’s how.
Step 1: Press the Windows key + R to open the Run prompt. Type sysdm.cpl and hit enter.
Step 2: Head over to the Advanced tab and click Settings under Startup and Recovery.
Step 3: Under System failure, uncheck Automatic restart.
Now restart your PC and try again. You should be able to see your log files now.
Run an SFC Scan
Corrupt files are the number one reason your PC might behave weirdly. Here’s how you can get rid of them and potentially resolve your issue.
Step 1: Press Windows Key + S to bring up the Cortana/Search box and search for Powershell. Open Windows Powershell from the search results.
Step 2: Type sfc /scannow to scan your system for issues.
Step 3: If the SFC scan finds any problem, use the following command to resolve them.
DISM /Online /Cleanup-Image /RestoreHealth
Restart your PC, and you should be able to read log files now.
Update your BIOS
Updating your BIOS is also a good idea if you’re running into this error. However, do keep in mind that the process for updating the BIOS differs greatly depending upon the make and model of your PC’s motherboard, so be sure to consult with an expert if you don’t know what you’re doing.
Repair your system
If nothing else works, the best way to get rid of the error is by simply reinstalling or repairing your OS.
The Windows Media Creation tool is a great way to install Windows and repair the OS. Using this, you can perform a clean installation or repair your OS without affecting your data.
You can download the Media Creation Tool here
Also read: What does ‘no dc’ mean? How to fix it?
