Remaining STOP Messages

A typical user will not be able to diagnose the cause of any of the remaining STOP messages. When you get one of these messages, first record the top few lines of the STOP message and then restart the computer. If the STOP message occurs again, you have four options for diagnosing the STOP condition, all of which should be handled by a trained technician at your own site:

• Diagnose the problem using the information displayed in the STOP message and any pertinent information from the Windows NT forum on CompuServe®, where Microsoft maintains an up-to-date list of causes for these STOP messages.
• Use the Windows NT debugger to get more information about the problem.

  If you use this option or the next one, be sure to switch Windows NT to debug mode before you restart your computer. See "Windows NT Debugger," later in this chapter, for information on how to prepare your computer for debugging.

• Contact your own or another technical support group for assistance in using the Windows NT debugger remotely.
• Contact your own or another technical support group to discuss the information in the STOP message. They may see a familiar pattern in the information and save everyone time.

The following list provides the ranges of unique hexadecimal numbers for the STOP messages that are least likely to happen. However, if one does occur, it will be after Windows NT Executive startup is complete and will not be caused by hardware or software traps in a processor. If you want more information about these messages, you can refer to the alphabetical list provided in Chapter 4, "Message Reference." However, most trained technicians will only need the unique hexadecimal number.

0x00000001 through 0x00000009 0x0000000B through 0x0000001D 0x0000001F through 0x00000030 0x00000033 through 0x0000005B 0x00000072 through 0x0000007B