IRP memory leak in nonpaged area.

NTDEV
1

I am following a memory leak in non paged area on some W2K servers.
I have enabled pool tagging and have taked a look with poolmon and memtriage but the only thing that is requesting excesive non paged memory is IRP. Something like this NT issue - http://support.microsoft.com/kb/171180.
My assumption is that this is a bug in the W2K OS but I need some expert advice on how to approach this issue.

TIA

2

If you have any out of box drivers (i.e. unsigned drivers that did not come
with the OS release), turn on driver verifier for these as see what it
reports. This is probably not a W2K bug, but a bug in a driver that
allocated but did not correctly free IRP’s. Some of the popular anti-virus
software could mess things up this way a few years ago.

–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
Remove StopSpam to reply

wrote in message news:xxxxx@ntdev…
>I am following a memory leak in non paged area on some W2K servers.
> I have enabled pool tagging and have taked a look with poolmon and
> memtriage but the only thing that is requesting excesive non paged memory
> is IRP. Something like this NT issue -
> http://support.microsoft.com/kb/171180.
> My assumption is that this is a bug in the W2K OS but I need some expert
> advice on how to approach this issue.
>
> TIA
>

3

Driver Verifier was on my list but unfortunatelly I’m not a developer and I will ned some help in what exactly to monitor with driver verifier. First I was thinking of Pool Tracking - but probably this will show only the requests for non paged memory.
Can anyone tell me what exactly do I need to monitor with Driver Verifier so that I can advance with this?