Parsing LMHOSTS with Invalid Entries Can Cause Stop 0x1E

This article was previously published under Q165439
This article has been archived. It is offered "as is" and will no longer be updated.
A Windows NT computer that is configured to use an LMHOSTS file may get ablue screen error during the use of the NBTSTAT -R command, and thesubsequent restart of the system. The blue screen error message for thiscondition is:
STOP: 0x0000001E (0xC0000028, 0x801327E1, 0x00000000, 0x00000000)
NOTE: The first and fourth parameters will be identical on a singleprocessor x86-based system.

STOP: 0x0000007F (0x00000008, 0x00000000, 0x00000000, 0x00000000)
NOTE: The first parameter will be identical on a single processor x86-based system.
Improperly formatted syntax in the LMHOSTS file can produce this STOPerror. Below is an example of the specific syntax error that causes theSTOP error:
   #include //severname/share/file				

The problem with the above line is that the slash (/) is used instead ofthe backslash (\).
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 theMicrosoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack

The LMHOSTS file may be deleted by the system during the Stop error. If thefile is not deleted, the system may become caught in a loop, producing theSTOP error each time the file is read while the computer is starting. Tocorrect this problem, the LMHOSTS will need to be deleted or have theincorrect entries edited out. The method used for this will depend onthe file system being used on the computer running Windows NT.

Windows NT Installed on FAT Drive

If your computer running Windows NT is FAT-formatted, perform the followingsteps:
  1. Start the computer to another operating system (such as MS-DOS, Microsoft Windows 95, or Microsoft Windows 3.x).
  2. Delete or edit the incorrect entry from the LMHOSTS file in the Winnt\System32\Drivers\Etc folder.
If you do not have MS-DOS or Windows 95 installed on the Windows NTcomputer (there is no menu option for MS-DOS or Windows 95 on the Startmenu), but Windows NT is installed on a FAT partition, you can boot from anMS-DOS floppy disk or Windows 95 Startup disk and edit or delete theLMHOSTS file on the FAT partition.

Windows NT Installed on NTFS Drive

If your computer running Windows NT is NTFS-formatted, perform thefollowing steps:
  1. Install a parallel copy of Windows NT into a new directory.
  2. Delete or edit the incorrect entry from the LMHOSTS file.
  3. Restart into the original Windows NT installation and delete the parallel installation of Windows NT.
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.

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 testedand should be applied only to systems experiencing this specific problem.Unless you are severely impacted by this specific problem, Microsoftrecommends that you wait for the next Service Pack that contains this fix.Contact Microsoft Technical Support for more information.

Article ID: 165439 - Last Review: 02/24/2014 08:27:45 - Revision: 3.1

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 Standard Edition, Microsoft Windows NT Workstation 3.5, Microsoft Windows NT Workstation 3.51, Microsoft Windows NT Workstation 4.0 Developer Edition

  • kbnosurvey kbarchive kbbug kbfix kbnetwork KB165439