Re: how to interpret poolmon output, 'Proc' tag.

Hi Roland,

I haven't been getting my notifications from this thread, so I hadn't
realized you had responded.

Your problem is definitely very very similar to mine.

I indeed also have a leak associated to the 'Toke' tag in the paged pool.
And I also see that the leak gets worse evertime i run a new process.

I can't say for sure when my problem started because unfortunately I was
forced to reformat/reinstall my compuer end-of-march because of hard drive
failure. My problems started happening right after I reinstalled everything.

I do also have an ATI card (Radeon 1650x series to be exact), and I probably
ended up installing a newer driver version as I result of the reinstall, but
I can't find any specific info that points towards that being the problem.

I have tried uninstalling my anti-virus recently based on some
recommendations I found on the web, but that was not it.

So I am still looking at this problem once in a while, hoping that I
magically stumble on the right solution. In the meantime, I monitor my memory
and reboot my computer regularly.

If there is any info I can provide that will help, let me know.

Sam

"levitation" wrote:



In case there are any MS or ATI or other company's driver developers.
8-) Please note.
The size of the leak is for every new process 664 bytes. I tried it
repeatedly on different days with starting notepad.exe and cmd.exe
applications. So whoever is behind this leak, You may well easily
check out the following: which of your drivers monitors for new
processes and has some data structures of 664 bytes?


On Apr 24, 1:28 am, levitation <roland.pihla...@xxxxxxxxx> wrote:
three bits of information.
1a) You might get temporary remedy by increasing the nonpaged pool
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
\Memory Management
by changing the value of NonPagedPoolSize. But as far as I understand,
the minimum nonpaged pool size is actually 128MB. When you increase
this parameter, the maximum reserved area for nonpaged pool will
increase a bit too. How the numbers are related, I do not know. It is
possible to monitor the sizes of reserved nonpaged and paged pool
areas with Process Explorer, when debug symbols are installed, under
System Information menu item.
1b) In my case there is also leak under pagedpool, under pool tag
"Toke", which means "Token objects". So You may need to increase the
maximum of paged pool too, in case it gets depleted too. I wont
describe the registry changes here much longer unless You ask for it.
There are other issues that need to be taken account when changing
these parameters. For example "System Page Table Entries" may become
low, but it is possible to monitor it with performance.msc and if
neccessary it is possible to find new reasonable configuration.
2. What was recently changed in my computer, is the following: 1)
installed newest ATI video card driver, 2) installed RATT and
kernrate, 3) installed some usual MS hotfixes. But my previous last
reboot was a month ago, so there might have been more changes during
that month; changes that I am not aware of right now. Anyway, before
my previous last reboot this problem did not occur, its a very recent
development which has been manifesting since reboot on last weekend.
3) PID-s may seometimes be large. When they do, they start being
systematically large, not only few of them. I have seen it too. It
seems to occur seldom, but randomly, even when no other bad things are
manifesting. Still there may be some relation, because right now my
PID numbers are in 100'000-s too.



ama...@xxxxxxxxx wrote:
On 21 abr, 20:52, levitation <roland.pihla...@xxxxxxxxx> wrote:
One more thing. It might help you if you disable any scheduled or
otherwise reoccuring tasks.
The Proc tag leaks at least in my case always when a new process
starts (it does not restore itself after closing the process). For
usual daily activities with a few programs, its so small that you wont
notice. But when some process starts and stops repeatedly in a
scheduled manner, this leak accumulates faster.

I'm having the same problem, we run 4 processes through our
application task scheduler every 10 second and i see a kernel memory
leak caused by the Proc tag pool, forcing to reboot the server every 2
days.
Another weird thing is the process identifier PID in the task manager
for new processes, the number is around 250.000 and growing- Hide quoted text -

- Show quoted text -


.

Relevant Pages

  • Re: how to interpret poolmon output, Proc tag.
    ... In case there are any MS or ATI or other company's driver developers. ... The size of the leak is for every new process 664 bytes. ... the minimum nonpaged pool size is actually 128MB. ...
    (microsoft.public.windowsxp.general)
  • Re: how to interpret poolmon output, Proc tag.
    ... the minimum nonpaged pool size is actually 128MB. ... my previous last reboot this problem did not occur, ... Another weird thing is the process identifier PID in the task manager ...
    (microsoft.public.windowsxp.general)
  • Re: system lacked sufficient buffer space or because a queue was f
    ... I rebooted the server now and will observe the NP Pool over the coming days. ... You could check in task manager for a memory or *file handle* leak. ... anymore and is resolved by doing a reboot. ...
    (microsoft.public.windows.server.general)
  • Re: Pool leak Episode II
    ... The water sits at the level of the skimmer ... That makes the likelihood of a skimmer pipe leak very high. ... So, if you can't find anything at a pool maintenance place, expand your ...
    (alt.home.repair)
  • Pool leak Episode II
    ... I have previously posted about a possible pool leak, ... if I fill up a few inches, the water will slowing drop to the skimmer lip ... I hired a pool leak detection expert to investigate. ... reinforced concrete slab with a footing on each end. ...
    (alt.home.repair)