STOP 0x78 When NonPagedPoolSize > Seven-eighths of Physical Memory

This article was previously published under Q184758
This article has been archived. It is offered "as is" and will no longer be updated.

IMPORTANT: This article contains information about editing the registry.Before you edit the registry, make sure you understand how to restore it ifa problem occurs. For information on how to do this, view the "Restoringthe Registry" online Help topic in Regedit.exe or the "Restoring a RegistryKey" online Help topic in Regedt32.exe.
You may receive a STOP 0x00000078 if the NonPagedPoolSize registry settingis more than seven-eighths of physical memory.
To work around this problem, change the registry setting so that theNonPagedPoolSize value is less than seven-eighths of physical memory.

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

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

  1. Run Registry Editor and open the following key:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control \Session Manager\Memory Manageme

    NOTE: The above registry key is one path; it has been wrapped for readability.
  2. Change NonPagedPoolSize to less than seven-eighths of the physical memory.
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 theMicrosoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack

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

Article ID: 184758 - Last Review: 10/07/2013 22:57:34 - Revision: 1.1

Microsoft Windows NT Server 4.0, Terminal Server Edition, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Server 4.0 Standard Edition

  • kbnosurvey kbarchive kbbug kbfix kbqfe kbwinnt400sp4fix KB184758