Stop 0x0000000A in NETBT.SYS After Applying Service Pack 2

Last reviewed: May 20, 1997
Article ID: Q164904

The information in this article applies to:

Microsoft Windows NT Workstation version 4.0 Service Pack 2
Microsoft Windows NT Server version 4.0 Service Pack 2

SYMPTOMS

A Windows NT server may blue screen with the following during a name query

   Stop 0x0000000a (0x00000051, 0x00000002, 0x00000000, 0xf62422c4)

NOTE: The fourth parameter within parenthesis is machine specific and may vary. The memory range will fall in Netbt.sys.

CAUSE

When doing a proxy name query, the machine bugchecks since it accesses the tracker flag, but the tracker is NULL.

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 4.0. This problem was corrected in the latest Microsoft Windows NT 4.0 U.S. Service Pack. For information on obtaining the service pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

Additional query words: resolution wins dns 4.00 prodnt
Keywords : kbbug4.00 kbfix4.00 kbfix4.00.sp2 ntdriver NTPROTOCOL NTSrvWkst ntstop kbnetwork kbbuglist kbfixlist
Version : 4.0
Platform : winnt
Hardware : ALPHA x86
Issue type : kbbug
Solution Type : kbservicepack

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: May 20, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.