Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

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

I am running Windows 7 with 32GB of RAM and have disabled my PageFile.

However, in Resource Monitor, the Memory tab is still showing values for Hard Faults/sec. I've read that this metric should display how many times per second a program is being read out of the PageFile on disk.

Given that I have mine disabled (and have rebooted), why am I still seeing non-zero values for this metric? Also, might this graph include Soft Faults too?

Screenshot of zero page file and still seeing hard faults / sec

share|improve this question
Why do you have pagefile disabled? – Frank Jan 22 '14 at 20:52
I have 32GB of physical RAM installed and my hard drive is as slow as molasses after a cold winter's day in Wisconsin. I'd rather take my system down if I push past 32GB than make it become unresponsive. In other words, personal preference :P – Jesan Fafon Jan 22 '14 at 20:54
It could count new allocations as a hard fault but I don't know for sure. Can you run perfmon and create a trace that contains all of the possible memory traces and post that? – Scott Chamberlain Jan 23 '14 at 0:44
pagefault has nothing to do with pagefile. It means the system needs data that it must read from disk because the data are not already in the RAM. – magicandre1981 Jan 23 '14 at 5:15
Jason: You don't understand virtual memory. – Jamie Hanrahan Dec 11 '14 at 12:13
up vote 4 down vote accepted

I've read that this metric should display how many times per second a program is being read out of the PageFile on disk.

Then you've clearly read some bogus rubbish. It's quite wrong to think that in a demand-paged operating system the only possible backing store for memory pages is the system page file. Program image files containing the code and (read-only/untainted) data for running programs are another possibility. Then there are explicitly memory mapped files.

Further reading

share|improve this answer
This is correct. And that article you linked is a very good primer on the subject. I usually refer people to it too. – Tonny Jan 23 '14 at 22:14
So Hard Faults apply to more than disk reads? I was under the understanding that Microsoft made a specific disambiguation between Page Faults and Hard Faults where the Hard in Hard Faults is the same hard in hard drive. Also, of course I don't think the only backing store is the page file. I think it is virtual memory and I was under the understanding that the Hard Faults metric ignored "non-slow" PageFault (virtual memory) locations. – Jesan Fafon Jan 23 '14 at 23:19
I do wonder where on Earth you are reading all of this bogus rubbish. You need to find, or if one doesn't exist add, a "What is meant by 'Hard Faults' in Windows' Resource Monitor?" question. Because almost none of what you just wrote was right. – JdeBP Jan 24 '14 at 0:19

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.