Bad Parameters Sent to Win32k.sys May Cause Stop Message

Last reviewed: August 13, 1997
Article ID: Q160601

The information in this article applies to:

Microsoft Windows NT Workstation versions 4.0
Microsoft Windows NT Server versions 4.0

SYMPTOMS

It is possible for an errant application to pass a bad parameter to a WIN32K function and cause Win32k.sys to have an access violation. This violation will usually result in Windows NT crashing with a STOP 0x0000001E blue screen error.

CAUSE

Not all of the WIN32K functions were correctly checking parameters for validity before processing them.

RESOLUTION

Install Windows NT 4.0 Service Pack 2.

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 4.0. This problem was corrected in the latest US Service Pack for Windows NT. For information on obtaining this update, query on the following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

Additional query words: prodnt crash ntcrash
Keywords : kbbug4.00 kbfix4.00.sp2 nt32ap ntstop ntui kbother kbprg kbui
Version : 4.0
Platform : winnt

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: August 13, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.