Open Files Can Cause Kernel to Report INSUFFICIENT_RESOURCES

ID: Q192409

The information in this article applies to:
  • Microsoft Windows NT Workstation version 4.0
  • Microsoft Windows NT Server version 4.0
  • Microsoft Windows NT Server version 4.0, Terminal Server Edition
IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.

SYMPTOMS

The problem described in this article is difficult to identify. One way to check for the problem if you suspect you are experiencing it is to calculate the number of files open on the Window NT-based computer, and look at their size. If you have approximately 180 GB of open files that are not being closed continuously or are opened and closed rapidly in a looping condition, you may be experiencing this problem. Also, your programs may be receiving an INSUFFICIENT_RESOURCES error message when attempting to open, create, or extend a file.

This problem is intermittent. If you try the operation again it is possible for it to succeed. This occurs because it is possible to have a program create and close files faster than Windows NT can clean up. When this occurs it is possible for the program to succeed if retried.

One method that can be used to identify the problem is to start Task Manager and click the Performance tab. At the bottom, locate the Kernel Memory section and watch the value for Paged Memory. You may experience the problem when that value reaches approximately 190. If this value goes back down immediately, you should be able to retry the operation that caused the error message and have it succeed if the system has enough resources to fulfill the program's request.


RESOLUTION

Install the following files and set the following registry entry.

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, please see the following article in the Microsoft Knowledge Base:

Q152734 How to Obtain the Latest Windows NT 4.0 Service Pack

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT, you should also update your Emergency Repair Disk (ERD).

  1. Start Registry Editor, locate and select the following Registry subkey in the HKEY_LOCAL_MACHINE subtree:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
    \Session Manager\Memory Management

    NOTE: The above registry key is one path; it has been wrapped for readability.


  2. From the Edit menu, click Add Value.


  3. Enter UnusedFileCache as the value name and set the Data Type to REG_DWORD.


  4. Click OK and enter a value of 0 or 5-40 as the data.

    0 = Default behavior similar to Windows NT 4.0 Service Pack 3.
    5 - 40 Trim unused file cache based on pool usage.
    It represents the percent of pool that we allow to be consumed by unused segments. Where 5 is most aggressive. (For example, it increases the size of the cache the least ) and 40 is least aggressive. (For example, lets the cache grow to the largest before trimming) .

    Internal testing found that this fix has positive benefits in that it also increases the performance of some applications such as IIS. It works best when set to 15-20. Do not choose a value greater than 20 without extensive stress testing.


  5. Click OK, quit Registry Editor, and then shut down and restart the computer.


For additional information, please see the following article in the Microsoft Knowledge Base:

Q171458 Windows NT May Fail On Request to Open Large Files
The solution to this issue also tends to improve performance of the computer.


STATUS

Microsoft has confirmed this to be a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.

Additional query words:

Keywords : NT4SP4Fix kbbug4.00 kbfix4.00.sp4
Version : winnt:4.0
Platform : winnt
Issue type : kbbug


Last Reviewed: July 8, 1999
© 2000 Microsoft Corporation. All rights reserved. Terms of Use.