A Terminal Services Server Generates a "Stop 0xAB" Message on a Blue Screen (317855)
The information in this article applies to:
- Microsoft Windows 2000 Server SP1
- Microsoft Windows 2000 Server SP2
- Microsoft Windows 2000 Advanced Server SP1
- Microsoft Windows 2000 Advanced Server SP2
- Microsoft Windows 2000 Professional SP1
- Microsoft Windows 2000 Professional SP2
This article was previously published under Q317855 SYMPTOMS
When a Terminal Services client logs off of the Terminal Services session, the Terminal Services server to which the client was connected might generate a "Stop 0xAB" error message on a blue screen.
CAUSE
This problem occurs because the Usqm pool is leaking because of an issue in the accessibility options.
RESOLUTIONTo resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
The English version of this fix should have the following file attributes or later:
Date Time Version Size File name
--------------------------------------------------------
14-Feb-2002 15:03 5.0.2195.49 708,880 Kernel32.dll
14-Feb-2002 15:02 5.0.2195.43 402,192 User32.dll
25-Jun-2001 18:17 3.10.0.103 47,808 User.exe
14-Feb-2002 15:02 5.0.2195.43 371,984 Userenv.dll
14-Feb-2002 15:04 5.0.2195.49 1,642,704 Win32k.sys
23-Jan-2002 10:45 5.0.2195.48 178,960 Winlogon.exe
14-Feb-2002 15:02 5.0.2195.46 243,472 Winsrv.dll
14-Feb-2002 15:02 5.0.2195.49 42,256 Basesrv.dll
14-Feb-2002 15:02 5.0.2195.45 222,480 Gdi32.dll
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows 2000 Service Pack 3.
| Modification Type: | Minor | Last Reviewed: | 9/27/2005 |
|---|
| Keywords: | kbHotfixServer kbQFE kbbug kbfix kbshell kbWin2000PreSP3Fix kbWin2000sp3fix KB317855 |
|---|
|