Memory guide

RAM and Page File Optimization Without Memory-Cleaner Myths

Understand cached, committed and compressed memory before changing the Windows page file.

“Used” memory is often useful

Windows uses free RAM for file cache and can reclaim it when applications need space. Task Manager’s Available value includes immediately reusable standby memory. A memory-cleaner app that empties cache makes the graph look empty but may slow the next application launch or asset load.

Read the important numbers

In Task Manager → Performance → Memory, compare In use, Available and Committed. Committed memory is virtual memory promised to processes and backed by RAM or page files. If the commit charge approaches the limit, applications can fail even when a simplified “RAM use” percentage looks acceptable.

RAMMap can break use into processes, mapped files, kernel pools, drivers and standby lists. Process Explorer can identify a process whose private bytes or handle count grows continuously. Restarting the leaking app is a workaround; updating or replacing it is the fix.

Leave the page file system-managed

For most PCs, Automatically manage paging file size for all drives is the safest setting. Windows can grow it for workload needs and crash dumps. Disabling it does not force all work to become faster RAM; it reduces the commit limit and can cause game, creative-app or crash-dump failures.

A fixed size can be justified for a measured, specialized workload or storage policy, but it should be based on peak commit and dump requirements, not “1.5× RAM” folklore. Keep a page file on a reliable SSD.

When more RAM helps

Upgrade when normal workloads approach the commit limit, applications are repeatedly trimmed, hard faults coincide with stutter, or you cannot keep the working set resident. Match supported capacity and configuration. Two correctly placed modules can provide the intended memory channels, while four high-speed DIMMs may be harder on the memory controller.

Validate memory stability

If crashes, decompression errors or corrupted downloads appear after enabling XMP/EXPO, return memory to default and retest. Use Windows Memory Diagnostic for a quick check and a bootable test such as MemTest86 for deeper validation. One repeatable error is not acceptable.

Verification

Primary sources & further reading

  1. Microsoft Sysinternals: RAMMap
  2. Microsoft: Introduction to the page file

Source pages can change after this guide’s verification date. Check release notes before a high-risk change.

Ready to tune?

Take the safe path in order.

Your checklist saves progress in this browser—no account required.

Open checklist