Stop error message on a terminal server that is running Windows Server 2003 Service Pack 1 or Windows Server 2003 Service Pack 2: "Stop 0x000000AB (SESSION_HAS_VALID_POOL_ON_EXIT)"

When a client computer logs off from a Terminal Services session, you receive a Stop error message on the terminal server. The Stop error message resembles the following:This problem occurs when the terminal server is running Windows Server 2003 with Service Pack 1 (SP1) or with Service Pack 2 (SP2).

When this problem occurs, other clients that are logged on to the same terminal server may also stop responding. Additionally, the following event is logged in the System log:

Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000ab (parameter1, parameter2, parameter3, parameter4). A dump was saved in: C:\WINDOWS\MEMORY.DMP.

This problem occurs because some objects that the Win32k.sys driver allocates from the session pool are not freed before the session ends. Defective printer drivers may cause this memory leak condition. In this case, the memory manager issues a Stop error to prevent the system from continuing in an unstable state.

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 SP1 or Windows Server 2003 SP2 installed on the computer. For more information, 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 hotfixes that are described in the following Microsoft Knowledge Base articles:

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 with SP1, x86-based versions

Windows Server 2003 with SP2, x86-based versions

Windows Server 2003 with SP1, Itanium-based versions

Windows Server 2003 with SP2, Itanium-based versions

Windows Server 2003, x64-based versions

Windows Server 2003 with SP2, x64-based versions

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

Session pool allocation is marked by a four-letter code (tag), such as "Gpat." Users can use this tag to find the leaked object. For example, some tags start with "G" for GDI objects. Other tags start with "U" for user objects.

The kernel-mode GDI code in the Win32k.sys driver calls back from the kernel mode to user-mode printer drivers. If a printer driver unexpectedly ends the thread that executes the callback, the GDI code may remain in an inconsistent state. In this case, objects may be leaked. Objects may also be leaked when the printer drivers close incorrect handles. Therefore, this problem may sometimes disappear after you update printer drivers.

This hotfix also includes all previous fixes that address "Stop 0x000000AB" issues. The investigation of the leaked tags that occur in the Win32k.sys driver is continuing. More leaked tags will be fixed when they are identified by specific cases. The following is an accumulative list of all leaked tags that this hotfix fixes:

• Gadd
• Gcac
• Geto
• Gffv
• Gfnt
• Ggb
• Gglf
• Ggls
• Gh*5
• Ghtc
• Ghx<
• Ghx4
• Ghx7
• GhxE
• Gl*5
• Gla4
• Gla5
• Glx4
• Gpat
• Gpfe
• Gpff
• Gpid
• Gqnk
• Gsp
• Gtmp
• Gtmw
• Gtvp
• Gump
• Gxlt
• knlf
• Uscm
• Usd1
• UsdE
• Usgh
• Usjb
• Usqm
• Usrt
• Ussy

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:

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: