B
Brian
Guest
I have an SBS2000 server that pretty much hangs after about 10 days of
running because it runs out of nonpaged pool space. It has been running fine
for about 5 years, and this started perhaps two months back. The first time,
I thought it was just an anomaly, but there has turned out to be a consistent
memory leak. Through PerfMon, I have identified the fact that both the
nonpaged bytes & the handle count steadily rise after a reboot but cannot
easily identify which process is responsible.
All the documentation I have seen seems to require me to have a suspect
process before I can determine whether it is, indeed, the problem. However,
how can I identify the runaway process if I have no idea which one is at
fault?
running because it runs out of nonpaged pool space. It has been running fine
for about 5 years, and this started perhaps two months back. The first time,
I thought it was just an anomaly, but there has turned out to be a consistent
memory leak. Through PerfMon, I have identified the fact that both the
nonpaged bytes & the handle count steadily rise after a reboot but cannot
easily identify which process is responsible.
All the documentation I have seen seems to require me to have a suspect
process before I can determine whether it is, indeed, the problem. However,
how can I identify the runaway process if I have no idea which one is at
fault?