Article ID: 934330 - Last Review: October 11, 2007 - Revision: 1.4 The Csrss.exe process in a terminal-server session continuously consumes more than 50 percent of CPU resources on a Windows Server 2003-based terminal server
On This PageSYMPTOMSOn a Microsoft Windows Server 2003-based terminal server, you may experience one or more of the following symptoms:
CAUSEThis problem occurs because an error in the Winsrv.dll file causes an access violation in the Csrss.exe process. The Csrss.exe process tries to de-reference an object that has already been released. This access violation generates high CPU usage in the Csrss.exe process. Therefore, the terminal-server session stops responding. RESOLUTIONHotfix informationA 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 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 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: http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
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.PrerequisitesTo apply this hotfix, you must have Windows Server 2003 Service Pack 1 or Windows Server 2003 Service Pack 2 installed on the computer. For more information, click the following article number to view the article in the Microsoft Knowledge Base:889100
(http://support.microsoft.com/kb/889100/
)
How to obtain the latest service pack for Windows Server 2003
Restart requirementYou must restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace any other hotfixes.File informationThe 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.Windows Server 2003 with Service Pack 1, x86-based versionsCollapse this table
Windows Server 2003 with Service Pack 2, x86-based versionsCollapse this table
Windows Server 2003 with Service Pack 1, Itanium-based versionsCollapse this table
Windows Server 2003 with Service Pack 2, Itanium-based versionsCollapse this table
Windows Server 2003, x64-based versionsCollapse this table
Windows Server 2003 with Service Pack 2, x64-based versionsCollapse this table
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATION
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates
APPLIES TO
| Article Translations
|

Back to the top
