STOP: 0x0000001E with Status C000009A

This article was previously published under Q163143
This article has been archived. It is offered "as is" and will no longer be updated.
Symptoms
When you run some programs, you may receive the following error message:
STOP: 0x0000001E : (0xC000009A, xxxxxxxx, xxxxxxxx, xxxxxxxx)
KMODE_EXCEPTION_NOT_HANDLED
Cause
This behavior can occur when you run a program that puts a high number oflocks on a file. To hold locks, the file system allocates memory from theNonPagedPool. If the NonPagedPool is exhausted, critical allocationsrequested by other system components cannot be satisfied, generating theSTOP error message.
Status
Microsoft has confirmed this to be a problem in Windows NT version 3.51.We are researching this problem and will post new information here as itbecomes available.

Microsoft has confirmed this to be a problem in 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 thefollowing word in the Microsoft Knowledge Base (without the spaces):
S E R V P A C K
More information
The size of the NonPagedPool is calculated in proportion to the amount ofphysical RAM in the computer. The number of possible locks is directlyrelated to the size of the NonPagedPool. For example, on a computer with32 MB of RAM, this behavior has been noted after more than 160,000 locksare set.

To correct this problem, Windows NT now reports an error to the programthat is issuing the locks.
3.51 4.00 0x1e
Properties

Article ID: 163143 - Last Review: 10/26/2013 01:47:00 - Revision: 2.0

  • Microsoft Windows NT Server 3.51
  • Microsoft Windows NT Server 4.0 Standard Edition
  • Microsoft Windows NT Workstation 3.51
  • Microsoft Windows NT Workstation 4.0 Developer Edition
  • kbnosurvey kbarchive kbnetwork KB163143
Feedback