This article contains troubleshooting information to help you resolve STOP error messages (these error messages are displayed on a blue screen).
When you receive a STOP message (a fatal system error message) in Microsoft Windows NT or BackOffice Small Business Server (SBS), the computer enters debug mode for troubleshooting purposes. The error message appears on a blue screen, and the first few lines are similar to the following sample error message:
Stop 0x0000001e (c000009a 80123f36 02000000 00000246)
Unhandled Kernel exception c000009a from 8123f26
Address has base at 80100000 ntoskrnl.exe
: Be sure to write down the text of the error message. It is important information and is one of the first things a Microsoft Support Professional may ask you.
Check the Microsoft Knowledge Base
The Microsoft Knowledge Base contains many articles that explain specific STOP error messages, and resolutions or ways to work around problems. Search the Microsoft Knowledge Base for at least the first hexadecimal number contained in the error message. Using the example above, search for 0x0000001e. It also may be helpful to search for the identified file name and other hexadecimal numbers.
Preparation to Create a Memory.dmp File
- Verify that your computer is set to write a Memory.dmp file (in Control Panel, double-click System, and then click the Startup/Shutdown tab).
- Click to select the Write an event to the system log and Write Debugging information to check boxes.
The box below these two check boxes should read "%SystemRoot%\Memory.dmp."
- Clicking to select the Overwrite any existing file check box overwrites the Memory.dmp file if you receive more than one error message on a blue screen.
- You can rename the Memory.dmp file and have two different dump files if the problem cannot be resolved by simple troubleshooting steps, and the dump has to be read.
- Clicking to select the Automatically reboot check box causes the server to automatically reboot after the error message is displayed on a blue screen. This is useful if the server restarts after hours and users dial in remotely to the server. However, it may also cause the server to be in an indefinite loop at startup if there is a serious problem.
- You need to have at least as much free space as there is RAM on the drive on which the Winnt.sbs folder is located. Also, the paging file must be on the same partition on which SBS is installed, and the size must be at least equivalent to the amount of RAM in the computer. A Memory.dmp file is a file to which memory is written, so it is the same size as the computer's RAM. You may need to compress this file and send it to Microsoft using File Transfer Protocol (FTP).
- To run a Windows NT Diagnostics (Winmsd.exe) report, click Start, click Run, type winmsd, and then click OK.
- To save the report as a text file that you can e-mail to Microsoft or to a consultant, click Save Report on the File menu. Click File, click Complete, and then click OK.
This report provides valuable information about your computer, including services that are running, hard disk and RAM availability, drivers in use, and networking information.
Event logs are another important troubleshooting aid. To save event logs:
- Click Start, point to Programs, click Administrative Tools, and then click Event Viewer.
- Click Log, click the log type (the options are System, Security, or Application), click Log, and then click Save As.
- Click the location to which you want to save the file, and give the file a name with an .evt extension.
Save all three log files for future reference.
Before You Call Microsoft Support
This is additional information that a Microsoft Support Professional may request of you. Please gather as much of this information as possible before you call a Microsoft Support Professional.
- What version of SBS is installed on the computer?
- Are any additional service packs installed?
- Are any Compaq Support Software Diskettes (SSDs) installed?
- Are any hotfixes installed?
- Is SBS installed on an NTFS partition?
- How are the hard disks partitioned?
- What programs are installed?
- What protocols are installed? (For example, TCP/IP or NetBEUI.)
- Are there any routers on your network?
- What is the brand and model of your computer?
- Is the computer listed on the Windows NT Hardware Compatibility List (HCL)?
- What are the brands, types, and sizes of the hard disks?
- What types of controllers are in the computer?
- How many and what types of processors are in the computer?
- How much memory (RAM) is in the computer?
- What types and models of tape drives are in the computer?
- What is the type and model of the CD-ROM drive?
- What types and models of network adapters are installed in the computer?
- Is this first occurrence of the problem?
Debugging Windows NT Setup STOP Screens
Windows NT Restarts Continuously with Blue Screen
Windows NT Does Not Save Memory Dump File After a Crash
No Memory.dmp File Created with RAM Above 1.7 GB
Gathering Blue Screen Information After Memory Dump
3Com 3c905b Prevents Write of Memory.dmp
How to Use Dumpchk.exe to Check a Memory Dump File
Checking Crashdump File for Corruption
Pressing CTRL+ALT+DEL When Logging On Can Cause Blue Screen
SBS Client Setup Fails With a Blue 'L2' Screen
No Crashdump and Compaq Systems with Smart-2/P (PCI) Controller
List of Bugs Fixed in Windows NT 4.0 Service Packs (Part 1)
SMC 8216 EtherCard Elite 16 Ultra May Cause Error Message
Determining If a Service Pack Has Been Installed
Article ID: 216206 - Last Review: November 19, 2003 - Revision: 3.3
- Microsoft BackOffice Small Business Server 4.0
- Microsoft BackOffice Small Business Server 4.0a
- Microsoft BackOffice Small Business Server 4.5