Blue Screen Preparation Before Calling Microsoft

The information in this article applies to:

• Microsoft Windows NT Workstation versions 3.5, 3.51, and 4.0
• Microsoft Windows NT Server versions 3.5, 3.51, and 4.0

SUMMARY

When a STOP message (fatal system error) occurs in Windows NT, it enters debug mode for troubleshooting purposes. This appears as a blue screen and the first few lines look similar to the following:

   Stop 0x0000001e (c000009a 80123f36 02000000 00000246)
   Unhandled Kernel exception c000009a from 8123f26
   Address 80123f36 has base at 80100000 - ntoskrnl.exe

MORE INFORMATION

Knowledge Base

The Knowledge Base contains many articles that explain specific STOP messages and often, resolutions to or ways to work around the problem. Search the Knowledge Base for at least the first hexadecimal number. For example, in the example above, that is "0x0000001e". It also may be helpful to search on the identified file name and other hexadecimal numbers.

Saving STOP Messages to File

You can configure Windows NT to save STOP message information to a "dump" file, Memory.dmp. If you need to contact Microsoft Product Support, this will help you give us the specific information we need to identify the problem.

Saving STOP message information to file is enabled by default in Windows NT Server. However, for Windows NT Workstation, you must enable the option manually. This must be done prior to encountering a fatal error for the information to be recorded. To enable this feature, follow these steps:

1. In the System component of Control Panel, choose the Recovery button.

2. Select the Write Debugging Information To check box.

3. Choose OK until you are asked to restart the computer.

Memory.dmp File

If a STOP message appears and a Memory.dmp file is created, a Microsoft support engineer may be able to debug the dump file. Call Microsoft Product Support, describe the STOP message to the support engineer and explain that you have a dump file.

You may be asked to send your Memory.dmp file to Microsoft if the support engineer is not able to solve the problem over the phone. If so, compress the file with an application such as PKZIP. Memory.dmp files usually compress significantly. Use one of the following options to upload the file:

• Send your compressed Memory.dmp file by FTP to ftp.microsoft.com. This requires FTP access to the Internet. The support engineer will explain how to place your file on the FTP server. The server TCP/IP address is:

        198.105.232.1
  

• Upload your compressed Memory.dmp file from the Microsoft Support File Exchange BBS. The support engineer will explain how to upload the file and what telephone number to use.
• Back up your Memory.dmp file to tape using NTBackup and mail the tape to the support engineer.
• Copy the file to a writeable compact disc and mail it to the support engineer.
• If none of the above options are feasible, the support engineer may be able to use Remote Access Service (RAS) to access your computer and examine or copy the Memory.dmp file. Follow these steps to prepare your computer for a Microsoft support engineer to access it with RAS:

  1. Create a temporary user account that a Microsoft support engineer

        can use when accessing the Memory.dmp file.
  

  2. On another server, create a share and give this new user account

        access to this share.
  

  3. Copy the newly created Memory.dmp file to this new share.

  4. If you don't have RAS installed at your site, install RAS on an

        Windows NT Server or Workstation. For security, you can install RAS
        on a computer and allow remote clients to connect only to that
        computer, not the network. If you do this, create the new network
        share on this computer and copy the Memory.dmp file there.
  

  5. Allow the support engineer user ID access to dial in to the RAS

        server.
  

  6. Give the support engineer the username, password, domain name,

        server name, share name, and phone number for the modem line.