Applies To:
  • CitectSCADA 3.00

Question: Windows NT is displaying a blue screen STOP message. What is the cause of this problem? 

The Windows NT STOP blue screen is displayed whenever Windows NT encounters a fatal error. This STOP message can be caused by both hardware and software problems. The following article is from the Microsoft TechNet Knowledge base and details the procedure for tracing STOP messages. You should follow this procedure and contact Microsoft Product Support. Where the article refers to the Knowledge base it means the Microsoft knowlege base, not Citect knowlege base.


When a STOP message (fatal system error) occurs in Windows NT, it enters debug mode for trouble shooting purposes. This appears as a blue screen andthe first few lines will look similar to this:

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

Following are two procedures to assist you in identifying the cause of the STOP message prior to contacting Microsoft Product Support Services (PSS).


Knowledge Base

The Knowledge Base contains many articles explaining 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. 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 PSS, 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 reboot.

NOTE: The paging file must be at least as large as the amount of physical RAM installed in your computer. The paging file must reside in the active partition. There must be adequate room for the MEMORY.DMP file to be created.


If a STOP message appears and a MEMORY.DMP file is created, a PSS supportengineer may be able to debug the dump file. Call Microsoft PSS, 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 This requires FTP access to the Internet. The support engineer will explain how you can put your file on the FTP server. The server TCP/IP address is:

  • Upload your compressed MEMORY.DMP file Microsoft Support File Exchange BBS. The support engineer will explain how to upload the file and what telephone number to use.
  • Backup your MEMORY.DMP file to tape using NTBackup and mail the tape to the support engineer.
  • Copy the file to a writeable CD-ROM and mail the 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 PSS support engineer 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 to 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.

Additional reference words: prodnt 3.50 Remote Debug

KBCategory: kbhowto

KBSubCategory: nthowto ntstop

Copyright Microsoft Corporation 1995.