How to Create a Pagefile for Memory Dumps Only in Windows 10

To configure a dedicated pagefile for memory dumps in Windows 10, you must keep a small system-managed pagefile on your primary C: drive to prevent instability, while creating a second, larger pagefile on a separate physical drive or partition specifically for crash dumps. This setup ensures that critical diagnostic data is written reliably without exhausting resources on your main operating system volume.

Why You Cannot Disable the System Pagefile

Many users mistakenly believe that disabling the pagefile entirely on the C: drive improves performance or frees up space. This advice is dangerous and often leads to system instability, application crashes, and even Blue Screen of Death (BSOD) errors. Windows requires a minimum amount of virtual memory to manage system resources, handle kernel operations, and allocate memory for drivers. Without a pagefile on the system drive, applications may fail to launch, and the OS itself can become unpredictable. The goal is not to remove the pagefile from your main drive but to offload the heavy lifting of memory dump storage to a different location. Memory dumps are large files generated when the system encounters a fatal error. By directing these specific writes to a secondary drive, you reduce fragmentation and I/O contention on your boot drive, which is crucial for maintaining system responsiveness during troubleshooting. If you are experiencing hardware failures alongside these issues, it is wise to check your storage health first by reviewing How to Fix Hard Drive Issues on Windows 7 and Windows 10.

Step-by-Step Configuration Guide

Follow these steps carefully to set up a dual-pagefile configuration. Ensure you have administrative privileges before proceeding.

1. Open Advanced System Settings: Press Win + R, type sysdm.cpl, and press Enter. Alternatively, search for "Advanced System Settings" in the Start menu.
2. Navigate to Performance Options: In the System Properties window, click the Advanced tab. Under the Performance section, click Settings...
3. Access Virtual Memory Settings: In the Performance Options dialog, select the Advanced tab again. At the bottom, under Virtual memory, click Change...
4. Disable Automatic Management: Uncheck the box that says Automatically manage paging file size for all drives. This allows manual configuration.
5. Configure the C: Drive Pagefile: Select your C: drive (usually labeled C:\). Choose System managed size or manually set a small size (e.g., 512 MB to 1 GB). Click Set. Do not choose "No paging file."
6. Select the Secondary Drive: Choose a different physical drive or a distinct partition that has sufficient free space (at least equal to your installed RAM for full dumps, or smaller for minidumps). Select this drive.
7. Create the Dedicated Dump Pagefile: Choose Custom size. Set the Initial and Maximum size to the same value (e.g., if you have 16 GB RAM, you might set 4096 MB for minidumps or higher for full dumps). Click Set.
8. Apply Changes: Click OK on all open dialogs. You will be prompted to restart your computer for the changes to take effect.

Configuring Crash Dump Settings

Simply having a pagefile on a secondary drive is not enough; you must also tell Windows to write the dump file there. The default behavior often keeps the dump file on the system drive even if the pagefile is elsewhere.

1. Return to sysdm.cpl > Advanced tab > Error Reporting button > Advanced...
2. Under Debugging Information, select Custom.
3. Specify the path where you want the dump file saved. A common convention is to create a folder like D:\CrashDumps on your secondary drive.
4. Click OK and restart your machine.

This separation ensures that when a BSOD occurs, the system writes the diagnostic data to the designated location without competing with system processes on the C: drive. This is particularly useful if you are debugging complex issues such as those caused by third-party drivers or software conflicts, similar to scenarios described in BSOD Kernel Mode Heap Corruption after failure to display.

Troubleshooting and Best Practices

If your system still fails to generate dumps, verify that the secondary drive is accessible at boot time. Network drives or removable USB sticks are not suitable for pagefiles because they may not be initialized early enough in the boot process. Always use internal SATA, NVMe, or properly connected external drives that appear as local volumes. Additionally, monitor the disk usage of both pagefiles. If the secondary drive fills up, the system may struggle to write new dumps. Regularly clean old dump files stored in your custom directory. Keep in mind that improper driver interactions can also cause crashes unrelated to memory management, so always update your chipset and GPU drivers if stability issues persist. For more insights on why emulators or specific apps might trigger these errors, see Android Studio Emulator Causes BSOD.

Frequently Asked Questions

Can I disable the pagefile on C: to save SSD space?

No, disabling the pagefile on your system drive can cause severe instability and application crashes. Windows relies on virtual memory for core operations, and removing it entirely removes a critical safety net for memory allocation. Instead, set it to a small system-managed size.

What size should the secondary pagefile be?

For minidumps, a size of 256 MB to 1 GB is usually sufficient regardless of your total RAM. For full memory dumps, the pagefile should be at least as large as your installed physical RAM. Check your Event Viewer to determine the actual size of previous dumps if unsure.

Does moving the pagefile improve gaming performance?

The impact is negligible for most users. Modern games and Windows efficiently manage memory. While reducing fragmentation on the C: drive might offer minor benefits, the primary advantage of a secondary pagefile is reliable crash dump generation, not general performance enhancement.

Why do I still get BSODs after setting up a dedicated pagefile?

A dedicated pagefile only helps store diagnostic data; it does not prevent the underlying cause of the crash. You must analyze the dump file using tools like WinDbg to identify faulty drivers or hardware issues. Refer to our guide on fixing hard drive issues if storage corruption is suspected.

Is it safe to put the pagefile on a USB drive?

It is generally not recommended. USB drives may not be ready during the early boot phase, leading to system failures. Additionally, USB speeds are slower and less consistent than internal drives, which can delay dump writing and increase the risk of data loss during a crash.