"STOP 0x50" Error Message in Mup.sys (241392)

The information in this article applies to:

Microsoft Windows NT Server 4.0 Terminal Server Edition SP4

This article was previously published under Q241392

SYMPTOMS

When a Terminal Server client logs on, the Terminal Server may receive a "STOP 0x50" error message with the following bugcheck data:

0: kd> dd kibugcheckdata l5
dd kibugcheckdata l5
80159ac0 00000050 aa575000 00000000 00000000
80159ad0 00000000

CAUSE

This behavior occurs because the Unicode string that is passed to Wcschr in TranslateClientName is not null-terminated.

RESOLUTION

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

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 Windows NT 4.0 Server, Terminal Server Edition, Service Pack 5.

Modification Type:	Minor	Last Reviewed:	9/23/2005
Keywords:	kbHotfixServer kbQFE kbbug kbfix kbQFE KB241392