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



Hello Samuel.

Please ignore the previous answers, they do not know what they are
talking about.

The owners of pool tags are not visible in task manager.
Currently I'm investigating, how to find the driver/process that
causes the pool with "Proc" tag to increase.
Usually it is simple - every driver has its own set of pool tags, so
you just need to search the drivers folder for corresponding string.
But "Proc" tag belongs to windows itself. So it is obvious that the
culprit is some other software, who just requests windows to reserve
memory under "Proc" pool tag.

I have same problem as you. Did this problem of Yours start just
recently? Did You install any updated drivers recently?

Roland


Pegasus (MVP) wrote:
I would look for two things in the Task Manager:
a) If there was a process called "Proc";
b) Which process keeps increasing its "Memory Usage".

"Samuel Stanojevic" <SamuelStanojevic@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:541A6E6F-5DF9-4BF9-B0CE-E31BC72DFCB6@xxxxxxxxxxxxxxxx
Hi Pegasus,

I assume you mean that I should be looking at the 'NP Pool' column of the
Task Manager and see if any process has a high value. I have tried that,
but
the highest value I've found for any given process is 200 Kb, and the
totals
for all processes do not top the 1 Mb. Meanwhile poolmon is showing that
the
'Proc' tag is leaking in the tens of Megabytes.

Any other suggestions?

Regards,
Sam

"Pegasus (MVP)" wrote:


"Samuel Stanojevic" <Samuel Stanojevic@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
in
message news:83A6F681-2785-4E9E-BAEB-1B3654061BA5@xxxxxxxxxxxxxxxx
Hi,

I'm running Windows XP Professional SP2, up-to-date with Windows
Updates.

I've recently noticed that my non-paged kernel memory is leaking at a
steady
pace of 10Mb+/day. If I don't reboot my machine every few days, it
eventually
and inevitably grinds to a halt, forcing me to reboot it.

By searching on the web, I realized I needed to run poolmon.exe to
debug
the
leak, which I did. The output of poolmon clearly shows that the leaking
tag
is 'Proc'. But what is 'Proc'? I have no idea.

Can someone please explain to me what the 'Proc' tag means, and how I
can
use that information to track down the cause of the leak?

Thanks!
Sam

The Windows Task Manager might tell you.



.

Relevant Pages

  • Re: how to interpret poolmon output, Proc tag.
    ... I'm running Windows XP Professional SP2, ... The output of poolmon clearly shows that the leaking ... But what is 'Proc'? ... Can someone please explain to me what the 'Proc' tag means, ...
    (microsoft.public.windowsxp.general)
  • Re: how to interpret poolmon output, Proc tag.
    ... The Proc tag leaks at least in my case always when a new process ... scheduled manner, this leak accumulates faster. ... Did You install any updated drivers recently? ...
    (microsoft.public.windowsxp.general)
  • Re: Memory Leak pooltag="Ddk", windows xp media center 2004, what driver is this?
    ... Maxim Shatskih, Windows DDK MVP ... has a memory leak that I would like to get fixed, ... determined that something with the pool tag "Ddk" was eating up all the ...
    (microsoft.public.development.device.drivers)
  • Re: WU Error 0x800A138F / 0xC00CE55F on Win XP Pro
    ... Is this Windows XP, 2000, or an XP upgrade from 2000? ... I've tried all the fixes> I could find on usenet / support sites including the FIPS algorithm check,> SSL2/3 enable, cache clearing, XML parser reinstall... ... The SOAP request contains information> about my client system and a > tag with a procedurename "Providers" specified. ... The SOAP POST data> are very similar to those of the first request, except this tiem the > tag contains a list of parentItems. ...
    (microsoft.public.windowsupdate)
  • Re: Shared Memory Modules
    ... >> Unix but not Windows. ... Thanks, Thomas. ... I don't know anything about shared memory) except that even after reading ... If you specify the name of an existing tag, ...
    (comp.lang.python)