Article ID: 262539 - View products that this article applies to.
This article was previously published under Q262539
This article has been archived. It is offered "as is" and will no longer be updated.
You might observe a memory leak in Lsass.exe private bytes with the System Monitor tool.
This behavior can occur if the built-in groups (such as the Administrators or Account Operators groups) have very many members. To verify this, use the information in the following Microsoft Knowledge Base article to create a log with System Monitor:
248345The leak occurs in the Private Bytes counter for the Lsass process. You can also use the information in the following Microsoft Knowledge Base article and Umdh.exe to verify that the function that is not freeing memory is in Samsrv.dll:
(http://support.microsoft.com/kb/248345/EN-US/ )How to Create a Log Using System Monitor in Windows 2000
(http://support.microsoft.com/kb/268343/EN-US/ )Umdhtools.exe: How to Use Umdh.exe to Find Memory Leaks
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:
260910The English version of this fix should have the following file attributes or later:
(http://support.microsoft.com/kb/260910/EN-US/ )How to Obtain the Latest Windows 2000 Service Pack
Date Time Version Size File name ----------------------------------------------------- 5/10/00 3:41:20 5.00.2195.2092 370,448 Samsrv.dll 4/17/00 9:52:16 5.00.2195.2042 903,952 Ntdsa.dll
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.
For additional information about how to install Windows 2000 and Windows 2000 hotfixes at the same time, click the article number below to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/249149/EN-US/ )Installing Microsoft Windows 2000 and Windows 2000 Hotfixes