"STOP 0x50" Error Message in Mup.sys

• Microsoft Windows NT Server versions 4.0, 4.0 SP4, Terminal Server Edition

SYMPTOMS

When a Terminal Server client logs on, the client 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, please see the following article in the Microsoft Knowledge Base:

Q152734 How to Obtain the Latest Windows NT 4.0 Service Pack

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. This problem was first corrected in Windows NT 4.0 Server, Terminal Server Edition, Service Pack 5.

Additional query words:

Keywords : kbbug4.00 kbfix4.00
Version : winnt:4.0,4.0 SP4
Platform : winnt
Issue type : kbbug