Troubleshooting "Stop 0x0A" Messages in Windows NT

ID: Q165863

The information in this article applies to:

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

SUMMARY

This article discusses how to troubleshoot the following "Stop" error message in Windows NT:

Stop: 0x0000000A (parameter1, parameter2, parameter3, parameter4) IRQL_NOT_LESS_OR_EQUAL*** Address <x> has base at <x> - <filename>

MORE INFORMATION

This stop message indicates that an attempt was made in kernel mode to touch pageable memory at a process internal request level (IRQL) that is too high. This error is usually caused by drivers using improper addresses.

Parameters


1 - Memory referenced
2 - IRQL
3 - Type of access: 0 = read operation, 1 = write operation
4 - Address of instruction that referenced memory in parameter 1

This article describes troubleshooting steps to take when you receive this stop error message either during the installation of Windows NT or after Windows NT is already installed.

For more general information about this stop error message and its associated parameters, see the following article in the Microsoft Knowledge Base:

ARTICLE-ID: Q130802
TITLE : General Information on Stop 0x0000000A

"Stop 0x0A" During the Installation of Windows NT

If you receive a "Stop 0xA" error message during the installation of Windows NT, use the following troubleshooting steps.

Check the HCL:

If you receive the "Stop 0x0A" error message during the installation of Windows NT, you should first verify that your hardware is on the Windows NT Hardware Compatibility List (HCL). For information about the Windows NT 4.0 HCL, see the following article in the Microsoft Knowledge Base:

ARTICLE-ID: Q131303
TITLE : Latest Windows NT Hardware Compatibility List (HCL)

For additional information, see the following article in the Microsoft Knowledge Base:

ARTICLE-ID: Q142865
TITLE : Microsoft Support Policy on Hardware Not On Windows NT HCL

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.

Install from the Local Hard Disk:

If you are installing Windows NT by using the three Windows NT boot disks, try the following installation method instead:

Copy the I386 folder from the CD-ROM to your hard disk.

From the I386 folder on your hard disk, run the following command:

winnt /b

Follow the installation instruction screens.

Other Troubleshooting Steps During Windows NT Installation:

If you continue to receive a "Stop 0xA" error message during the installation of Windows NT, try the following troubleshooting steps (after each step, try to install Windows NT again):

During the installation bootup, press the F5 key at the "Setup is inspecting your computer's hardware configuration..." message. Select the correct computer type (or HAL) when you are prompted. For example, if you have a single processor select the "Standard PC" HAL.

For more information on this procedure, see the following article in the Microsoft Knowledge Base:

ARTICLE-ID: Q132512
TITLE : Selecting a Computer Type Before Windows NT Setup Begins

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

Remove all adapters and disconnect all hardware devices that are not absolutely required to boot the computer and install Windows NT, including:

Network adapter.

Internal modem.

Sound card.

Extra hard disks (at least one is required to complete the installation).

CD-ROM drive (if installing from the local hard disk).

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 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 drive).

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.

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).

Call the manufacturer of the computer or motherboard to see if there are any known issues with running or installing Windows NT. 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).

"Stop 0x0A" After Windows NT Is Already Installed

If you receive the "Stop 0xA" error message after Windows NT 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. Reboot 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 Windows NT after you have installed the software or drivers, you need to use one of the following methods to restore Windows NT:

Try the Last Known Good configuration by pressing SPACEBAR during bootup when you are prompted. When the Hardware Profile/Configuration Recovery menu appears, press L to switch to the Last Known Good configuration, then press ENTER.

Repair the Windows NT installation with the Emergency Repair Disk.

If Windows NT is on a FAT partition, boot to MS-DOS and rename the problem software or driver.

Remove Any Newly Installed Hardware:

If you have added any hardware since Windows NT 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 (if any) 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.

Additional Information

For additional information, see the following articles in the Microsoft Knowledge Base:

ARTICLE-ID: Q140059
TITLE : Stop 0xA in Afd When Browsing IIS

ARTICLE-ID: Q157054
TITLE : Stop 0x0000000A Accessing IIS Server After Upgrading to Windows NT 4.0

ARTICLE-ID: Q141239
TITLE : Stop 0xA Errors May Occur After Installing Service Pack 2

If none of the above items resolves the issue and you are running Windows NT on an HCL computer, see the following article:

ARTICLE-ID: Q129845
TITLE : Blue Screen Preparation Before Contacting Microsoft

REFERENCES

Microsoft Windows NT Resource Kit version 3.51, "Windows NT Messages" volume, Chapter 4, "Message Reference."

Additional query words: ntoskrnl.exe blue screen ntfaqset tshoot


Keywords          : kberrmsg ntstop prodnt 
Version           : 3.5 3.51 4.0
Platform          : WINDOWS 
Issue type        :

Last Reviewed: July 13, 1999