Win32k.sys Causes STOP 0x0000001e and 0x0000000a On SMP

Last reviewed: February 19, 1998
Article ID: Q175687

The information in this article applies to:

Microsoft Windows NT Workstation version 4.0
Microsoft Windows NT Server version 4.0

SYMPTOMS

Programs that launch and terminate GUI frequently, when running on multiprocessors computers, will cause Windows NT 4.0 to encounter either of the following STOP blue screens:

   STOP 0x0000001e (0xc0000005, 0xa00f7538, 0x00000000, 0x00000008)
   KMODE_EXCEPTION_NOT_HANDLED

   -or-

   STOP 0x0000000a(0x00000004, 0x0000001c, 0x00000000, 0x801175db)
   IRQL_NOT_LESS_OR_EQUAL

CAUSE

The thread object reference count was broken due to a threadlockobject instruction within Win32k.sys that was not multiprocessor safe.

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 4.0. A supported fix is now available, but has not been fully regression tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information.

Keywords          : kbbug4.00 kbfix4.00 ntmp NTSrvWkst ntstop kbfixlist
Version           : WinNT:4.0
Platform          : winnt
Hardware          : ALPHA x86
Solution Type     : kbfix kbpatch kbservicepack

================================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: February 19, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.