Windows 2000 Stop Messages
Windows 2000 Stop Messages |
|
Stop messages generally fall into one of four categories:
The most common Stop messages are generated during regular operations. Even in a complex and robust operating system such as Windows 2000, catastrophic problems sometimes cause the system to stop responding and display a Stop message. In Windows 2000, a driver or the file system can generate a Stop message by introducing an unhandled error (exception) in the code or by performing some illegal operation.
For information about troubleshooting Stop messages, including detailed information about the most common errors, see "Troubleshooting Stop Messages" later in this chapter.
For the most comprehensive list of Stop messages in Windows 2000, along with useful information about diagnosing and troubleshooting these messages, refer to the Microsoft Knowledge Base article Q103059, titled "Descriptions of Bug Codes for Windows NT."
An unsuccessful attempt to install Windows 2000 can result in a Stop message. When this happens, first check that the computer and all of its peripheral hardware are compatible with Windows 2000. To do this, refer to the latest Windows 2000 Hardware Compatibility List (HCL). Microsoft compiles the HCL through rigorous component and compatibility testing of computers and peripheral hardware to determine if they work well with Windows 2000. For more information about the HCL, see "Additional Resources" at the end of this chapter.
If the hardware you use is not included on the Windows 2000 HCL, contact the hardware manufacturer as a first-line resource for available information, newly tested hardware, and Basic Input/Output System (BIOS) and firmware revisions. Reducing the number of hardware components by removing nonessential peripherals and devices can help you pinpoint installation conflicts as well.
Some Stop messages occur only during the relatively short Phase 4 period of the Windows 2000 startup sequence. Initialization of the Windows 2000 Executive, a family of software components that provides basic operating system services, is one step during Phase 4. Executive initialization can be further broken down into two phases: Phase 0 and Phase 1. During Phase 0, interrupts are disabled and only a few Executive components, such as the hardware abstraction layer (HAL), are initialized. During Phase 1 of Executive initialization, the system is fully operational, and the Windows 2000 subcomponents go through a full initialization.
If you receive one of the Phase 0 initialization Stop messages listed in Table 17.171, run the hardware diagnostics provided by your system manufacturer.
Note
In many situations, hardware failures manifest themselves as errors that generate Stop messages. This is why troubleshooting many of the Stop messages includes running hardware diagnostics on the system.
If no hardware problems are found, reinstall Windows 2000 and try to initialize it again. If you get the same message, contact a support technician.
Table 17.1 Phase 0 Initialization Stop Messages
| Message ID | Symbolic Name |
|---|---|
| 0x31 | PHASE0_INITIALIZATION_FAILED |
| 0x5C | HAL_INITIALIZATION_FAILED |
| 0x5D | HEAP_INITIALIZATION_FAILED |
| 0x5E | OBJECT_INITIALIZATION_FAILED |
| 0x5F | SECURITY_INITIALIZATION_FAILED |
| 0x60 | PROCESS_INITIALIZATION_FAILED |
If you receive one of the Phase 1 initialization Stop messages listed in Table 17.17.2, reinstall Windows 2000 and try to initialize it again. If you get the same message, contact a support technician.
Table17.2 Phase 1 Initialization Stop Messages
| Message ID | Symbolic Name |
|---|---|
| 0x32 | PHASE1_INITIALIZATION_FAILED |
| 0x61 | HAL1_INITIALIZATION_FAILED |
| 0x62 | OBJECT1_INITIALIZATION_FAILED |
| 0x63 | SECURITY1_INITIALIZATION_FAILED |
| 0x64 | SYMBOLIC_INITIALIZATION_FAILED |
| 0x65 | MEMORY1_INITIALIZATION_FAILED |
| 0x66 | CACHE_INITIALIZATION_FAILED |
| 0x67 | CONFIG_INITIALIZATION_FAILED |
| 0x68 | FILE_INITIALIZATION_FAILED |
| 0x69 | IO1_INITIALIZATION_FAILED |
| 0x6A | LPC_INITIALIZATION_FAILED |
| 0x6B | PROCESS1_INITIALIZATION_FAILED |
| 0x6C | REFMON_INITIALIZATION_FAILED |
| 0x6D | SESSION1_INITIALIZATION_FAILED |
| 0x6E | SESSION2_INITIALIZATION_FAILED |
| 0x6F | SESSION3_INITIALIZATION_FAILED |
| 0x70 | SESSION4_INITIALIZATION_FAILED |
| 0x71 | SESSION5_INITIALIZATION_FAILED |
Erroneous software conditions detected by the processor, called software traps, can also generate Stop messages. A software trap occurs when a processor detects a problem with executing an instruction, which causes it to stop. For example, a processor does not carry out an instruction that contains invalid operands.
When you receive one of these messages, first write down the information displayed in the bugcheck information section of the Stop message, and then restart the computer. If the message recurs, you have four options for diagnosing the Stop error, all of which should be handled by a trained support technician at your own site:
Important
If you use either of the following options, be sure Windows 2000 is in debug mode before you restart your computer.