Article ID: 162837 - Last Review: November 1, 2006 - Revision: 1.1 Replacing TCP/IP After SP2 Causes STOP 0x00000050This article was previously published under Q162837 On This PageSYMPTOMS
On a Windows NT 4.0 computer that previously had Service Pack 2 (SP2)
installed, if you remove the TCP/IP protocol, and then later add TCP/IP to
the system, when you boot the computer, you receive the following STOP
error:
STOP 0x00000050 (0xFF10c004, 0x0, 0x0, 0x0) PAGE_FAULT_IN_NONPAGED_AREA
STOP 0x00000050 (0xFF404004, 0x0, 0x0, 0x0) PAGE_FAULT_IN_NONPAGED_AREA
STOP 0x00000050 (0xA0133004, 0x0, 0x0, 0x0) PAGE_FAULT_IN_NONPAGED_AREA
CAUSE
This error only occurs if Remote Access Service is installed and is
configured to use the TCP/IP protocol as either a dial-in or a dial-out
protocol.
WORKAROUND
To work around this problem, after adding the TCP/IP protocol back to the
system, do one of the following:
Method 1: Windows NT Is on a FAT PartitionIf Windows NT is installed on a FAT partition, boot the computer to another operating system (such as MS-DOS, Microsoft Windows 95, or Microsoft Windows 3.x). Replace the Tcpip.sys file in the \Winnt\System32\Drivers folder with the one from Service Pack 2.Method 2: Windows NT Is on an NTFS PartitionIf Windows NT is installed on an NTFS partition, install a parallel copy of Windows NT 4.0 in a new directory. Replace the Tcpip.sys file in the \Winnt\System32\Drivers folder with the one from Service Pack 2. Reboot to the original Windows NT installation, and then reapply Service Pack 2. When you are done, delete the parallel installation of Windows NT 4.0.STATUS
Microsoft has confirmed this to be a problem in Windows NT version 4.0.
This problem was corrected in the latest Windows NT 4.0 U.S. Service Pack.
For information on obtaining the Service Pack, query on the following word
in the Microsoft Knowledge Base (without the spaces):
S E R V P A C K
| Article Translations
|
Back to the top
