Microsoft KB Archive/836084

From BetaArchive Wiki

Article ID: 836084

Article Last Modified on 10/26/2006



APPLIES TO

  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Datacenter Server




SYMPTOMS

When you log off from a Terminal Services session that is hosted on a Microsoft Windows 2000 Server-based computer, Windows 2000 Server may stop unexpectedly, and you may receive an error message that is similar to the following on the Windows 2000 Server:

STOP 0x0000001e (0xc0000005, 0xa0004d41, 0x00000001, 0x0000002c) KMODE_EXCEPTION_NOT_HANDLED

CAUSE

This problem may occur if synchronization does not complete correctly during the session cleanup that occurs when the Terminal Server session is closed. If the computer is under heavy stress conditions, some kernel-mode data structures that are in memory that are related to font resources may be freed incorrectly and may cause this error.

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

Windows 2000 Service Pack 3 or Windows 2000 Service Pack 4

Restart requirement

You must restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

   Date         Time   Version        Size       File name
   ----------------------------------------------------------
   24-Mar-2004  02:17  5.0.2195.6824     42,256  Basesrv.dll      
   21-Sep-2003  00:45  5.0.2195.6824    236,304  Cmd.exe          
   19-Jun-2003  20:05  5.0.2195.6660    233,744  Gdi32.dll        
   24-Mar-2004  02:17  5.0.2195.6897    742,160  Kernel32.dll     
   24-Mar-2004  02:17  5.0.2195.6824     54,544  Mpr.dll          
   04-Oct-2004  13:46  5.0.2195.6974    335,120  Msgina.dll       
   24-Mar-2004  02:17  5.0.2195.6892     90,264  Rdpwd.sys
   13-Sep-2004  19:27  5.0.2195.6974  5,898,752  Sp3res.dll       
   24-Mar-2004  02:17  5.0.2195.6897    403,216  User32.dll       
   05-Aug-2003  22:14  5.0.2195.6794    385,808  Userenv.dll      
   04-Oct-2004  13:35  5.0.2195.6982  1,632,848  Win32k.sys
   11-Mar-2004  02:37  5.0.2195.6898    181,520  Winlogon.exe     
   25-Sep-2003  18:08  5.0.2195.6826    243,984  Winsrv.dll       

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

For additional information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:

816915 New file naming schema for Microsoft Windows software update packages


For additional information, 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


For additional information about similar problems that may occur when a Terminal Services session is closed, click the following article numbers to view the articles in the Microsoft Knowledge Base:

837583 STOP: 0x00000050 error occurs in Windows Server 2003 when a Terminal Services session is closed


841054 You receive a "Stop 0x0000001E" error message when you log off from a Windows 2000 Server terminal server


839429 You receive a "STOP: 0x0000001E" error message on a Windows 2000-based computer that is running Terminal Services


Keywords: kbhotfixserver kbqfe kbhotfixserver kbqfe kbbug kbfix kbqfe kbwin2000presp5fix KB836084