Err Msg: STOP 0x0000001e {0xc000005, 0xa1000aa7, 0x0, 0x00440194} in Win32k.sys

ID: Q224982

The information in this article applies to:

SYMPTOMS

When the process ID (PID) of any given process exceeds 65,535 bytes, Win32k.sys generates the following blue screen error message:

STOP 0x0000001e {0xc000005, 0xa1000aa7, 0x00000000, 0x00440194}
NOTE: The first parameter will always be 0xc0000005 and the second parameter will always fall within the memory range of Win32k.sys.


CAUSE

When a process terminates, Win32k.sys must release structures allocated by that process. Win32k.sys tracks these structures by PID number. The driver Win32k.sys only supports PID numbers less than 65,535 bytes.

This problem occurs because a program is not releasing thread handles. When a thread is created, a handle is allocated out of the system handle table as well as the process handle table. This system handle table is the same handle table process IDs come from. This can drive the process ID numbers greater than 65,000 bytes.


RESOLUTION

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next Windows NT 4.0 service pack that contains this fix.

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 on support costs, please go to the following address on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp
The English version of this fix should have the following file attributes or later:

   Date      Time    Size        File name      Platform
   ------------------------------------------------
   3/30/99   9:30p   948,672     Ntkrnlmp.exe   x86
   3/30/99   9:23p   928,640     Ntoskrnl.exe   x86

   3/30/99   9:22p   1,414,80    Ntkrnlmp.exe   Alpha
   3/30/99   9:21p   1,385,664   Ntoskrnl.exe   Alpha

NOTE: If this product was already installed on your computer when you purchased it from the Original Equipment Manufacturer (OEM) and you need this fix, please call the Pay Per Incident number listed on the above Web site. If you contact Microsoft to obtain this fix, and if it is determined that you only require the fix you requested, no fee will be charged. However, if you request additional technical support, and if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support, you may be charged a non-refundable fee.

For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base:
Q154871 Determining If You Are Eligible for No-Charge Technical Support


STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article.


MORE INFORMATION

After you install the hotfix, if you attempt to create a process with an ID greater than 64,000 bytes, the following pop-up error message is displayed and the process create does not work:

Initialization of the dynamic link library USER32.DLL failed. The process is terminating abnormally.
To find the process that is not releasing thread handles, use Performance Monitor to find a process with a high handle count.

Additional query words: 


Keywords          : kbbug4.00 kbfix4.00 
Version           : winnt:4.0,4.0 SP4
Platform          : winnt 
Issue type        : kbbug

Last Reviewed: July 2, 1999