The information in this article applies to:
SYMPTOMSIt 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. S E R V P A C K Additional query words: prodnt
Keywords : kb3rdparty kbbug4.00 kbfix4.00.sp2 nt32ap NTSrvWkst |
Last Reviewed: February 2, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |