"STOP 0x50" Error Message in Mup.sys

View products that this article applies to.

This article was previously published under Q241392

Expand all | Collapse all

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

Back to the top

CAUSE

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

Back to the top

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 (http://support.microsoft.com/kb/152734/EN-US/ ) How to Obtain the Latest Windows NT 4.0 Service Pack

Back to the top

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.

Back to the top