ThisCalculator

Everyday

Configure Windows 10 for BSOD Dump Files

Updated · Standard formula, shown below

Configure Windows 10 for BSOD Dump Files

To configure Windows 10 to create dump files on a Blue Screen of Death (BSOD), you adjust the startup and recovery settings to choose a dump type and ensure the page file is large enough. The most useful option for troubleshooting is a kernel memory dump, which writes to C:\Windows\MEMORY.DMP by default.

What Dump Files Are and Why They Matter

When Windows crashes with a BSOD, it can save a snapshot of memory at the moment of the crash. This file is called a memory dump (or crash dump). It contains information about which drivers, processes, and kernel components were active, which is essential for diagnosing the root cause. Without a dump file, you only see the stop code on the blue screen, which is often too vague to pinpoint the faulty driver. Analyzing the dump with tools like WinDbg or BlueScreenView can reveal the exact file that caused the crash.

Types of Dump Files in Windows 10

Windows 10 offers several dump types, each with a different size and level of detail:

  • Small memory dump (256 KB): Also called a minidump. Stores the stop code, parameters, loaded driver list, and the processor context. Saved in C:\Windows\Minidump. It is quick to write but lacks full kernel memory.
  • Kernel memory dump: Contains all kernel-mode memory, which is enough to analyze most crashes. Saved to C:\Windows\MEMORY.DMP. Requires a page file large enough (typically 800 MB to 1 GB).
  • Automatic memory dump: The default in Windows 10. Behaves like a kernel dump but can shrink to a smaller size if the page file is too small. It also updates the system to use a small page file for future crashes.
  • Complete memory dump: Contains all physical memory, including user-mode data. Requires a page file at least as large as RAM. Not recommended for most users because of the large size.

How to Enable Dump Files (Step-by-Step)

  1. Press Windows + R, type sysdm.cpl, and press Enter to open System Properties.
  2. Go to the Advanced tab and click Settings under Startup and Recovery.
  3. Under System failure, choose a dump type from the “Write debugging information� dropdown. For most users, Automatic memory dump or Kernel memory dump is best.
  4. Ensure the “Overwrite any existing file� checkbox is checked (it is by default) so new dumps replace old ones.
  5. Click OK and restart the computer if prompted.

After a BSOD, the dump file will be saved to the specified location. You can also verify that the setting is active by checking the registry key HKLM\SYSTEM\CurrentControlSet\Control\CrashControl; the value CrashDumpEnabled should be set to 1 (kernel dump) or 7 (automatic dump).

Page File Requirements

The page file (virtual memory) must be large enough to hold the dump. For kernel and automatic dumps, Windows needs a page file on the boot drive (usually C:) with at least 800 MB free. For a complete memory dump, the page file must be at least as large as your RAM. If the page file is too small, Windows will not be able to write the dump and you will see a message like “The system cannot write to the dump file.� To adjust the page file size:

  1. In System Properties, click Settings under Performance, then go to the Advanced tab.
  2. Under Virtual memory, click Change.
  3. Uncheck “Automatically manage paging file size for all drives.�
  4. Select the boot drive, choose Custom size, and set Initial and Maximum size (e.g., 1024 MB for kernel dumps).
  5. Click Set, then OK, and restart.

Common Problems and Fixes

If you are not getting dump files, check these issues:

  • No page file on boot drive: Ensure the page file is enabled on the system drive.
  • Insufficient disk space: The dump file can be several GB. Free up space on the boot drive.
  • Third-party crash dump tools: Some utilities override Windows settings. Disable them if they interfere.
  • Fast Startup: This can prevent a clean shutdown and sometimes interferes with dump creation. Disable it in Control Panel > Power Options > Choose what the power buttons do.
  • Corrupted system files: Run sfc /scannow and chkdsk /f to repair system files and disk errors.

How to Analyze a Dump File

Once you have a dump file, you can open it with the Windows Debugging Tools (WinDbg) or a simpler tool like BlueScreenView. In WinDbg, load the file and run !analyze -v to get the bugcheck code and the likely culprit driver. For example, a dump might show ntoskrnl.exe as the faulting module, but the real cause could be a third-party driver like nvlddmkm.sys (NVIDIA graphics). The dump will list the loaded drivers and the stack trace, which helps you identify the problem.

Frequently Asked Questions

Where are dump files stored?

By default, kernel and automatic dumps are saved to C:\Windows\MEMORY.DMP, and small memory dumps (minidumps) are saved to C:\Windows\Minidump. You can change the location in the Startup and Recovery settings, but it is usually best to keep the default.

Can I delete dump files?

Yes, dump files are safe to delete. They are only used for debugging. You can delete them manually or use Disk Cleanup to remove system error memory dump files. However, if you are still troubleshooting a recurring BSOD, keep the most recent dump until you have resolved the issue.

Why is my dump file not being created?

The most common reasons are a disabled page file, insufficient disk space, or a setting that was changed by a third-party tool. Check the page file size, free disk space, and the registry key CrashDumpEnabled. Also, ensure that the system is set to write debugging information and that “Overwrite any existing file� is checked.

What is the difference between kernel and minidump?

A minidump is a small file (256 KB) that contains only essential crash information, while a kernel dump contains all kernel-mode memory and is much larger (hundreds of MB). Minidumps are easier to share and analyze quickly, but kernel dumps provide more detail for complex driver issues.

Is it safe to use a complete memory dump?

Complete memory dumps contain all of physical memory, including sensitive user data like passwords or files open in memory. They are safe in the sense that they are only used for debugging, but they create a large file that could be a privacy risk if it falls into the wrong hands. For most users, a kernel or automatic dump is sufficient.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.