Very Slow Paged Pool Leak in Windows NT 4.0

This article was previously published under Q196745
This article has been archived. It is offered "as is" and will no longer be updated.
After a Windows NT server has been running at least a week, the following event may show up in the System event log:
TEXT: The server was unable to allocate from the system paged poolbecause the pool was empty.
Or, by other troubleshooting methods or by using Performance Monitor, you observe that the paged pool memory counter is higher than it has been under previous observations. Observing for several days, you do not observe any real changes but, by observing the system for weeks, the trend is always up.

This leak occurs on servers with many users more than 100 and many groups greater than 10 for each user. It is not related to the relative load on the server.
Under certain conditions, the NetSessionEnum and NetUserGetLocalGroups NET APIs leak memory in both the calling application private bytes and paged pool memory. This leak is very difficult to track down as it is very slow to show up.
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack
Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4 and Windows NT Server 4.0, Terminal Server Edition, Service Pack 4.

Article ID: 196745 - Last Review: 10/11/2013 15:55:14 - Revision: 2.1

Microsoft Windows NT Server 4.0, Terminal Server Edition, Microsoft Windows NT Server 4.0 Standard Edition, Microsoft Windows NT Workstation 4.0 Developer Edition

  • kbnosurvey kbarchive kbfix kbprb KB196745