Microsoft KB Archive/253215

From BetaArchive Wiki
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
Knowledge Base


STOP 0x00000050 Error Message in Windows Terminal Server

Article ID: 253215

Article Last Modified on 2/28/2007



APPLIES TO

  • Microsoft Windows NT Server 4.0, Terminal Server Edition Service Pack 4
  • Microsoft Windows NT Server 4.0, Terminal Server Edition Service Pack 5
  • Microsoft Windows NT Server 4.0, Terminal Server Edition Service Pack 6



This article was previously published under Q253215

SYMPTOMS

When you try to use Terminal Server on your Windows NT 4.0-based computer, you may receive a stop 0x00000050 error message on a blue screen. Also, the bug check information displayed may look similar to the following:

BugCheckCode . . . . .0x00000050
BugCheckParameter1 . .0xfffffffb
BugCheckParameter2 . .0x00000000
BugCheckParameter3 . .0x00000000
BugCheckParameter4 . .0x00000000

ExceptionCode. . . . .0x80000003
ExceptionFlags . . . .0x00000001
ExceptionAddress . . .0x801325ec
                

CAUSE

Many applications can cause this program to stop responding. One known cause is if you have Microsoft Outlook 97 or Microsoft Outlook 98 installed, and a large number of appointment reminders in your calendar.

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.

Keywords: kbhotfixserver kbqfe kbbug kberrmsg kbfix kbinterop KB253215