"Stop 0x50" Error Message While Installing Windows NT 4.0

• Microsoft Windows NT Server version 4.0
• Microsoft Windows NT Workstation version 4.0

SYMPTOMS

While you are installing Windows NT 4.0, your computer may stop responding (hang) while displaying the following error message on a blue screen:

   STOP: 0x00000050
   PAGE_FAULT_IN_NONPAGED_AREA

CAUSE

This error message may be caused by faulty memory (RAM) in your computer.

RESOLUTION

To resolve this issue, replace the faulty RAM.

MORE INFORMATION

The faulty RAM could be located in any of several areas, including the secondary RAM cache, the video RAM, or the computer's main memory. To determine where the faulty RAM is located, use the following steps:

1. Disable all caching on your computer, including the CPU cache and L2 cache, in the computer's CMOS settings. For information about how to use your computer's CMOS configuration tool, please refer to your computer's documentation.

   If you can successfully install Windows NT after disabling all caching, try re-enabling each cache, one at a time, to determine the area in which the faulty RAM is located. If you still receive the error message, continue to the next step.

2. Temporarily replace your video adapter. If you can install Windows NT after replacing the video adapter, the video adapter you replaced is faulty.

3. Temporarily replace the main memory installed in your computer. If the RAM in your computer consists of multiple SIMM modules, you may be able to swap SIMM modules to determine which has the faulty memory.

   For example, if you have four modules of 8 megabytes (MB) each, remove two of the modules and try installing Windows NT again. If the Setup process still does not succeed, swap one of the SIMMs in the computer with one that you removed and try again. Continue this process to determine which of the SIMM modules contains the faulty memory.

   ARTICLE-ID: Q155573
   TITLE     : "Stop 0x50" Transferring Files over RAS with Windows NT 4.0

   ARTICLE-ID: Q156211
   TITLE     : Network Virus Checking Programs and Microsoft Windows NT

   ARTICLE-ID: Q162837
   TITLE     : Replacing TCP/IP After SP2 Causes STOP 0x00000050

   ARTICLE-ID: Q156410
   TITLE     : STOP 0x1E or 0x50 Error on Multiprocessor DEC Alpha
               Computer

   ARTICLE-ID: Q164352
   TITLE     : Stop 0x00000050 in Tcpip.sys Caused by Winsock Applications

   ARTICLE-ID: Q167362
   TITLE     : STOP 0x00000050 in Srv.sys When Shutting Down Computer

   ARTICLE-ID: Q163620
   TITLE     : STOP 0x50 in Rdr.sys If Pathname Too Long in SMB

   ARTICLE-ID: Q162438
   TITLE     : "STOP 0x50" Accessing Files on Windows NT from Windows 95

   ARTICLE-ID: Q160370
   TITLE     : Stop Screen 0x00000050 Caused by Fs_rec.sys