STOP 0x0000005c on Multi-Processor Computer During Setup

 Last reviewed: September 18, 1995
Article ID: Q136781
The information in this article applies to:
  • Microsoft Windows NT Workstation version 3.51
  • Microsoft Windows NT Server version 3.51

SYMPTOMS

During the installation of Windows NT 3.51 on a multi-processor computer with a single processor, the following STOP Message appears: 

   STOP: 0x0000005c
   HAL NO RTC DEVICE INTERRUPT

CAUSE

This problem occurs when the Windows NT version Setup program calls the computer BIOS to obtain computer configuration information. On several computers, the BIOS returns invalid information for the number of processors installed on the computer. Therefore the multi-processor Hardware Abstraction Layer (HAL) is installed instead of required uni- processor HAL.

RESOLUTION

To correct this problem, do one of the following:

  • Contact your computer manufacturer and request an updated BIOS

    -or-

  • Press F5 during the portion of Windows NT 3.51 Setup that displays the following text: 

            Setup is inspecting your computer hardware

   This forces Windows NT Setup to use the uni-processor Hardware
   Abstraction Layer (HAL).
NOTE: Selecting "Standard PC" (without quotes) for the computer type in 
      Custom Setup does not correct the problem.

KBCategory: kbsetup
KBSubcategory: ntstop ntsetup
Additional reference words: prodnt 3.51 trap 0x5c

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: September 18, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.