<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#004006" bgcolor="#ffff80">
<p><font face="Comic Sans MS">Hi Dick</font></p>
<p><font face="Comic Sans MS">The source of your page fault storm is
probably some combination of an insufficient amount of RAM and
poorly chosen virtual memory parameters. </font><font
face="Comic Sans MS"><font face="Comic Sans MS">4GB sounds like
a lot of RAM, but it really isn't. </font>I don't know that
or even if win10 includes the capability of changing your
virtual memory parameters. Perhaps someone with better knowledge
of win10 internals can comment on that. <br>
</font></p>
<p><font face="Comic Sans MS">The "brute force" method of dealing
with an excessive number of page faults (which you appear to
have) is to simply increase the amount of RAM in your computer.
That mean$ $ome new hardware. In my experience, hardware (and
management) folk often claim that, "memory is cheap." You may be
about to learn exactly how cheap it is. <br>
</font></p>
<font face="Comic Sans MS">Most win10 systems on the market these
days come with at least 8GB of RAM. Personally, I try to max out
the RAM on my systems so that I can avoid the page fault storm
problem. These days that seems to be 16 GB but I will not be
surprised if that eventually turns out to be inadequate. It
shouldn't be, but over time that is the trend. </font><br>
<p><font face="Comic Sans MS">Another hardware approach is to
replace your hard disk with a solid state disk. That doesn't
really change anything in terms of page faults, but it does
remove delays due to the disk's rotational latency. If your disk
controller supports it, you may also get increased bandwidth.
Perhaps just speeding up the disk will make the page fault storm
tolerable.<br>
</font></p>
<p><font face="Comic Sans MS">If you want a cheaper, software based
fix, look at what programs are trying to run on your system and
get rid of anything you don't really need. The decision of what
to get rid of is <i><b>tricky</b></i>, so it's important to
know what it is you are killing off. That means knowing what it
is and what it's trying to do for (or to) you before you get rid
of it. Simply killing off anything you don't recognize or don't
understand is <i>NOT</i> a good approach. That will eventually
lead you to having to reinstall everything or possibly have to
go out and buy a new computer!</font></p>
<p><font face="Comic Sans MS">Good luck!</font></p>
<p><font face="Comic Sans MS">73 de Glenn</font><br>
</p>
<div class="moz-cite-prefix">On 5/25/2020 9:16 PM, Dick Bingham
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAMX=kLm-cgbVHkf4+qZQ9n6Vz3NrTOnL3NTwrSJvSae4VFKxjw@mail.gmail.com"><br>
<div dir="ltr">
<div>
<div class="gmail_default" style="font-size:large">
<div><br>
</div>
<div>I have close to 4GB of memory and as time progresses
"Leakage" or whatever is consuming</div>
<div>available memory to the point my computer will not
allow <b>Task Manager to start </b>due to </div>
<div>'insufficient resources'. At this point I have to shut
down the computer and restart it to have</div>
<div>a functioning machine.</div>
<br>
</div>
</div>
</div>
</blockquote>
<pre class="moz-signature" cols="72">--
Here is Schrodinger's Epistemic Virus.
We don't know that we have it because we can't be tested.
We don't want to spread it, so we act as if we have it.
We don't want to catch it, because we have no justification to believe we're immune.
Thus, we have the virus
...and at the same time don't have the virus
...and also reserve judgement on the matter.
Hence Schrodinger's Epistemic Virus.</pre>
</body>
</html>