STOP 0x0000001E may occur in Win32k.sys under stress

This article has been archived. It is offered "as is" and will no longer be updated.
Under stress, a computer running Windows NT Server or Workstation maydisplay a STOP 0x0000001E error message on a blue screen. The firstparameter is C0000005. This can occur without user activity in theforeground.
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:
For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

Windows NT 4.0, Terminal Server Edition

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix should have the following file attributes or later:
  Date       Time      Size       File Name   --------------------------------------------- 03/27/2001  10:20a    170,256    Gdi32.dll 07/11/2000  03:44p    331,536    User32.dll 09/07/2001  08:46a  1,279,920    Win32k.sys 08/03/2001  11:38a    195,856    Winsrv.dll					

Microsoft has confirmed this to be a problem in Windows NT version 4.0. This problem was first corrected in Windows NT version 4.0 Service Pack 5.

Article ID: 196330 - Last Review: 01/10/2015 11:38:39 - Revision: 6.0

Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Server 4.0 Standard Edition, Microsoft Windows NT Server 4.0 Enterprise Edition

  • kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbfix KB196330