This article was previously published under Q162837
This article has been archived. It is offered "as is" and will no longer be updated.
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 tothe system, when you boot the computer, you receive the following STOPerror:
NOTE: The first argument may change but the STOP code (0x00000050) is thesame in all error messages.
This error only occurs if Remote Access Service is installed and isconfigured to use the TCP/IP protocol as either a dial-in or a dial-outprotocol.
To work around this problem, after adding the TCP/IP protocol back to thesystem, do one of the following:
Reapply SP2 after adding the TCP/IP protocol back to the system, but before rebooting the computer. Click No when you are prompted to reboot, after adding TCP/IP.
After adding the TCP/IP protocol, disable TCP/IP from your RAS configuration and allow the Windows NT computer to reboot. After the computer reboots, reapply SP2 and enable TCP/IP through RAS.
To recover from this error, use the method appropriate to your situation.
Method 1: Windows NT Is on a FAT Partition
If Windows NT is installed on a FAT partition, boot the computer to anotheroperating system (such as MS-DOS, Microsoft Windows 95, or MicrosoftWindows 3.x). Replace the Tcpip.sys file in the \Winnt\System32\Driversfolder with the one from Service Pack 2.
Method 2: Windows NT Is on an NTFS Partition
If Windows NT is installed on an NTFS partition, install a parallel copy ofWindows 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 tothe original Windows NT installation, and then reapply Service Pack 2. Whenyou are done, delete the parallel installation of Windows NT 4.0.
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 wordin the Microsoft Knowledge Base (without the spaces):