"0x000000AB" Stop error in Windows Server 2012-based RDS server when you log off from a Remote Desktop session

View products that this article applies to.

Symptoms

When this issue occurs, all the running Remote Desktop Protocol (RDP) sessions on the Remote Desktop Services (RDS) server stop responding, and the unsaved work on these sessions will be lost. Additionally, the Stop error message resembles the following:

STOP: 0x000000AB (parameter1 , parameter2 , parameter3 , parameter4 )

Notes

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

↑ Back to the top

Cause

This issue occurs because of a memory leak in the Win32k.sys subsystem.

↑ Back to the top

Resolution

To resolve this issue, we have released a hotfix for Windows Server 2012. This hotfix has a restart requirement.

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.

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, submit a request to 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:

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.

Prerequisites

There is no prerequisite to apply this hotfix.

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You have to 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 2012 file information and notes

Important Windows 8 hotfixes and Windows Server 2012 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 8/Windows Server 2012" 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:

Version Product Milestone Service branch
6.2.920 0.21xxx Windows Server 2012 RTM LDR
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very 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.

Version	Product	Milestone	Service branch
6.2.920 0.21xxx	Windows Server 2012	RTM	LDR

For all supported x64-based versions of Windows Server 2012

File name	File version	File size	Date	Time	Platform
Win32k.ptxml	Not applicable	4,172	25-Jul-2012	20:29	Not applicable
Win32k.sys	6.2.9200.21314	4,065,792	03-Dec-2014	07:12	x64
Wow64_win32k.ptxml	Not applicable	4,172	12-Feb-2013	00:09	Not applicable

Additional file information

Additional file information for Windows Server 2012

Additional files for all supported x64-based versions of Windows Server 2012

File property	Value
File name	Amd64_975705fd955bffbd703553a98e30ec2c_31bf3856ad364e35_6.2.9200.21315_none_1838d2a4a73603f2.manifest
File version	Not applicable
File size	1,038
Date (UTC)	05-Dec-2014
Time (UTC)	21:45
File name	Amd64_d9a9c7b5013346dbf6e081ee0e0569bc_31bf3856ad364e35_6.2.9200.21315_none_32817dc096b18c6f.manifest
File version	Not applicable
File size	698
Date (UTC)	05-Dec-2014
Time (UTC)	21:45
File name	Amd64_fab5358794e604eaf2a19cc2c1e5c80a_31bf3856ad364e35_6.2.9200.21315_none_047fcd338717e822.manifest
File version	Not applicable
File size	698
Date (UTC)	05-Dec-2014
Time (UTC)	21:45
File name	Amd64_microsoft-windows-win32k_31bf3856ad364e35_6.2.9200.21315_none_129354fa3d2f11bb.manifest
File version	Not applicable
File size	104,691
Date (UTC)	05-Dec-2014
Time (UTC)	04:06
File name	Wow64_microsoft-windows-win32k_31bf3856ad364e35_6.2.9200.21315_none_1ce7ff4c718fd3b6.manifest
File version	Not applicable
File size	103,958
Date (UTC)	05-Dec-2014
Time (UTC)	01:13