Serial Mouse Not Installed; Err Msg: STOP 0x0000001E

This article was previously published under Q149983
This article has been archived. It is offered "as is" and will no longer be updated.
SYMPTOMS
After you change the OverrideHardwareBitstring in the registry, theserial mouse is not installed during the boot process and the followingSTOP error message appears in Windows NT:
STOP: 0x0000001E : (C0000005, 80118C84, 00000000, 0061008C)
KMODE_EXCEPTION_NOT_HANDLED

NOTE: The parameters may not all be exactly the same.
CAUSE
Microsoft Knowledge Base article 102990 defines theOverrideHardwareBitstring as follows:
OverrideHardwareBitstring REG_DWORD 0x1 or 0x2 This entry is not usually present. When present, it specifies that regardless of whether it was actually detected, a serial mouse is present on the system. Add this value to tell the driver to assume the serial mouse is on COM1 (specified by the value 0x1) or COM2 (specified by the value 0x2). This entry is useful if the serial mouse has not been automatically detected.

Windows NT expected the mouse to be present.
WORKAROUND
Remove the OverrideHardwareBitstring from the registry, or make sure themouse is connected to the computer when Windows NT starts.

WARNING: Using Registry Editor incorrectly can cause serious, system-wideproblems that may require you to reinstall Windows NT. Microsoft cannotguarantee that problems resulting from the incorrect use of Registry Editorcan be solved.

Use Registry Editor at your own risk.
STATUS
Microsoft has confirmed this to be a problem in Windows NT version 3.51.We are researching this problem and will post new information here in theMicrosoft Knowledge Base as it becomes available.
3.50 3.51 prodnt trap 0x1E ntblue ntregistry
Properties

Article ID: 149983 - Last Review: 02/28/2014 08:02:31 - Revision: 3.1

  • Microsoft Windows NT Workstation 3.5
  • Microsoft Windows NT Workstation 3.51
  • Microsoft Windows NT Server 3.5
  • Microsoft Windows NT Server 3.51
  • kbnosurvey kbarchive KB149983
Feedback