"Stop 0x50" Occurs in win32k!GreExtSelectClipRgn() in Windows NT 4.0 Terminal Server Edition (316764)



The information in this article applies to:

  • Microsoft Windows NT Server 4.0 Terminal Server Edition

This article was previously published under Q316764

SYMPTOMS

You may receive a "Stop 0x50" error message on a blue screen in Windows NT Server 4.0, Terminal Server Edition.

RESOLUTION

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date         Time   Version         Size       File name
   ---------------------------------------------------------
   27-Mar-2001  09:20  4.0.1381.33476    170,256  Gdi32.dll
   11-Jul-2000  14:44  4.0.1381.33392    331,536  User32.dll
   07-Feb-2002  16:20  4.0.1381.33524  1,279,664  Win32k.sys
   03-Aug-2001  10:38  4.0.1381.33478    195,856  Winsrv.dll
				
NOTE: Because of file dependencies, this hotfix requires Microsoft Windows NT 4.0 Service Pack 6a.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Modification Type:MinorLast Reviewed:9/27/2005
Keywords:kbHotfixServer kbQFE kbbug kbfix kbQFE kbWinNT400nospFix KB316764