Knowledge Base

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

Article ID: 837771

Article Last Modified on 10/26/2006

APPLIES TO

Microsoft Windows 2000 Server
Microsoft Windows 2000 Advanced Server

SYMPTOMS

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 inconsistent
with the IRP's IoStatus.Status field. (Dispatch handler routine, IRP, IRP's
IoStatus.Status, and returned Status specified.)
Arg2: afada654
Arg3: b3890f68
Arg4: 00000000

CAUSE

This problem may occur if the correct status is not returned for the input/output request packet (IRP) by the TCPDispatch() function call.

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

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

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

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

Additional query words: Stop

Keywords: kbhotfixserver kbqfe kbbug kbfix kbqfe kbwin2000presp5fix KB837771

Microsoft KB Archive/837771

Contents