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

This article has been archived. It is offered "as is" and will no longer be updated.
Any Windows NT system that contains one or more NetBIOS group namesspecified in the LMHOSTS file may experience a STOP 0xA error message withparameters similar to the following:

Stop 0xA (0000000a 00000000 00000002 00000000)
If a group name is added to the NetBT name cache as a result of the networkactivity of various services before the LMHOSTS file is fully parsed, andthe LMHOSTS file contains a matching group name entry, the systemincorrectly overwrites the cached entry with the LMHOSTS entry. Because itis assumed that the LMHOSTS file only contains unique NetBIOS names and notgroup names, the cached entry is incorrectly treated as unique, causing aSTOP 0xA.
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 theMicrosoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack

Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. 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.
bluescreen blue screen

Article ID: 178113 - Last Review: 01/06/2015 02:36:54 - Revision: 2.0

  • Microsoft Windows NT Workstation 4.0 Developer Edition
  • Microsoft Windows NT Server 4.0 Standard Edition
  • kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbfix KB178113