Windows NT May Fail On Request to Open Large Files

When an application tries to open large files (over 100MB), the open request may fail with one of the following error messages: - or - The actual error returned varies depending on the application being used to open the file.

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, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

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.

Microsoft has confirmed that this is 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.

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.