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.
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
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.