Specifying a Group Name in LMHOSTS File May Cause STOP 0xA

Last reviewed: December 15, 1997
Article ID: Q178113
The information in this article applies to:
  • Microsoft Windows NT Workstation version 4.0
  • Microsoft Windows NT Server version 4.0

SYMPTOMS

Any Windows NT system that contains one or more NetBIOS group names specified in the LMHOSTS file may experience a STOP 0xA error message with parameters similar to the following:

   Stop 0xA (0000000a 00000000 00000002 00000000)

CAUSE

If a group name is added to the NetBT name cache as a result of the network activity of various services before the LMHOSTS file is fully parsed, and the LMHOSTS file contains a matching group name entry, the system incorrectly overwrites the cached entry with the LMHOSTS entry. Because it is assumed that the LMHOSTS file only contains unique NetBIOS names and not group names, the cached entry is incorrectly treated as unique, causing a STOP 0xA.

RESOLUTION

To resolve this problem, remove all group entries from the LMHOSTS file, obtain the following fix, or wait for the next Windows NT service pack.

This fix should have the following time stamp:

   11/13/97  16:21               120,656 Netbt.sys (Intel)
   11/13/97  13:16               217,744 Netbt.sys (Alpha)

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 4.0. A supported fix is now available, but has not been fully regression tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information.


Additional query words: bluescreen blue screen
Keywords : kbbug4.00 kbfix4.00 NTSrvWkst ntstop
Version : WinNT:4.0
Platform : winnt
Issue type : kbbug
Solution Type : kbpatch


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: December 15, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.