Access Violation in LSASS When There Are Low-Memory Conditions (306483)



The information in this article applies to:

  • Microsoft Windows 2000 Server SP1
  • Microsoft Windows 2000 Server SP2
  • Microsoft Windows 2000 Advanced Server SP1
  • Microsoft Windows 2000 Advanced Server SP2
  • Microsoft Windows 2000 Professional SP1
  • Microsoft Windows 2000 Professional SP2

This article was previously published under Q306483

SYMPTOMS

When you run Active Directory on a Windows 2000 Server-based computer and there is high memory usage (if the commit limit is reached or if LSASS is out of virtual memory), you may receive an LSASS access violation error message.

To verify that this problem is occurring on your computer, confirm the CPU utilization by using Performance Monitor.

CAUSE

This problem occurs because a memory location is freed twice while recovering from the memory allocation not working.

RESOLUTION

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-language version of this fix should have the following file attributes or later:

   Date     Time   Version        Size     File name
   ----------------------------------------------------
   9/10/01  23:12  5.0.2195.4276  355,600  Advapi32.dll
   9/10/01  23:12  5.0.2195.4141  133,904  Dnsapi.dll
   9/10/01  23:12  5.0.2195.3649   90,896  Dnsrslvr.dll
   9/10/01  23:12  5.0.2195.4301  525,072  Instlsa5.dll
   9/10/01  23:12  5.0.2195.4117  143,120  Kdcsvc.dll
   9/07/01  22:03  5.0.2195.4310  199,440  Kerberos.dll
   9/04/01  18:32  5.0.2195.4276   71,024  Ksecdd.sys
   9/07/01  03:31  5.0.2195.4301  507,152  Lsasrv.dll
   9/07/01  03:31  5.0.2195.4301   33,552  Lsass.exe
   9/10/01  23:12  5.0.2195.4153  312,080  Netapi32.dll
   9/10/01  23:12  5.0.2195.4117  369,424  Netlogon.dll
   9/10/01  23:12  5.0.2195.4301  910,608  Ntdsa.dll
   9/10/01  23:12  5.0.2195.4316  386,832  Samsrv.dll
   9/10/01  23:12  5.0.2195.4117  111,376  Scecli.dll
   9/10/01  23:12  5.0.2195.3649  248,592  Scesrv.dll
   9/10/01  23:12  5.0.2195.4025   50,960  W32time.dll
   8/02/01  06:44  5.0.2195.4025   56,592  W32tm.exe
					


WORKAROUND

To work around this problem, increase paging space or physical memory. If you are running Windows 2000 Advanced Server, you can also enable 3 GB of program memory to work around the problem.

STATUS

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 3.

MORE INFORMATION

For additional information about how to install multiple hotfixes with only one reboot, click the article number below to view the article in the Microsoft Knowledge Base:

296861 Use QChain.exe to Install Multiple Hotfixes with One Reboot

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:

249149 Installing Microsoft Windows 2000 and Windows 2000 Hotfixes


Modification Type:MinorLast Reviewed:9/26/2005
Keywords:kbHotfixServer kbQFE kbbug kbfix kbSecurity kbWin2000PreSP3Fix kbWin2000sp3fix KB306483