Paged pool leakage: what owns Wdm tag?

[Tom Welsh]

Windows 2000 Pro, SP4. Paged pool is steadily expanding from its
initial value of about 54MB, at a rate of about 5-10MB per day. I have
seen it as high as 150MB after a week or so, but have been rebooting
without waiting for Windows to seize up.

I have been running OSR's PoolTag utility, and the evidence is clear.
A tag called Wdm is steadily accumulating paged pool, and hardly ever
releasing any. Its growth accounts nicely for the overall expansion of
paged pool. So all I need is to find the responsible driver.
Unfortunately, AFAIK there is no easy way of doing this for W2K. But I
realize that WDM is part of Windows that handles some of the work of
device drivers, so if this is what owns the Wdm tag, I am presumably
looking at a Microsoft bug.

Can anyone help? E.g. by telling me anything about the Wdm tag, who
owns it, what sort of events cause pool allocations to be associated
with it, and (ideally) if there is any fix? And if this is not ther
best newsgroup to ask, any suggestions for a better/more specialized
one?

 

[Guest]

WDM stands for win32 driver model. I don't know enough to tell you if the
memory leak is a WDM problem or the problem of an incorrectly written 3rd
party driver that's interfacing with WDM (or maybe just using that tag to
distinguish itself?).

Check out this link though for more info on how to find out what you need (I
think)

http://codeproject.com/system/api_spying_hack.asp

PS - If none of us here are any help maybe try posting your issue here:

http://www.microsoft.com/windowsser...oft.public.win32.programmer.wmi&lang=en&cr=US

***I'm not saying you shouldn't have posted here first, I'm just suggesting
an alternative if we are a bust.

Thanks,

Nick