Article ID: 250560
Article Last Modified on 11/1/2006
APPLIES TO
- Microsoft Windows NT Server 4.0, Terminal Server Edition
This article was previously published under Q250560
SYMPTOMS
The Terminal Server randomly stops responding (hang) and you receive the following error message on a blue screen:
CAUSE
The error actually occurs when a Terminal Server client is logging off a session. Terminal Server is trying to access the client's System Tray window despite the fact that it has already been closed.
RESOLUTION
To resolve this problem, obtain the latest service pack for Windows NT Server version 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack
STATUS
This problem was first corrected in Windows NT Server version 4.0, Terminal Server Edition Service Pack 6.
MORE INFORMATION
The stack trace from this hang looks something like this:
bd1d3d78 a304f6b0 a414cb88 0000019a a5081338 win32k!IsTrayWindow+0x40
bd1d3dbc a30292e7 a414cb88 e2893b68 a3054573 win32k!xxxDestroyWindow+0x233
bd1d3dc8 a3054573 a5081338 e2893c08 e2893b68 win32k!HMDestroyUnlockedObject+0x6f
bd1d3ddc a3054961 bd1d3e08 807b1184 00000000 win32k!DestroyThreadsObjects+0xa2
bd1d3df4 a3053865 807b1184 00000001 a305374a win32k!xxxDestroyThreadInfo+0x141
bd1d3e08 a30537b3 e2893b68 00000001 e2893b68 win32k!UserThreadCallout+0xad
bd1d3e1c 801a38cd e2893b68 00000001 807b1184 win32k!W32pThreadCallout+0x29
bd1d3ea4 801a35f8 00000000 82c7d608 8011c38d ntkrnlmp!PspExitThread+0x253
bd1d3eb0 8011c38d 82c7d608 bd1d3ee8 bd1d3ee4 ntkrnlmp!PsExitSpecialApc+0x1a
bd1d3eec 801475a4 00000001 00000000 bd1d3f04 ntkrnlmp!KiDeliverApc+0x181
bd1d3eec 77ee199f 00000001 00000000 bd1d3f04 ntkrnlmp!KiServiceExit+0x59
bd1d3d78 a304f6b0 a414cb88 0000019a a5081338 +0x77ee199f
The bottom of the stack may be different, but the problem always occurs in win32k!IsTrayWindow.
Keywords: kbhotfixserver kbqfe kbbug kbfix KB250560
