Microsoft KB Archive/946068

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

Article ID: 946068

Article Last Modified on 12/19/2007

-

APPLIES TO

 Microsoft Windows Server 2003 Service Pack 1, when used with:  Microsoft Windows Server 2003, Standard Edition (32-bit x86)

 Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)

 Microsoft Windows Server 2003, Web Edition

 Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)</li></ul>

 Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems</li></ul>

 Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems</li></ul> </li> Microsoft Windows Server 2003 Service Pack 2, when used with:  Microsoft Windows Server 2003, Standard Edition (32-bit x86)</li></ul>

 Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)</li></ul>

 Microsoft Windows Server 2003, Web Edition</li></ul>

 Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)</li></ul>

 Microsoft Windows Server 2003, Standard x64 Edition</li></ul>

 <li>Microsoft Windows Server 2003, Enterprise x64 Edition</li></ul>

<ul> <li>Microsoft Windows Server 2003, Datacenter x64 Edition</li></ul>

<ul> <li>Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems</li></ul>

<ul> <li>Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems</li></ul> </li> <li>Microsoft Windows Server 2003, Standard x64 Edition</li> <li>Microsoft Windows Server 2003, Enterprise x64 Edition</li> <li>Microsoft Windows Server 2003, Datacenter x64 Edition</li></ul>

-

<div class="symptoms_section">

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

Stop 0x000000AB (SESSION_HAS_VALID_POOL_ON_EXIT)

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:

Time:

User: N/A

Computer:

Description:

The computer has rebooted from a bugcheck. The bugcheck was: 0x000000ab. A dump was saved in: C:\WINDOWS\MEMORY.DMP.

<div class="cause_section">

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

<div class="resolution_section">

Hotfix information
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:

http://go.microsoft.com/?linkid=6294451

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:

http://support.microsoft.com/contactus/?ws=support

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:

889100 How to obtain the latest service pack for Windows Server 2003

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:

901150 You may receive a &quot;Stop 0x000000ab&quot; error message when you log off a Terminal Services session on a Windows Server 2003 Service Pack 1-based Terminal Server

907242 You receive a &quot;Stop 0x000000ab&quot; error message when you log off from a Terminal Services session on a Windows Server 2003 Service Pack 1-based terminal server

910362 Error message when you log off from a Terminal Services session on a Windows Server 2003 Service Pack 1-based terminal server: &quot;Stop 0x000000AB SESSION_HAS_VALID_POOL_ON_EXIT&quot;

918673 You receive a &quot;Stop 0x000000ab&quot; error message when a Terminal Services client computer logs off from a Terminal Services session on a Windows Server 2003 Service Pack 1-based Terminal Services computer

923035 Stop error message when a Terminal Services client logs off from a session on a server that is running Windows Server 2003 with Service Pack 1: &quot;Stop 0x000000AB (SESSION_HAS_VALID_POOL_ON_EXIT)&quot;

924806 Stop error message when a client logs off a Terminal Services session on a server that is running Windows Server 2003 with Service Pack 1: &quot;Stop 0x000000AB (SESSION_HAS_VALID_POOL_ON_EXIT)&quot;

925919 Stop error message when a client computer logs off from a Terminal Services session on a server that is running Windows Server 2003 with Service Pack 1 or with Service Pack 2: &quot;Stop 0x000000AB (SESSION_HAS_VALID_POOL_ON_EXIT)&quot;

931282 Stop error message when a client computer logs off from a Terminal Services session on a server that is running Windows Server 2003 with Service Pack 1 or with Service Pack 2: &quot;Stop 0x000000AB (SESSION_HAS_VALID_POOL_ON_EXIT)&quot;

939442 Stop error message when a client logs off from a Terminal Services session on a Windows Server 2003-based terminal server: &quot;Stop 0x000000ab&quot;

944916 Stop error message when a client logs off from a Terminal Services session on a server that is running Windows Server 2003 with Service Pack 1 or Windows Server 2003 with Service Pack 2: &quot;Stop 0x000000AB (SESSION_HAS_VALID_POOL_ON_EXIT)&quot;

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 SP2, x64-based versions
<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

<div class="moreinformation_section">

MORE INFORMATION
Session pool allocation is marked by a four-letter code (tag), such as &quot;Gpat.&quot; Users can use this tag to find the leaked object. For example, some tags start with &quot;G&quot; for GDI objects. Other tags start with &quot;U&quot; 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 &quot;Stop 0x000000AB&quot; 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

<div class="references_section">