When a client computer logs off from a Terminal Services session, you may receive a Stop error message on the terminal server that resembles the following:This problem occurs when the terminal server is running Microsoft Windows Server 2003 with Service Pack 1. When this problem occurs, other client computers that are logged on to the terminal server may stop responding.

Back to the top

This problem is caused by a session pool memory leak in the Win32k.sys file.

Back to the top

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

Hotfix information

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 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: 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.

Prerequisites

To apply this hotfix, you must have Windows Server 2003 Service Pack 1 installed. For more information about how to obtain the latest service pack for Windows Server 2003, click the following article number to view the article in the Microsoft Knowledge Base:

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix replaces the following 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.

Windows Server 2003, x86-based versions

File name	File version	File size	Date	Time	Platform	SP requirement
Gdi32.dll	5.2.3790.2766	282,112	08-Aug-2006	13:04	x86	SP1
Win32k.sys	5.2.3790.2766	1,850,880	06-Aug-2006	16:28	x86	SP1

Windows Server 2003, x64-based versions

File name	File version	File size	Date	Time	Platform	SP requirement	Service branch
Gdi32.dll	5.2.3790.2767	610,304	07-Aug-2006	22:23	x64	SP1	Not Applicable
Win32k.sys	5.2.3790.2767	4,529,664	07-Aug-2006	22:23	x64	SP1	Not Applicable
Wgdi32.dll	5.2.3790.2766	285,184	07-Aug-2006	22:23	x86	SP1	WOW

Windows Server 2003, Itanium-based versions

File name	File version	File size	Date	Time	Platform	SP requirement	Service branch
Gdi32.dll	5.2.3790.2767	906,240	07-Aug-2006	22:23	IA-64	SP1	Not Applicable
Win32k.sys	5.2.3790.2767	5,546,496	07-Aug-2006	22:23	IA-64	SP1	Not Applicable
Wgdi32.dll	5.2.3790.2766	285,184	07-Aug-2006	22:23	x86	SP1	WOW

Back to the top

Other problems may cause similar symptoms. For more information about the "Stop 0x000000AB" error message, click the following article numbers to view the articles in the Microsoft Knowledge Base:

Back to the top

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2.

Back to the top