Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

"0x000000AB" Stop error when a Citrix client logs off from a RD Session Host that is running Windows Server 2008 R2 SP1


View products that this article applies to.

Symptoms

Assume that a Remote Desktop Session Host (RD Session Host) is running Windows Server 2008 R2 Service Pack 1 (SP1). Additionally, Citrix XenApp is installed in the RD Session Host. When a Citrix client logs off from a remote Citrix ICA session on the RD Session Host, the RD Session Host crashes. Additionally, you receive a Stop error message that resembles the following:
Stop 0x000000AB (Parameter1, Parameter2, Parameter3, Parameter4)

Notes

  • This Stop error describes a SESSION_HAS_VALID_POOL_ON_EXIT issue.
  • The parameters in this Stop error message vary, depending on the configuration of the computer.
  • Not all "Stop 0x000000AB" errors are caused by this issue.

↑ Back to the top


Cause

This issue occurs because the Gdbr tag in the Win32k.sys file leaks. This causes�the pool memory of a session to leak.

↑ Back to the top


Resolution

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 the problem described in this article. 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 website: 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 be running Windows Server 2008 R2 SP1.

For more information about how to obtain a Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To use the hotfix, you do not have to change the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, milestone (RTM,SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
    VersionProductMilestoneService branch
    6.1.760 1.22xxxWindows Server 2008 R2SP1LDR
  • The MANIFEST files (.manifest) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. MANIFEST files and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Win32k.sys6.1.7601.221733,152,38424-Nov-201203:31x64
For all supported IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Win32k.sys6.1.7601.221737,450,11224-Nov-201203:05IA-64

↑ Back to the top


Status

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

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

↑ Back to the top


More information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2
File nameAmd64_40e3b2daa20e8d0f1a204a8fbb3eb2ec_31bf3856ad364e35_6.1.7601.22173_none_998d2c79e69bbe63.manifest
File versionNot applicable
File size698
Date (UTC)24-Nov-2012
Time (UTC)08:32
PlatformNot applicable
File nameAmd64_582c24bc5dcaec4299f1d043a37953a4_31bf3856ad364e35_6.1.7601.22173_none_70ae55802de01626.manifest
File versionNot applicable
File size1,038
Date (UTC)24-Nov-2012
Time (UTC)08:32
PlatformNot applicable
File nameAmd64_b7b4434b8b64127d399a92a837cc8872_31bf3856ad364e35_6.1.7601.22173_none_f30f07848852a8d0.manifest
File versionNot applicable
File size698
Date (UTC)24-Nov-2012
Time (UTC)08:32
PlatformNot applicable
File nameAmd64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.22173_none_17611bdcca75a9f8.manifest
File versionNot applicable
File size42,090
Date (UTC)24-Nov-2012
Time (UTC)07:18
PlatformNot applicable
File nameWow64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.22173_none_21b5c62efed66bf3.manifest
File versionNot applicable
File size4,178
Date (UTC)24-Nov-2012
Time (UTC)06:21
PlatformNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File nameIa64_f8b725ce0c4379dfc45dc500f22f384a_31bf3856ad364e35_6.1.7601.22173_none_8cf8ef459a649edd.manifest
File versionNot applicable
File size1,036
Date (UTC)24-Nov-2012
Time (UTC)08:32
PlatformNot applicable
File nameIa64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.22173_none_bb44244f121641be.manifest
File versionNot applicable
File size42,088
Date (UTC)24-Nov-2012
Time (UTC)07:13
PlatformNot applicable
File nameWow64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.22173_none_21b5c62efed66bf3.manifest
File versionNot applicable
File size4,178
Date (UTC)24-Nov-2012
Time (UTC)06:21
PlatformNot applicable

↑ Back to the top


Keywords: kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseadvanced, kbexpertisebeginner, KB2786447

↑ Back to the top

Article Info
Article ID : 2786447
Revision : 2
Created on : 1/9/2013
Published on : 1/9/2013
Exists online : False
Views : 342