What is Performance Monitor telling me when my page faults / second are high? (4 Solutions!!)

What is Performance Monitor telling me when my page faults / second are high?

The Question: I have a Windows 7 64-bit computer that is having performance issues. After
some investigation, I have discovered that the page faults / second on it - as
reported by Performance Monitor - are really high.
Everything else seems to be normal. Resource Monitor reports no hard faults and
lots of available memory.
Is this a potential cause for problems, or is it a red herring? If it is
something that could be causing problems, what should I do next to figure out
what is causing it?
Here is a screenshot of the Performance Monitor. Notice that the average page
faults / second is 75,887. On another computer that does not have problems,
this number is closer to 3,000.
[Performance Monitor--Page Faults / Second = 75,000!]
Here is a screenshot of the Resource Monitor, sorted by hard faults / second,
which is currently 0 for all processes.
[Resource Monitor--Hard Faults / Second = 0]

Solutions: Please watch the whole video to see all solutions, in order of how many people found them helpful

== This solution helped 3 people ==
A hard page fault is when the memory manager finds that the block of memory its
needs is not in RAM. That memory has been swapped out to disk, and your system
slows down because it takes more time to get it from there. Add more memory to
your system to reduce the number of page faults and improve performance.

== This solution helped 12 people ==
to check how many page faults are being generated,
this way you can identify the program that is causing the problem and
troubleshoot more specific.

----
Performance Monitor: Average page faults / second:
This counter gives a general idea of how many times information being
requested is not where the application (and VMM) expects it to be.
The information must either be retrieved from another location in
memory or from the pagefile. Recall that while a sustained value may
indicate trouble here, you should be more concerned with hard page
faults that represent actual reads or writes to the disk. Remember
that the disk access is much slower than RAM.

== This solution helped 1 person ==
Here's a table from the Windows Internals book about what's the page fault.
(I've excluded the ones that result in an access violation):
* Reason for Fault - Result
* Accessing a page that isn't resident in memory but is on disk in a page
file or a mapped file - Allocate a physical page, and read the desired
page from disk and into the relevant working set
* Accessing a page that is on the standby or modified list - Transition the
page to the relevant process, session, or system working set
* Accessing a demand-zero page - Add a zero-filled page to the relevant
working set
* Writing to a copy-on-write page - Make process-private (or session-
private) copy of page, and replace original in process or system working
set .
questions/5684365/what-causes-page-faults
there are so many reason to make page fault.