Best Pagefile Settings for Gaming on Nvme Ssd: Best Settings and Config (2026) (2026)

In the era of modern PC gaming, virtual memory optimization remains one of the most misunderstood aspects of system tuning. With the widespread adoption of high-speed PCIe Gen 4 and Gen 5 NVMe solid-state drives, old advice regarding the Windows pagefile (pagefile.sys) is obsolete. Many legacy optimization guides recommend disabling the pagefile entirely if you have 16GB or 32GB of system RAM, claiming it reduces SSD wear and forces Windows to use your faster physical memory. This is a critical mistake that leads to instability, micro-stutters, and hard crashes to desktop in modern, asset-heavy titles.

To optimize your system for gaming, you must prioritize stability, consistent frame times (specifically 1% and 0.1% lows), and the prevention of “Out of Memory” (OOM) crashes. As we push into 2026, modern game engines like Unreal Engine 5 rely heavily on virtual memory allocation to pre-cache high-resolution textures, compile shaders, and manage VRAM spillover. When your GPU run out of dedicated video memory, the DirectX and Vulkan runtimes allocate system memory as a backup. If your system RAM is also highly utilized, Windows must have a robust, fast pagefile configured on your primary NVMe drive to prevent the system commit limit from being breached.

This guide details the exact configurations needed to maximize gaming performance and drive longevity using your NVMe SSD. We will bypass the myths and focus on the architectural realities of the Windows memory manager.

Quick Recommended Settings

For those looking for immediate configuration values, the table below outlines the optimal pagefile settings based on your installed physical RAM and storage configuration. All values are calculated in Megabytes (MB), where 1 GB equals 1024 MB.

Setting-by-Setting

To configure these settings, you must navigate to the Advanced System Settings menu in Windows. Use the following precise path:

1. Press Windows Key + R to open the Run dialog box.
2. Type sysdm.cpl and press Enter to open the System Properties window.
3. Click on the Advanced tab.
4. Under the Performance section, click the Settings… button.
5. In the Performance Options window, switch to the Advanced tab.
6. Under the Virtual memory section, click the Change… button.
7. Uncheck the box at the top that reads “Automatically manage paging file size for all drives” to unlock manual configuration.

Drive Selection

Exact Value: Primary NVMe SSD partition (typically C:).

The Trade-off: Setting the pagefile exclusively on your fastest NVMe SSD ensures that when Windows is forced to read or write to virtual memory (known as a page fault), the latency is kept to an absolute minimum. The trade-off is a minor consumption of your drive’s overall capacity and a negligible increase in total bytes written (TBW). You must disable pagefiles on secondary mechanical hard drives (HDDs) or older, slower SATA SSDs, as a page fault on a slow drive will freeze your game engine for several frames, causing severe micro-stutters.

Paging File Size Mode (Custom Size vs. System Managed)

Exact Value: Custom Size.

The Trade-off: A “System Managed” pagefile dynamically shrinks and grows based on OS demand. The trade-off of using System Managed is that when a game demands a sudden surge in virtual memory, the Windows kernel must pause thread execution slightly to expand the size of pagefile.sys on the storage controller. This allocation overhead causes sudden, unpredictable frame-time spikes during gameplay. Selecting “Custom Size” and defining static boundaries prevents Windows from constantly resizing the file, keeping your frame delivery smooth.

Initial Size (MB)

Exact Value: 4096 MB (for 32GB/64GB RAM) or 8192 MB (for 16GB RAM).

The Trade-off: The Initial Size is the amount of storage permanently reserved on your NVMe SSD for virtual memory from the moment Windows boots. Setting this to a baseline of at least 4096 MB ensures that the operating system has an immediate, contiguous block of storage allocated for basic background processes and crash dump logging. The trade-off is that this storage space is permanently locked and cannot be used for storing games or other files, even if your physical RAM utilization is low.

Maximum Size (MB)

Exact Value: 16384 MB (for 32GB RAM) or 24576 MB (for 16GB RAM).

The Trade-off: The Maximum Size acts as a hard ceiling for system commit charge expansion. If a poorly optimized game suffers from a memory leak, the pagefile can expand up to this limit to prevent an immediate crash, giving you time to save your progress or finish a match. The trade-off is that if the game does hit this ceiling, system performance will degrade as it heavily utilizes the SSD’s flash controller, though this is still preferable to an instantaneous crash to desktop.

By Hardware Tier

Low-Tier Hardware (8GB to 16GB RAM / Mid-Range NVMe SSD)

If your gaming PC is running on 16GB of system RAM or less, your pagefile settings are critical to system survival. Modern games regularly exceed 12GB of physical memory usage on their own, leaving almost nothing for Windows background services, Discord, or web browsers. In this tier, your NVMe SSD will be actively used as an extension of your RAM.

• Initial Size: 8192 MB
• Maximum Size: 24576 MB

This configuration ensures that your system commit limit is high enough to absorb both heavy gaming loads and background multitasking. Because low-tier systems are highly susceptible to running out of physical memory, allocating up to 24GB of maximum virtual memory space prevents memory allocation failures that force modern games to close abruptly.

Mid-Tier Hardware (32GB RAM / High-Performance Gen 4 NVMe SSD)

