how-to-solve-no-dump-file-after-bsod-windows-10

NO DUMP FILE AFTER BSOD WINDOWS 10

Whenever a Blue Screen of Death (BSOD) happens on a Windows computer and leads it to crash, all the events are written to a dump (DMP) file. These files will be in memory until the computer is restarted. The dump files play a vital role in analyzing the cause of the crash. What if you don’t find the dump file on your computer after a BSOD crash? Something might be misconfigured on your computer then. Refer to the quick steps given on our site to fix this issue no dump file after Bsod Windows 10.

no dump file after Bsod Windows 10

Solution 1: Configuring your Windows 10 computer to create the crash dump files on BSOD

  • Before configuring, create a system restore point to back up all our system data.
  • Click the Start menu and open the Windows Control Panel to fix the issue no dump file after Bsod Windows 10.
  • Click on System and security and give a right-click on the This PC icon.
  • Select the Properties option from the pop-up menu.
  • Navigate to the left-side panel and select Advanced system settings.
  • In the new window, click the Settings button in the Startup and Recovery section.
  • In the Startup and Recovery window, go to the System Failure section.
  • In the Write debugging information column, select Automatic memory dump from the drop-down menu.
  • Click OK and close the window.
  • Restart your Windows computer and check if the problem has been resolved.

Solution 2: Creating dump files using the WMIC command line

  • On your Windows computer, open the Run dialog box by pressing the Windows + R shortcut keys.
  • Type ‘cmd’ in the search panel and hit the Enter key to run the Command Prompt app as an administrator.
  • Alternatively, press the Windows + X shortcut keys to open the quick access menu and click the Command Prompt (Admin) option to launch the Command Prompt app.
  • In the Command Prompt window, type no dumpfile: wmic RECOVEROS set DebugInfoType = 0 and press the Enter key.
  • Once the command has been executed, type the exit command to close the Command Prompt window.
  • Restart your Windows computer and check if the problem has been resolved.
  • If the problem remains unsolved, contact our technical support team for remote assistance to fix the issue no dump file after Bsod Windows 10.