Parsing LMHOSTS with Invalid Entries Can Cause Stop 0x1E (165439)
The information in this article applies to:
- Microsoft Windows NT Server 4.0 Terminal Server Edition
- Microsoft Windows NT Server 3.5
- Microsoft Windows NT Server 3.51
- Microsoft Windows NT Server 4.0
- Microsoft Windows NT Workstation 3.5
- Microsoft Windows NT Workstation 3.51
- Microsoft Windows NT Workstation 4.0
This article was previously published under Q165439 SYMPTOMS
A Windows NT computer that is configured to use an LMHOSTS file may get a
blue screen error during the use of the NBTSTAT -R command, and the
subsequent restart of the system. The blue screen error message for this
condition is:
STOP: 0x0000001E (0xC0000028, 0x801327E1, 0x00000000, 0x00000000)
KMODE_EXCEPTION_NOT_HANDLED
NOTE: The first and fourth parameters will be identical on a single
processor x86-based system.
-or-
STOP: 0x0000007F (0x00000008, 0x00000000, 0x00000000, 0x00000000)
UNEXPECTED_KERNEL_MODE_TRAP
NOTE: The first parameter will be identical on a single processor x86-
based system.
CAUSE
Improperly formatted syntax in the LMHOSTS file can produce this STOP
error. Below is an example of the specific syntax error that causes the
STOP error:
#include //severname/share/file
The problem with the above line is that the slash (/) is used instead of
the backslash (\).
RESOLUTION
To work around this problem, correctly format the LMHOSTS file.
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
STATUSMicrosoft 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.
Microsoft has confirmed this to be a problem in Windows NT version 3.51.
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.
Modification Type: | Major | Last Reviewed: | 6/30/2004 |
---|
Keywords: | kbbug kbfix kbnetwork KB165439 |
---|
|