Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Possible Duplicate:
In winxp, I have 4GB of RAM, am using 1.77GB, but programs keep paging out to memory. Why?

I'm sitting at my computer right now with a couple of applications open. I have several hundred megs of RAM free and I recently rebooted. Even so, many applications are continuously writing to the page file (at least, the "page fault" counter keeps increasing in Task Manager).

Why do applications write to the page file when there's plenty of available memory?

share|improve this question

marked as duplicate by ChrisF, random Jul 18 '10 at 1:48

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

Long story short: If Windows doesn't need instant access to anything, it will usually cache it on the pagefile - making more RAM free for the user, and not filling it with useless crap (e.g. Vista). – Breakthrough Sep 24 '09 at 11:39
up vote 1 down vote accepted

You should read Mark's excellent writing on Paging at
Pushing the Limits of Windows: Virtual Memory and related posts.
Very shortly: the pagefile system is not used as an overflow space for your RAM.

share|improve this answer

Think of the page file as a memory "helper". It's job is to support memory allocation by acting as a cache. Often times, the page file stores stuff that USED to be in memory and is only there for reference purposes / easy access.

The types of apps you have running and how they go about allocating memory and loading/unloading things also has bearing on how the page file gets used.

Also check out some interesting discussion on page files on one of Jeff's old posts:

Running XP with the pagefile disabled

share|improve this answer

From Page fault in wikipedia:

Hardware generates a page fault for page accesses where:

  • the page corresponding to the requested address is not loaded in memory.
  • the page corresponding to the memory address accessed is loaded, but its present status is not updated in hardware.

This means that one of the applications is busily loading data or code into memory through reference, as distinct from I/O disk operations.

Since you have oodles of free memory, this can't be program/data swap-in or out to the pagefile.

The only other explanation I can think of is that some program has created a Memory-mapped file and is now processing it. This operation maps a memory portion equal in size to the file, although the file stays on the disk until the program refers to this "memory" through a pointer.

Question: which program in task manager is generating all these page faults?

share|improve this answer

There are several misconceptions here, primarily due to inconsistent and misleading labels in Task Manager.

  1. Most of the memory labeled as "Available" in Task Manager is actually in use. You don't have nearly as much free memory as you think.
  2. What is labeled as "PF Usage" is NOT actual pagefile usage. It is really the commit charge. Actual pagefile usage will typically be much lower.
  3. Since the pagefile is used only to store rarely-used data the actual amount means little to performance.
  4. Paging is not exclusive to the pagefile. In most cases it will only be about 10%.

Interpreting Task Manager is not as simple as most people think. If you see something that appears to be make no sense you are probably misinterpreting it.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged .