While you are installing the Windows operating system, your computer may stop responding (hang) while displaying the following error message on a blue screen:
This error message may be caused by faulty memory (RAM) in your computer.
To resolve this issue, replace the faulty RAM.
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:
- 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
If you can successfully install Windows 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.
- Temporarily replace your video adapter. If you can install Windows
after replacing the video adapter, the video adapter you replaced
- 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 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.
For additional information about the error message listed above, see the
following articles in the Microsoft Knowledge Base:
Possible Resolutions to STOP 0x0A, 0x01E, and 0x50 Errors
"Stop 0x50" Transferring Files over RAS with Windows NT 4.0
Network Virus Checking Programs and Microsoft Windows NT
Replacing TCP/IP After SP2 Causes STOP 0x00000050
STOP 0x1E or 0x50 Error on Multiprocessor DEC Alpha Computer
Stop 0x00000050 in Tcpip.sys Caused by Winsock Applications
STOP 0x00000050 in Srv.sys When Shutting Down Computer
STOP 0x50 in Rdr.sys If Pathname Too Long in SMB
"STOP 0x50" Accessing Files on Windows NT from Windows 95
Stop Screen 0x00000050 Caused by Fs_rec.sys
Stop 0x00000050 with S3 Video
New Installation of Windows NT 4.0 Results in STOP 0x00000050
Upgrade Installation of Windows NT 4.0 Results In STOP Errors