Troubleshooting Stop 0x0000000a Messages with SBS

ID: Q214764

The information in this article applies to:

Microsoft BackOffice Small Business Server versions 4.0, 4.0a, 4.5

SUMMARY

One of the most frequent STOP errors in Windows NT or Small Business Server (SBS) is Stop 0x0000000A. This STOP message can be caused by both hardware and software problems.

This error is typically caused by a driver or memory. The driver may be corrupted or it may be the incorrect driver. The driver may be loading in the incorrect memory address or the memory may be bad or going bad.

MORE INFORMATION

To determine what process or driver tried to access memory that it should not access, look at the parameters displayed on the STOP screen information. For example, in the following STOP message:

STOP 0x0000000A(0xWWWWWWWW, 0xXXXXXXXX, 0xYYYYYYYY, 0xZZZZZZZZ)
IRQL_NOT_LESS_OR_EQUAL
** Address 0xZZZZZZZZ has base at <address>- <driver>

The four parameters inside the parenthesis have the following meaning:

0xWWWWWWWW: Address that was referenced improperly
0xXXXXXXXX: IRQL that was required to access the memory
0xYYYYYYYY: Type of access, 0=Read, 1=Write
0xZZZZZZZZ: Address of instruction which attempted to reference the memory at 0xWWWWWWWW

Typically, the driver causing the error will be listed at the end of the STOP error section. You may find additional information on the driver error by searching in the Microsoft Knowledge Base on the keywords 0x0000000A and the driver name.
If you have recently added any hardware or software, you may choose to remove it and see if the the STOP error still occurs.

Troubleshooting

STOP 0x0A After SBS Is Already Installed

If you receive the STOP 0xA error message after SBS is already installed, use the following troubleshooting steps:

Remove any recently installed third-party software or drivers.

If you have installed any third-party software or drivers, you may want to remove or disable them from loading. Restart to see if the software or driver was causing the error message. If so, contact the vendor of the software or driver to report the problem.

If you are not able to boot into SBS after you have installed the software or drivers, you need to use one of the following methods to restore the Windows NT portion of SBS:
- Try the Last Known Good configuration by pressing the space bar during startup when you are prompted. When the Hardware Profile/Configuration Recovery menu appears, press L to switch to the Last Known Good configuration, and then press ENTER.
- Repair the SBS installation with the Emergency Repair Disk.

Remove any newly installed hardware:

If you have added any hardware since SBS was installed, you may want to remove the hardware to see if the error message stops occurring. If this corrects the problem, you may want to use any or all of the following methods:
- Obtain updated drivers for the device.
- Call the vendor to see if there are any known issues with the device.
- Run diagnostics to see if the device is working properly.
- Check Event Viewer for any additional error messages that might help determine the device or driver that is causing the problem.

STOP 0x0A During the Installation of SBS

If you receive a STOP 0xA error message during the installation of SBS, use the following troubleshooting steps:

Check the Hardware Compatibility List (HCL).

If you receive the STOP 0x0A error message during the installation of SBS, you should first verify that your entire system is on the Windows NT HCL, and that modems and network cards are on the SBS HCL.

For information about the Windows NT 4.0 HCL and the SBS HCL, see the following Microsoft Web site:

http://www.microsoft.com/SMALLBUSINESSSERVER/deployadmin/Recommended.htm

If your hardware is not on the Windows NT HCL, the troubleshooting steps listed below may help isolate the problem. However, you may want to consider obtaining hardware that is on the HCL.

If you continue to receive a STOP 0xA error message during the installation of SBS, try the following troubleshooting steps (after each step, try to install SBS again):
1. Disable the following items in your computer's CMOS settings.
  
  Consult your hardware documentation or manufacturer for instructions on disabling these features:
  - All caching including:
    - L2 cache
    - BIOS cache
    - Internal/External cache
    - Write back cache on disk controllers
  - All shadowing
  - Plug and Play
  - Any BIOS-based virus protection feature
2. Remove all adapters and disconnect all hardware devices that are not absolutely required to boot the computer and install SBS, including:
  - Network adapter
  - Internal modem
  - Sound card
  - Extra hard disks (at least one is required to complete the installation)
3. If you are using a SCSI adapter, check the following items.
  Consult your hardware documentation for information on these items:
  - Obtain the latest Windows NT or SBS driver from the adapter vendor.
  - Disable sync negotiation on the SCSI controller.
  - Check and verify termination and IDs of the SCSI devices.
  - Take all SCSI devices off the chain except for one hard disk (if you are booting from or installing to that disk).
4. If you are using IDE devices, check the following items:
  - Define the on-board IDE port to Primary only.
  - Check the Master/Slave/Only settings for the IDE devices.
  - Remove all other IDE devices except for the hard disk.
5. Check the memory SIMMs (RAM) in the computer:
  - Remove any mismatched memory SIMMs (use all one speed, such as 60ns or 70ns).
  - Remove any bad memory SIMMs (run systems test on the memory).
  - Test with different SIMMs (if available).
6. Call the manufacturer of the computer or motherboard to see if there are any known issues with running or installing Windows NT or SBS. They may be able to provide guidance on the following items:
  - Running a diagnostics program on the computer
  - Upgrading the computer's BIOS (if applicable)

REFERENCES

The Microsoft 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 from the Summary section, you would search on 0x000000A. It also may be helpful to search on the identified file name and other hexadecimal numbers.
For additional information, please see the following article(s) in the Microsoft Knowledge Base:

Q192463 Gathering Blue Screen Information After Memory Dump

Q123750 Debugging Windows NT Setup STOP Screens

Q165863 Troubleshooting "Stop 0x0A" Messages in Windows NT

Q174630 Windows NT Restarts Continuously with Blue Screen

Q103059 Descriptions of Bug Codes for Windows NT

Q130802 General Information on STOP 0x0000000A

Q161703 "Stop: 0x0000001E" Error Message During Setup

Additional query words: smallbiz Stop A 0x0A

Keywords : kbtshoot
Version : winnt:4.0,4.0a,4.5
Platform : winnt
Issue type : kbinfo