Bad Parameters Sent to Win32k.sys May Cause Stop Message (160601)
The information in this article applies to:
- Microsoft Windows NT Workstation 4.0
- Microsoft Windows NT Server 4.0
This article was previously published under Q160601 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):
Modification Type: | Major | Last Reviewed: | 8/10/2001 |
---|
Keywords: | kbother kbProgramming kbui KB160601 |
---|
|