Windows NT May Fail On Request to Open Large Files

Last reviewed: January 29, 1998
Article ID: Q171458
The information in this article applies to:
  • Microsoft Windows NT Workstation versions 3.51 and 4.0
  • Microsoft Windows NT Server versions 3.51 and 4.0

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

When an application tries to open large files (over 100MB), the open request may fail with one of the following error messages:

  • Insufficient Resources

    - or –

  • Invalid Handle

The actual error returned varies depending on the application being used to open the file.

RESOLUTION

The allocation for paged-pool memory was modified to correct any problem that might occur on systems that have large files (greater 100MB) that are repeatedly opened sequentially, updated, and then closed.

Ntoskrnl.exe and Ntkrnlmp.exe have been updated to correct this problem.

Windows NT 3.51

To resolve this problem on Windows NT 3.51, obtain and install the hotfix. You must restart the computer for the fix to take effect. No registry changes are required on Windows NT 3.51.

Windows NT 4.0

To resolve this problem on Windows NT 4.0, obtain the following fix or wait for the next Windows NT service pack.

The fix should have the following time stamp:

   10/31/97  5:00p               916,352 Ntoskrnl.exe (Intel)
   10/31/97  5:01p               936,064 Ntkrnlmp.exe (Intel)

   10/31/97  2:22p             1,368,128 Ntoskrnl.exe (Alpha)
   10/31/97  2:23p             1,395,456 Ntkrnlmp.exe (Alpha)

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.

  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 DisablePagedPoolHint as the value name and set the Data Type to REG_DWORD.

  4. Click OK and enter 1 as the Data.

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

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 4.0. A supported fix is now available, but has not been fully regression-tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information.

Microsoft has confirmed this to be a problem in Windows NT version 3.51. A fix to this problem is in development, but has not been regression- tested and may be destabilizing in production environments. Microsoft does not recommend implementing this fix at this time. Contact Microsoft Product Support Services for more information on the availability of this fix.


Additional query words: 3.51 4.00
Keywords : kbbug3.51 kbbug4.00 kbfix4.00 ntgeneral NTSrvWkst
Version : WinNT:3.51,4.0
Platform : winnt
Issue type : kbbug
Solution Type : kbpatch


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: January 29, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.