Stop 0x0000001e Error Message in Win32k.sys When Users Log Off from a Server Running Terminal Services (302510)



The information in this article applies to:

  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Professional
  • Microsoft Windows 2000 Server

This article was previously published under Q302510

SYMPTOMS

When you log off from a Windows 2000-based server that is running Terminal Services, you may receive a stop 0x0000001e error message that references the Win32k.sys file.

CAUSE

This problem may occur when code tries to dereference a window class object that has already been destroyed.

RESOLUTION

Service Pack Information

To resolve this problem, obtain the latest service pack for Microsoft 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

Hotfix Information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site: Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. The English version of this fix should have the following file attributes or later:
   Date         Time   Version         Size       File name
   -----------------------------------------------------------
   16-Apr-2002  18:24  5.0.2195.5265      42,256  Basesrv.dll
   16-Apr-2002  18:24  5.0.2195.5520     222,480  Gdi32.dll
   16-Apr-2002  18:24  5.0.2195.4928     708,880  Kernel32.dll
   25-Jun-2001  21:17  3.10.0.103         47,808  User.exe
   16-Apr-2002  18:24  5.0.2195.4314     402,192  User32.dll
   16-Apr-2002  18:24  5.0.2195.5521     369,424  Userenv.dll
   13-Apr-2002  19:39  5.0.2195.5579   1,641,776  Win32k.sys
   23-Jan-2002  13:45  5.0.2195.4865     178,960  Winlogon.exe
   16-Apr-2002  18:24  5.0.2195.4602     243,472  Winsrv.dll         
				

STATUS

Microsoft 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 Microsoft Windows 2000 Service Pack 4.

MORE INFORMATION

The desktop menu window object is destroyed after the reference count is decremented to 0. Dereferencing this object causes the system to bug check.

Inconsistency Between ReferenceClass/DereferenceClass

: kd> r
ast set context:
ax=00000000 ebx=a0d70a78 ecx=a0d90000 edx=a0d706e0 esi=a0d70a48 
edi=a21ee6d8
ip=a0034a4d esp=ac74bc70 ebp=ac74bcac iopl=0         nv up ei ng nz na po 
nc
s=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000            
efl=00010286
in32k!DereferenceClass+11:
0034a4d ff4828           dec  dword ptr [eax+0x28] 
ds:0023:00000028=????????
: kd> kv
 *** Stack trace for last set context - .thread resets it
hildEBP RetAddr  Args to Child
c74bc6c a0034934 a0d70a48 a21ee6d8 a0d70a48 win32k!DereferenceClass+0x11 
(FPO: [1,0,0])
c74bcac a003422c a22133b8 ac74bcec a017b1c0 win32k!xxxFreeWindow+0x641 
(FPO: [Non-Fpo])
c74bcfc a00846cf 00000000 00000000 00000000 win32k!xxxDestroyWindow+0x410 
(FPO: [Non-Fpo])
c74bda8 80454fde 870fb7d8 00000000 00000000 win32k!xxxDesktopThread+0x5bf 
(FPO: [Non-Fpo])
c74bddc 8046a302 a0084110 a017b1c0 0000000 
ntkrnlmp!PspSystemThreadStartup+0x54 (FPO: [Non-Fpo])
0000000 00000000 00000000 00000000 00000000 ntkrnlmp!_KiThreadStartup+0x16
: kd> dd a0d70a48+60 l1
0d70aa8  a0d90000
: kd> dd a0d90000
0d90000  00000000 00000000 00000000 00000000
0d90010  00000000 00000000 00000000 00000000
0d90020  00000000 00000000 ffffffff 00000000
0d90030  00000000 00000000 00000000 00000000
0d90040  00000000 00000000 00000000 00000000
0d90050  00000000 00000000 00000000 00000000
0d90060  00000000 00000000 00000000 00000000
0d90070  00000000 00000000 00000000 00000000
: kd> u win32k!DereferenceClass
in32k!DereferenceClass:
0034a3c 8b442404         mov     eax,[esp+0x4]
0034a40 8b4860           mov     ecx,[eax+0x60]
0034a43 8b4120           mov     eax,[ecx+0x20]
0034a46 ff4928           dec     dword ptr [ecx+0x28]
0034a49 3bc8             cmp     ecx,eax
0034a4b 741f             jz      win32k!DereferenceClass+0x30 (a0034a6c)
0034a4d ff4828           dec     dword ptr [eax+0x28]
0034a50 83792800         cmp     dword ptr [ecx+0x28],0x0
				
For additional information about how to obtain a hotfix for Windows 2000 Datacenter Server, click the article number below to view the article in the Microsoft Knowledge Base:

265173 Datacenter Program and Windows 2000 Datacenter Server Product

For additional information about how to install multiple hotfixes with only one reboot, click the following article number to view the article in the Microsoft Knowledge Base:

296861 How to Install Multiple Windows Updates or Hotfixes with Only One Reboot

For additional information about how to install Windows 2000 and Windows 2000 hotfixes at the same time, click the article number below to view the article in the Microsoft Knowledge Base:

249149 Installing Microsoft Windows 2000 and Windows 2000 Hotfixes


Modification Type:MinorLast Reviewed:10/7/2005
Keywords:kbHotfixServer kbQFE kbWin2kSP4fix kbWin2000preSP4Fix kbbug kbenv kberrmsg kbfix kbTermServ kbShell KB302510 kbAudITPRO