Multiprocessor Computer May Stop Responding (Hang) Because of Tcpip.sys

• Microsoft Windows NT Workstation version 4.0
• Microsoft Windows NT Server version 4.0
• Microsoft Windows NT Server version 4.0, Terminal Server Edition

SYMPTOMS

A multiprocessor computer running Microsoft Windows NT version 4.0 may appear to stop responding (hang) when subjected to heavy TCP/IP stress. The system will continue to respond to PINGs, but higher level TCP/IP activity will be blocked. If other network protocols are installed, the system may continue to function normally except for activities that depend on TCP/IP.

CAUSE

For this problem to occur, a process must have an open handle to an address and an open handle to a connection and must try to close both simultaneously (as, for example, might happen at process termination). Under very specific and timing-dependent situations, Tcpip.sys can become deadlocked, blocking further work by the driver. When this happens, other parts of the system will typically continue running for a period of minutes or longer until higher level services that depend on Tcpip.sys also become blocked, waiting for the driver.

RESOLUTION

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, please see the following article in the Microsoft Knowledge Base:

Q152734 How to Obtain the Latest Windows NT 4.0 Service Pack

STATUS

Microsoft has confirmed this to be 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.

Additional query words: multi-processor multi processor

Keywords          : kbnetwork NT4SP4Fix kbbug4.00 ntprotocol nttcp kbfix4.00.sp4 NTSrvWkst 
Version           : WinNT:4.0
Platform          : winnt 
Issue type        : kbbug 

Last Reviewed: April 10, 1999