Article ID: 165439 - View products that this article applies to.
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 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:
NOTE: The first and fourth parameters will be identical on a single processor x86-based system.
STOP: 0x0000001E (0xC0000028, 0x801327E1, 0x00000000, 0x00000000)
NOTE: The first parameter will be identical on a single processor x86- based system.
STOP: 0x0000007F (0x00000008, 0x00000000, 0x00000000, 0x00000000)
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:
The problem with the above line is that the slash (/) is used instead of the 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 the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/152734/EN-US/ )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 the file is not deleted, the system may become caught in a loop, producing the STOP error each time the file is read while the computer is starting. To correct this problem, the LMHOSTS will need to be deleted or have the incorrect entries edited out. The method used for this will depend on the file system being used on the computer running Windows NT.
Windows NT Installed on FAT DriveIf your computer running Windows NT is FAT-formatted, perform the following steps:
Windows NT Installed on NTFS DriveIf your computer running Windows NT is NTFS-formatted, perform the following steps:
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 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.
Article ID: 165439 - Last Review: February 24, 2014 - Revision: 3.1