Continuous Bhnt.sys Load and Unload Causes STOP 0xA and 0x7F (172762)
The information in this article applies to:
- Microsoft Windows NT Server 4.0 Terminal Server Edition
- Microsoft Windows NT Workstation 4.0
- Microsoft Windows NT Server 4.0
This article was previously published under Q172762 SYMPTOMS
You may receive one of the following STOP error messages in Windows NT:
0x0000000A (0x00000003, 0x0000001c, 0x00000000, 0x00000003)
NOTE: The parameters may vary.
0x0000007F (0x0000008, 0x0000000, 0x00000000, 0x00000000)
NOTE: The parameters will appear as above.
0x0000001e (c0000005 f1f733f7 00000000 0000000c)
NOTE: The third parameter will be different and is dependent on system
configurations.
CAUSE
This problem is caused by drivers that load Bhnt.sys, or services that
cause Bhnt.sys to be loaded, to get the network counters, and then unload
it. If this happens continuously, a corruption may occur in the unloading
of Bhnt.sys.
RESOLUTION
To resolve this problem, do any one of the following:
- Obtain the latest version of Compaq Insight Management Agents for
Windows NT from Compaq, if applicable.
- Configure BH Service (Network Monitor Agent Driver) to load at system
startup.
- 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, click the following article number to view the article in the
Microsoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack
STATUS
Microsoft has confirmed this to be a problem in the Network Monitor Agent
Driver. 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.MORE INFORMATION
Compaq Insight Manager is manufactured by Compaq, a vendor independent of
Microsoft; we make no warranty, implied or otherwise, regarding this
product's performance or reliability.
| Modification Type: | Minor | Last Reviewed: | 9/23/2005 |
|---|
| Keywords: | kbHotfixServer kbQFE kbbug kbfix kbWinNT400sp4fix KB172762 |
|---|
|