Article ID: 837585
Article Last Modified on 11/3/2007
APPLIES TO
- Microsoft Windows Server 2003, Standard x64 Edition
- Microsoft Windows Server 2003, Datacenter x64 Edition
- Microsoft Windows Server 2003, Enterprise x64 Edition
- Microsoft Windows Server 2003, 64-Bit Datacenter Edition
- Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
- Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
- Microsoft Windows Server 2003, Standard Edition (32-bit x86)
- Microsoft Windows 2000 Service Pack 3
- Microsoft Windows 2000 Service Pack 4
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Advanced Server
SYMPTOMS
On your Microsoft Windows 2000 Server-based computer or your Microsoft Windows Server 2003-based computer that is running Terminal Services, you may experience the following symptoms:
- The server becomes slow and unresponsive. Eventually, you cannot establish new Terminal Services sessions.
- If you use Task Manager to view the running processes, you may see that there are several orphaned Csrss.exe processes. There are no corresponding Terminal Services client sessions when you view the sessions in Terminal Services Manager.
- You cannot stop the orphaned Csrss.exe processes to free server resources. Therefore, the Csrss.exe processes may continue to accumulate until you must restart the server to free memory and CPU resources.
If you apply the hotfix that is described in the Microsoft Knowledge Base article 827350, this may help reduce the number of Csrss.exe processes, but you still experience the problem.
827350 Clients cannot connect to a terminal server when Csrss.exe and Termsrv.exe spike at 100 percent CPU usage
CAUSE
The problem occurs because of a regression that was introduced in Windows 2000 Service Pack 3 (SP3). Windows 2000 SP3 includes a fix that introduces a temporary winstation object in the Csrss.exe process. This fix is described in the following Microsoft Knowledge Base article:
261322 Stop 0x0000001E error message when you print from a Windows 2000 Terminal Services client
If the temporary winstation objects are not released correctly, you may experience the symptoms that are described earlier in this article.
RESOLUTION
Hotfix information
Windows Server 2003
A supported hotfix is now 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 this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows Server 2003 Service Pack that contains this hotfix.
To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:
Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:
Prerequisites
No prerequisites are required.
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.
Windows Server 2003, x86-based versions
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Winsrv.dll | 5.2.3790.170 | 291,840 | 04-May-2004 | 23:28 | x86 |
Windows Server 2003, Itanium-based versions
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Winsrv.dll | 5.2.3790.170 | 764,928 | 04-May-2004 | 08:22 | IA-64 |
Windows 2000
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows 2000 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer 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
To install this hotfix, you must have Windows 2000 Service Pack 3 (SP3) installed on the computer.
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 item in Control Panel.
| File name | File version | File size | Date | Time | Platform | Service branch |
|---|---|---|---|---|---|---|
| Basesrv.dll | 5.0.2195.6824 | 42,256 | 24-Mar-2004 | 02:17 | x86 | Not Applicable |
| Cmd.exe | 5.0.2195.6824 | 236,304 | 21-Sep-2003 | 00:45 | x86 | Not Applicable |
| Gdi32.dll | 5.0.2195.6660 | 233,744 | 19-Jun-2003 | 20:05 | x86 | Not Applicable |
| Kernel32.dll | 5.0.2195.6897 | 742,160 | 24-Mar-2004 | 02:17 | x86 | Not Applicable |
| Mpr.dll | 5.0.2195.6824 | 54,544 | 24-Mar-2004 | 02:17 | x86 | Not Applicable |
| Msgina.dll | 5.0.2195.6958 | 335,120 | 13-Jul-2004 | 21:25 | x86 | Not Applicable |
| Rdpwd.sys | 5.0.2195.6892 | 90,264 | 24-Mar-2004 | 02:17 | x86 | Not Applicable |
| Sp3res.dll | 5.0.2195.6935 | 5,887,488 | 04-Jun-2004 | 23:13 | x86 | Not Applicable |
| User32.dll | 5.0.2195.6897 | 403,216 | 24-Mar-2004 | 02:17 | x86 | Not Applicable |
| Userenv.dll | 5.0.2195.6794 | 385,808 | 05-Aug-2003 | 22:14 | x86 | Not Applicable |
| Win32k.sys | 5.0.2195.6958 | 1,631,760 | 10-Jul-2004 | 05:36 | x86 | Not Applicable |
| Winlogon.exe | 5.0.2195.6898 | 181,520 | 11-Mar-2004 | 02:37 | x86 | Not Applicable |
| Winsrv.dll | 5.0.2195.6958 | 244,496 | 13-Jul-2004 | 21:25 | x86 | Not Applicable |
| Kernel32.dll | 5.0.2195.6897 | 742,160 | 24-Mar-2004 | 02:17 | x86 | UNIPROC |
| Win32k.sys | 5.0.2195.6958 | 1,631,760 | 10-Jul-2004 | 05:36 | x86 | UNIPROC |
| Winsrv.dll | 5.0.2195.6958 | 244,496 | 13-Jul-2004 | 21:25 | x86 | UNIPROC |
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This feature was first included in Windows Server 2003 Service Pack 1.
MORE INFORMATION
For more information about how hotfix packages are named, click the following article numbers to view the articles in the Microsoft Knowledge Base:
816915 New naming schema for Microsoft Windows hotfix packages
824684 Description of the standard terminology that is used to describe Microsoft software updates
Technical support for x64-based versions of Microsoft Windows
If your hardware came with a Microsoft Windows x64 edition already installed, your hardware manufacturer provides technical support and assistance for the Windows x64 edition. In this case, your hardware manufacturer provides support because a Windows x64 edition was included with your hardware. Your hardware manufacturer might have customized the Windows x64 edition installation by using unique components. Unique components might include specific device drivers or might include optional settings to maximize the performance of the hardware. Microsoft will provide reasonable-effort assistance if you need technical help with a Windows x64 edition. However, you might have to contact your manufacturer directly. Your manufacturer is best qualified to support the software that your manufacturer installed on the hardware. If you purchased a Windows x64 edition such as a Microsoft Windows Server 2003 x64 edition separately, contact Microsoft for technical support.
For product information about Microsoft Windows XP Professional x64 Edition, visit the following Microsoft Web site:
For product information about x64-based versions of Microsoft Windows Server 2003, visit the following Microsoft Web site:
Additional query words: Winx64 Windowsx64 64-bit 64bit
Keywords: kbhotfixserver kbbug kbfix kbqfe kbwin2000presp5fix KB837585
