Memory Page Faults

[William Bunch]

I am getting high memory hard page faults with the following services in
Vista Home Premium.

wlschost.exe 10000 Hard page faults a min
svchost.exe 300 Hard page faults a min
MsMpEng.exe 4056 hard page faults a min

I have 2 Gigs of Dual channel Ultra Memory w/heat spreaders 800MHz DDR2
Core2Quad system

I was wondering while the warranty is still on my RAM if I should return it
or is it something else?

 

[dennis@home]

I am getting high memory hard page faults with the following services in
Vista Home Premium.

wlschost.exe 10000 Hard page faults a min
svchost.exe 300 Hard page faults a min
MsMpEng.exe 4056 hard page faults a min

I have 2 Gigs of Dual channel Ultra Memory w/heat spreaders 800MHz DDR2
Core2Quad system

I was wondering while the warranty is still on my RAM if I should return
it or is it something else?

They are not faults in the hardware.

Page faults are a term used to describe when an OS attempts to read from
memory and finds that "page" is not in real physical RAM, but is stored on
the disk. The page then has to be read from the disk into real physical RAM
so it can be used.

 

[William Bunch]

Quick response thanks, So I need more RAM then I though a lot of page faults
was BAD

 

[Canuck57]

Quick response thanks, So I need more RAM then I though a lot of page
faults was BAD

Page faults (UNIX/Linux or Vista) are not necessarily bad. But it they are
excessive, and you experience performance issues or drive thrashing, time
for more RAM. Also note if you are still using 32 bit versions of Vista,
even if your system can hold more, 3.1 to3.5GB is all you will see.

 

[William Bunch]

My HDD Sata 160 Gig Seagate 7200.10 is always being accessed even when I am
not using it. I assumed this was from all the background crap. Oh BTW the
memory thing was fixed in SP1 for Vista 32 bit Version or so it said anyway

 

[dennis@home]

My HDD Sata 160 Gig Seagate 7200.10 is always being accessed even when I
am not using it. I assumed this was from all the background crap. Oh BTW
the memory thing was fixed in SP1 for Vista 32 bit Version or so it said
anyway

You get page faults whenever a file is accessed on the disk (files are just
mapped to virtual memory these days, virtual memory has to be paged in to be
used and its paging that causes the faults.

wlschost.exe is windows one care.. probably scanning.
MsMpEng.exe is defender.. probably scanning
svchost could be lots of things as its a generic handler.. 300 faults/min is
not high AFAIK.

I doubt if you need more RAM yet..
have you had the system running long enough to index your files? indexing
creates lots of faults for the first day or three.

 

[William Bunch]

Ahh forgot about that indexing thing had the system full running for about a
week or two