Article ID: 835579 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
A server that is running Microsoft Windows NT 4.0 Terminal Server Edition responds slowly, and a Client-Server Runtime SubSystem (CSRSS) process uses 100 percent of the processor time.
This problem occurs when a CSRSS process becomes orphaned on a server that is running Windows NT 4.0 Terminal Server Edition.
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:
http://support.microsoft.com/contactus/?ws=supportNote 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.
The English version of this hotfix has the file attributes (or later) 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 -------------------------------------------------------------- 19-Aug-2003 13:58 4.0.1381.33552 170,256 Gdi32.dll 19-Aug-2003 13:58 4.0.1381.33552 332,048 User32.dll 26-Jan-2004 16:59 4.0.1381.33559 1,280,816 Win32k.sys 16-Dec-2003 17:56 4.0.1381.33559 196,368 Winsrv.dll
Note Because of file dependencies, this hotfix requires Microsoft Windows NT 4.0 Service Pack 6a.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.