Memory management
The Windows page file
Why disabling it causes crashes, and what it is actually for
Last updated
Should you disable the page file if you have enough RAM?
The page file is not a slower substitute for RAM that Windows falls back on when memory runs out. It is part of how the memory manager commits memory, and applications routinely reserve far more commit than they ever touch. Disabling it makes commit limit equal to physical RAM, and applications that reserve generously will fail -- sometimes as an out-of-memory error, sometimes as a crash.
Registry location and values
Paging file size
- Location
System Properties → Advanced → Performance → Advanced → Virtual memory- Value name
Paging file size- Type
System setting- Default
- System managed
| Value | What it does |
|---|---|
System managed | Windows sizes it dynamically. The correct choice for almost everyone. |
None | No page file. Commit limit becomes physical RAM. |
What Windows actually does with this
Windows tracks committed memory, which is memory that has been promised to processes whether or not it has been written to. The commit limit is physical RAM plus page file size. An application that reserves a large region and touches a fraction of it consumes commit against that limit. The page file also backs the memory dump written when the system crashes.
What it affects
Whether memory-hungry applications can start and run. Whether crash dumps can be written at all.
Is it worth changing?
Do not disable it, regardless of how much RAM you have. This is the tweak on this list with the clearest failure mode: games and creative applications that reserve large address ranges will fail on a machine with no page file even when Task Manager shows gigabytes free, because the constraint is commit, not usage. If you want to reduce disk use, set a modest fixed size rather than disabling it. If you want stability, leave it system managed.
What can go wrong
Application crashes and out-of-memory failures on a machine that appears to have free memory. Loss of crash dumps, which makes diagnosing anything else considerably harder.
How to undo it
System Properties → Advanced → Performance Settings → Advanced → Virtual memory → Change → tick Automatically manage, then restart.
Create a System Restore Point before editing the registry. Every setting on this page is reversible, but a restore point is the difference between undoing one change and reinstalling Windows.
Which Windows versions this applies to
All modern Windows versions.
The Windows page file: common questions
I have 32GB and I never use more than 12GB. Why do I need one?
Because the limit that matters is committed memory, not memory in use. Applications reserve address space they never touch, and that reservation counts against the commit limit. Removing the page file removes headroom you are using without seeing.
Does the page file slow gaming down?
No. Pages that are actively used stay in RAM. The page file backs commit and holds pages that are not being touched.
Sources
Does JINSHI Tweaks change this?
This page documents a setting that corresponds to the following toggle in JINSHI PC Tweaks: Disable Page File.
The reference above is written to be usable without the product. Everything here can be applied by hand for free. What the application adds is that the change is applied in one pass, a System Restore Point is created first, and each toggle can be reversed individually.