Possible Access Violation in Win32k.sys Under High Stress (160678)
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 Q160678 SYMPTOMS
It is possible for an application that is doing intensive screen output to
generate an access violation in WIN32K. This may result in the system
crashing with a STOP 0x0000001E error message.
CAUSE
There is a problem in a GDI text handling function that can cause WIN32K to
reference an invalid memory address.
STATUS
Microsoft has confirmed this to be a problem in Microsoft Windows NT
version 4.0.
This problem was corrected in the latest Microsoft Windows NT 4.0 U.S.
Service Pack. For information on obtaining the service pack, query on the
following word in the Microsoft Knowledge Base (without the spaces):
Modification Type: | Major | Last Reviewed: | 8/10/2001 |
---|
Keywords: | kb3rdparty KB160678 |
---|
|