Microsoft KB Archive/817864

From BetaArchive Wiki

Article ID: 817864

Article Last Modified on 10/26/2006



APPLIES TO

  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Service Pack 1
  • Microsoft Windows 2000 Service Pack 2
  • Microsoft Windows 2000 Service Pack 3
  • Microsoft Windows 2000 Service Pack 1
  • Microsoft Windows 2000 Service Pack 2
  • Microsoft Windows 2000 Service Pack 3



SYMPTOMS

After you exit from the Network Monitor program, your computer may stop responding (hang), and you may receive the following error message on a blue screen:

STOP 0x000000d1 (0x00000000,0x00000002,0x00000000,0xF9C8D886)

Note The last parameter of the stop code may differ.

CAUSE

This problem may occur if Network Monitor's protocol driver, Nmnt.sys, is unloaded under certain circumstances.
Some network adapter miniports or Network Driver Interface Specification (NDIS) intermediate drivers send the status message of "NDIS_STATUS_CLOSING" to bound protocols when shutting down. This NDIS status causes Network Monitor's protocol driver to fail with the bugcheck error: DRIVER_IRQL_NOT_LESS_OR_EQUAL (0xd1)

Network adapter miniports or NDIS drivers do not have to indicate NDIS_STATUS_CLOSING, and when possible, drivers that do so must be corrected. However, in those scenarios where this cannot be done, this hotfix contains a replacement Network Monitor protocol driver that can correctly handle this status.

RESOLUTION

Service Pack Information

To resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

260910 How to Obtain the Latest Windows 2000 Service Pack


Hotfix Information

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Windows 2000 service pack that contains this hotfix.

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 about support costs, visit the following Microsoft Web site:

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 typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.


The English version of this fix 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
   --------------------------------------------------------------
   01-Apr-2003  20:32  5.0.2195.6699      37,552  Nmnt.sys


                



STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Windows 2000 Service Pack 4.

MORE INFORMATION

For additional information about how to obtain a hotfix for Windows 2000 Datacenter Server, click the article number below to view the article in the Microsoft Knowledge Base:

265173 The Datacenter Program and Windows 2000 Datacenter Server Product


Keywords: kberrmsg kbbug kbfix kbwin2000presp4fix kbqfe kbddk kbprb kbwin2ksp4fix kbhotfixserver KB817864