This article was previously published under Q262386
This article has been archived. It is offered "as is" and will no longer be updated.
A server that is acting as a master browser (commonly a primary domain controller in Windows NT 4.0) may leak non-paged pool memory.
This problem can occur if there is a string that is associated with Browser Master Announcements that is not being properly freed.
To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
The English version of this fix for Windows 2000 should have the following file attributes or later:
Date Time Size File name Platform ------------------------------------------------------------- 06/13/2000 05:06p 368,976 mrxsmb.sys
Service pack information
To resolve this problem, obtain the latest service pack for Microsoft Windows NT 4.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
152734 How to obtain the latest Windows NT 4.0 service pack
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows 2000 Service Pack 2.
You may be able to view this leak by performing the following steps:
Enable Pool tagging by using the Gflags.exe tool.
View the number of non-paged pool allocation for tag "Strg" by using the Poolsnap.exe tool.
If the leak is occurring, the number for allocations versus free calls continually rises.
Microsoft Windows 2000 Advanced Server, Microsoft Windows 2000 Professional Edition, Microsoft Windows 2000 Server, Microsoft Windows NT Server 4.0 Enterprise Edition, Microsoft Windows NT Server 4.0 Standard Edition, Microsoft Windows NT Workstation 4.0 Developer Edition