The Lsass.exe process crashes, and then you receive the following error message on a computer that is running a 64-bit version of Windows Server 2003 Service Pack 2 (SP2):
System Shutdown - The system is shutting down. Please save all work in progress and log off. Any unsaved changes will be lost. This shutdown was initiated by NT AUTHORITY\SYSTEM. Shutdown will begin in number seconds. Shutdown message: The system process 'C:\WINDOWS\system32\lsass.exe' terminated unexpectedly with status code error code . The system will now shut down and restart.
Additionally, the following event is logged to the Application log:
Event Type: Information Event Source: Application Error Event Category: (100) Event ID: 1004 Description: Reporting queued error: faulting application lsass.exe, version version number, faulting module module name, version 5.2.3790.3959, fault address memory address.
The following event is logged to the System log:
Event Type: Error Event Source: LsaSrv Event Category: Security Package Manager Event ID: 5000 Date: date Time: time User: N/A Computer: computer Description: The security package Negotiate generated an exception. The exception information is the data.
This issue occurs because the Lsass.exe process does not initialize a 64-bit pointer variable and then transfers data to this variable from a 32-bit pointer variable by using Windows on Win32 (WOW). Therefore, the 64-bit pointer variable becomes invalid, and the Lsass.exe process crashes when the variable is used to access memory.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
To apply this hotfix, you must be running Windows Server 2003 Service Pack 2 (SP2).
For more information about how to obtain a Windows Server 2003 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
889100 How to obtain the latest service pack for Windows Server 2003
You may have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
The English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2003 file information notes
In addition to the files that are listed in these tables, this hotfix also installs an associated security catalog file (KBnumber.cat) that is signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2003
For all supported IA-64-based versions of Windows Server 2003
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates