Stop 0x00000050 in Win32k.sys When Changing Keyboard Layout

View products that this article applies to.

This article was previously published under Q252371

SYMPTOMS

When you change the keyboard layout, the following error message in Win32k.sys may be displayed:

Stop 0x00000050 (0xffffff68, 0x0, 0x0, 0x0)

Back to the top

This behavior occurs when a mutex is not obtained before scaling the process/thread list. This allows entries within the list to be changed or removed by a different thread while another thread is scaling the list.

Back to the top

RESOLUTION

Windows NT Server or Workstation 4.0

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:
152734 (http://support.microsoft.com/kb/152734/EN-US/ ) how to obtain the latest windows nt 4.0 service pack

For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS (http://support.microsoft.com/default.aspx?scid=fh;en-us;cntactms)

The English-language version of this fix should have the following file attributes or later:

   Date        Time       Size        File name     Platform
   ---------------------------------------------------------
   01/25/2000  08:05p     2,051,088   Win32k.sys    Alpha
   01/11/2000  08:16p     1,251,152   Win32k.sys    X86

Back to the top

Windows NT Server 4.0, Terminal Server Edition

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 (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 Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT Server 4.0 Service Pack 6 and Windows NT Server 4.0, Terminal Server Edition Service Pack 6.

Back to the top