Windows 2000 Server stops responding if the TCPDispatch function returns an incorrect status for the IRP

This article has been archived. It is offered "as is" and will no longer be updated.
Occasionally, your computer that is running Microsoft Windows 2000 Server stops responding. If you turn on the Driver Verifier utility to troubleshoot the issue, you receive bug check error messages that are similar to the following:
DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)The IO manager has caught a misbehaving driver.Arguments:Arg1: 00000224, (Fatal error) An IRP dispatch handler has returned a status that is inconsistentwith the IRP's IoStatus.Status field. (Dispatch handler routine, IRP, IRP'sIoStatus.Status, and returned Status specified.)Arg2: afada654Arg3: b3890f68Arg4: 00000000
This problem may occur if the correct status is not returned for the input/output request packet (IRP) by the TCPDispatch() function call.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.


This hotfix requires Windows 2000 Service Pack 3 or later.

Restart requirement

You must restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date         Time   Version            Size    File name   --------------------------------------------------------------   12-Dec-2003  17:11  5.0.2195.6882     118,960  Afd.sys   10-Mar-2004  17:33  5.0.2195.6824     105,232  Msafd.dll           09-Mar-2004  23:44  5.0.2195.6905     314,928  Tcpip.sys   12-Dec-2003  17:08  5.0.2195.6882      16,240  Tdi.sys   10-Mar-2004  17:33  5.0.2195.6824      17,680  Wshtcpip.dll   
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For additional information about the Driver Verifier utility, click the following article number to view the article in the Microsoft Knowledge Base:
244617 How to use Driver Verifier to troubleshoot device drivers in Windows 2000
For additional information about how hotfix packages are named, click the following article numbers to view the articles in the Microsoft Knowledge Base:
816915 New file naming schema for Microsoft Windows hotfix packages
824684 Description of the standard terminology that is used to describe Microsoft software updates

Article ID: 837771 - Last Review: 10/26/2013 20:57:28 - Revision: 2.5

Microsoft Windows 2000 Server, Microsoft Windows 2000 Advanced Server

  • kbnosurvey kbarchive kbautohotfix kbhotfixserver kbqfe kbbug kbfix kbqfe kbwin2000presp5fix KB837771