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

ID: Q177245

The information in this article applies to:

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

Windows NT 4.0

To resolve this problem, obtain the latest service pack for Windows NT 4.0. 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

NOTE: This hotfix is superseded by the fix referred to in the following article in the Microsoft Knowledge Base:

Q179129 STOP 0x0000000A or 0x00000019 Due to Modified Teardrop Attack

Windows NT Server 4.0, Terminal Server Edition

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next Windows NT Server 4.0, Terminal Server Edition service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp

The English version of this fix should have the following file attributes or later:


   Date      Time                 Size    File name     Platform
   -------------------------------------------------------------
   07/21/99  05:13p             147,920   Tcpip.sys     x86
   07/21/99  04:05p             269,648   Tcpip.sys     Alpha

STATUS

Windows NT 4.0

Microsoft has confirmed this to be a problem in Windows NT 4.0. This problem was first corrected in Windows NT 4.0 Service Pack 4.

Windows NT Server 4.0, Terminal Server Edition

Microsoft has confirmed this to be a problem in Windows NT Server 4.0, Terminal Server Edition.

Additional query words: multi-processor multi processor

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