This is the standard configuration for modern PC gaming. With 32GB of physical memory, your system rarely runs out of actual RAM, but Windows still requires a pagefile to optimize memory pages. Windows will move idle background processes (like your game launcher, anti-cheat services, and explorer.exe) out of physical RAM and into the pagefile while you play, freeing up the fastest physical silicon for the active game engine.

• Initial Size: 4096 MB
• Maximum Size: 16384 MB

This strikes the perfect balance between storage conservation and performance safety. It prevents dynamic resizing stutters while ensuring that if a game’s VRAM requirements spill over into system memory, there is ample commit space to handle the overflow on your high-speed NVMe drive.

High-Tier Hardware (64GB+ RAM / Premium PCIe Gen 5 NVMe SSD)

High-end enthusiasts with 64GB or more of DDR5 RAM might assume they do not need a pagefile at all. However, many game engines and anti-cheat systems utilize legacy APIs that directly query the Windows pagefile system. Disabling it or setting it too low can cause these engines to fail initialization checks or crash during level loading screens.

• Initial Size: 4096 MB
• Maximum Size: 8192 MB

With 64GB of RAM, you do not need a massive swap space. A fixed, smaller pagefile of 4GB to 8GB satisfies all software queries and allows Windows to write a complete kernel memory dump in the event of a hardware Blue Screen of Death (BSOD), without unnecessarily consuming space on your expensive Gen 5 SSD.

Common Mistakes

Disabling the Pagefile Entirely

What causes it: Users read outdated optimization guides claiming that disabling the pagefile forces Windows to run entirely in physical RAM, theoretically increasing performance and preserving SSD write life.

How to check: Open the Virtual Memory configuration menu (via sysdm.cpl). If “No paging file” is selected for all drives, your pagefile is disabled.

What to do: Select your primary NVMe drive (usually C:), choose “Custom size” or “System managed size,” enter the appropriate values for your RAM tier, and click the Set button. Click OK and restart your PC.

How to undo: Go back to the Virtual Memory menu, select “No paging file,” click Set, and restart. (Note: We do not recommend undoing this, as disabling the pagefile will cause immediate crash-to-desktop behavior in modern titles).

Placing Pagefiles on Multiple Drives (or Slower HDDs)

What causes it: Windows default settings sometimes automatically allocate a pagefile on every connected storage drive, including old secondary SATA SSDs or mechanical storage drives used for backup archiving.

How to check: Look at the drive list in the Virtual Memory dialog box. If you see “System Managed” or a size value listed next to your D:, E:, or other secondary slow drives, Windows is actively using them for paging.

What to do: Click on each non-NVMe drive in the list, select the No paging file radio button, and click Set. Ensure only your fastest NVMe SSD is set to “Custom Size” or “System managed.” Click OK and restart.

How to undo: Select the secondary drive in the list, choose “System managed size,” and click Set.

FAQ

Does a pagefile on an NVMe SSD reduce its lifespan?

No, not in any meaningful way. Modern NVMe SSDs utilize advanced TLC (Triple-Level Cell) or QLC (Quad-Level Cell) NAND flash paired with wear-leveling algorithms managed by the drive’s onboard controller. These drives are rated for hundreds of Terabytes Written (TBW). Even under heavy gaming and multitasking, Windows pagefile writes represent a fraction of a percent of your drive’s daily write endurance. Your SSD will become technologically obsolete long before pagefile writes degrade its silicon health.

Should I set the Initial and Maximum size to the exact same value?

While some legacy guides suggest setting the Initial and Maximum sizes to identical values (e.g., 16384 MB for both) to prevent file fragmentation, this is unnecessary on NVMe drives. Fragmentation is a mechanical drive issue; solid-state drives read fragmented blocks with virtually zero latency penalty because there is no physical read head to move. Setting a lower initial size and a higher maximum size allows you to save valuable SSD storage space during normal desktop use, while still providing a safety buffer that can expand dynamically if a game experiences a memory leak.

Why does my game crash with “Out of Memory” when I have 32GB of RAM and no pagefile?

This occurs because of how the Windows Operating System manages “Commit Charge.” When a game requests memory, it asks the OS to reserve a specific amount of virtual space (committed memory). Windows will only grant this reservation if the total requested size is less than the physical RAM plus the size of your pagefile (the Commit Limit). If you have 32GB of RAM and no pagefile, your commit limit is exactly 32GB. If your game, background applications, and GPU drivers request 33GB of virtual space, Windows must deny the request, leading to an immediate crash, even if your actual physical RAM usage is only sitting at 24GB.

Does moving the pagefile to a non-system NVMe drive improve gaming performance?

If you have two physical NVMe SSDs (for example, a primary C: drive for OS and a secondary D: drive for games), placing the pagefile on the secondary drive can theoretically reduce bus saturation. However, in practice, the performance difference is imperceptible on modern PCIe Gen 4 or Gen 5 interfaces, which feature massive bandwidth pipelines. The best practice is to keep the pagefile on your primary OS drive (C:) to ensure that Windows can successfully write memory dumps during system crashes, which is a feature that often fails if the pagefile is located on a secondary storage controller.