Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
STOP 0x0000001E may occur in Win32k.sys under stress
Article ID: 196330 - View products that this article applies to.
This article was previously published under Q196330
Under stress, a computer running Windows NT Server or Workstation may display a STOP 0x0000001E error message on a blue screen. The first parameter is C0000005. This can occur without user activity in the foreground.
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:
Windows NT 4.0, Terminal Server EditionA 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:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMSNOTE: 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: June 11, 2012 - Revision: 3.0