You may receive a "Stop 0x00000050" error message in Windows NT 4.0 Terminal Server Edition (322939)

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

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

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.

Prerequisites

No prerequisites are required.

Restart requirement

You do not have to restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later) 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 tool in Control Panel.

   Date         Time   Version         Size       File name
   -----------------------------------------------------------
   06-Apr-2002  00:38  4.0.1381.33535    170,256  Gdi32.dll
   19-Sep-2002  19:09  4.0.1381.33542  1,003,968  Ntkrnlmp.exe
   19-Sep-2002  19:09  4.0.1381.33542    982,976  Ntoskrnl.exe
   24-Sep-2002  19:39  1.16.120.0      2,630,424  Q322939i.exe
   06-Apr-2002  00:38  4.0.1381.33535    332,048  User32.dll
   19-Sep-2002  19:08  4.0.1381.33542  1,279,952  Win32k.sys
   06-Apr-2002  00:42  4.0.1381.33535    196,368  Winsrv.dll

MORE INFORMATION

Stack output

This following is an example of stack dump information that is generated when the problem occurs:

f3d25e48 a3116a94 b3ca2eb0 00004e20 f3d25f04 win32k!FHungApp+0x7
f3d25ea8 a3104c05 0000011c 00000004 00c0fd7c win32k!QueryInformationThread+0x2f8
f3d25ee8 80148589 0000011c 00000004 00c0fd7c win32k!NtUserQueryInformationThread+0xa3
f3d25ee8 5ffc3f93 0000011c 00000004 00c0fd7c nt!KiSystemService+0xc9
00c0f94c 5ffaf96e 0000011c 00000004 00c0fd7c winsrv!ZwUserQueryInformationThread+0xb
00c0fda0 5ffaf790 0014002a 00228d50 00000000 winsrv!MySendEndSessionMessages+0x1ac
00c0fdc8 5ffaf646 00010022 00228d50 00000009 winsrv!SendShutdownMessages+0x3e
00c0fe1c 5ff83e8b 00228c38 00000204 c0fe3001 winsrv!UserClientShutdown+0x298
00c0fe70 5ffaf2a3 00c0fe8c 00000204 7ffde000 CSRSRV!CsrShutdownProcesses+0xfe
00c0fec8 5ffb010d 00229ea8 00000204 00000000 winsrv!_ExitWindowsEx+0x142
00c0fee4 5ff827b8 00c0ff00 00c0ffd0 00000005 winsrv!SrvExitWindowsEx+0x38
00c0fff4 00000000 00000000 00000000 0001009f CSRSRV!CsrApiRequestThread+0x5db
3: kd> !userkdx.dti b7560eb0
et 0x83289020 t 0xb7560eb0 q 0xa4147ba8 i 7f7.924 NDDEAGNT.EXE
PTHREADINFO @ 0xb7560eb0
	PtiLink.Flink         @0xb7560ee8
	ptl                   @0x00000000
	ptlOb                 @0x00000000
	ppi                   @0xb914aed0
	pq                    @0xa4147ba8
	spklActive            @0x00000000
	mlPost.pqmsgRead      @0x00000000
	mlPost.pqmsgWriteLast @0x00000000
	mlPost.cMsgs           0x00000000
	rpdesk                @0x831a2d18
	hdesk                  0x00000034
	amdesk                 0x000f01ff
	pDeskInfo             @0xa5190588
	pClientInfo           @0x7ffde044
	TIF_flags              TIF_INCLEANUP | TIF_DONTATTACHQUEUE | TIF_ALLOWSHUTDOWN | TIF_SHUTDOWNCOMPLETE | 0x2000000
	sphkCurrent           @0x00000000
	pEventQueueServer     @0x83a00400
	hEventQueueClient      0x00000000
	fsChangeBits           0
	fsChangeBitsRemovd     QS_POSTMESSAGE | QS_ALLPOSTMESSAGE
	fsWakeBits             0
	fsWakeMask             0
	cPaintsReady           0x0000
	cTimersReady           0x0000
	timeLast               0x00000000
	ptLast.x               0x00000000
	ptLast.y               0x00000000
	idLast                 0x00000000
	cQuit                  0x00000000
	exitCode               0x00000000
	pSBTrack               0x00000000
	psmsSent              @0x00000000
	psmsCurrent           @0x00000000
	fsHooks                0x00000000
	asphkStart            @0xb7560fb8 l16
	sphkCurrent           @0x00000000
	psmsReceiveList       @0x00000000
	ptdb                  @0x00000000
	Thread                @0x83289020
	  PriorityClass 2
	cWindows               0x00000000
	cVisWindows            0x00000000
	pqAttach              @0x00000000
	iCursorLevel           0x00000000
	pMenuState            @0x00000000

Dump the ppi:
3: kd> dd 0xb914aed0
b914aed0  ???????? ???????? ???????? ????????
b914aee0  ???????? ???????? ???????? ????????
b914aef0  ???????? ???????? ???????? ????????

BOOL << FHungApp>> (
PTHREADINFO pti,
DWORD dwTimeFromLastRead)
{

/*
* A program is considered to be hung if it is not waiting for input, 
* is not in startup processing, and has not called PeekMessage() 
* within the specified timeout.
*/ 
if (!(pti->ppi->W32PF_Flags & W32PF_APPSTARTING) 
&&    <------the problem occurs here because pti->ppi is invalid
!(pti->pcti->fsWakeMask & (QS_MOUSE | QS_KEY)) &&
((NtGetTickCount() - GET_TIME_LAST_READ(pti)) > dwTimeFromLastRead)) 
{return TRUE;}