Troubleshooting "Stop 0x0A" Messages in Windows 2000 and Windows NT

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. Drivers using improper addresses usually cause this error. 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 or after Windows is already installed.

For additional information about this stop error message and itsassociated parameters, click the article number below to view the article in the Microsoft Knowledge Base:

"Stop 0x0A" During the Installation of Windows

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

Check the HCL

If you receive the "Stop 0x0A" error message during the installation of Windows, you should first verify that your hardware is on the Windows Hardware Compatibility List (HCL). For additional information about the Windows HCL, click the article numbers below to view the articles in the Microsoft Knowledge Base: The latest HCL is available at the following Microsoft Web site: If your hardware is not on the Windows 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:

1. Copy the I386 folder from the CD-ROM to your hard disk.
2. From the I386 folder on your hard disk, run the following command:

   winnt /b

3. Follow the installation instruction screens.

If you are installing Windows 2000 by using the four Windows 2000 boot disks, try one of the following installation methods instead:

• Method 1:
  1. Copy the I386 folder from the CD-ROM to your hard disk.
  2. From the I386 folder on your hard disk, run the following command:

     winnt /b

  3. Follow the installation instruction screens.
• Method 2:
  1. Boot from the Windows 2000 CD-ROM.
  2. follow the installation instruction screens.

Other Troubleshooting Steps During Windows Installation

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

1. 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 additional information about this procedure, click the article number below to view the article in the Microsoft Knowledge Base:

   132512 Selecting a Computer Type Before Windows NT Setup Begins

2. 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
3. Remove all adapters and disconnect all hardware devices that are not absolutely required to boot the computer and install Windows, 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)
4. If you are using a SCSI adapter, check the following items. Consult your hardware documentation for information on these items:
   • Obtain the latest Windows 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).
5. 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.
6. 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).
7. Call the manufacturer of the computer or motherboard to see if there are any known issues with running or installing Windows. 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 Is Already Installed

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

• Try the Last Known Good configuration by pressing SPACEBAR during startup when you receive the prompt. When the Hardware Profile/Configuration Recovery menu appears, press L to switch to the Last Known Good configuration, and then press ENTER.
• Repair the Windows installation with the Emergency Repair Disk or use the Windows Emergency Repair process.
• If Windows 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 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.

"Stop 0x0000000a(0x00000029,0x00000002,0x00000000,0x80466d7b" Error Message after Windows Is Already Installed

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

When this issue occurs, use the following troubleshooting steps:

1. Uninstall the Easy CD Creator software
2. Start Registry Editor (Regedit.exe).
3. Go to the following registry key:

   HKEY_LOCAL_MACHINE\System\CurrentControlSet\Security

4. Remove the file called Etetnt.mpd; it has a revision date of 1997.
5. Go to the following registry key:

   HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services

6. Remove the following files:
   • Cdr4vsd
   • Cdralw2k
   • Cdr4_2k
   • Cdudf

Additional Information

For additional information about how to uninstall Roxio products, click the article number below to view the article in the Microsoft Knowledge Base: For additional information, click the article number below to view the article in the Microsoft Knowledge Base: If none of the preceding articles helps you to resolve the issue, if you are running Windows on an HCL computer, see the following article: NOTE: Adaptec has software that is installed to make an external CD-RW work through a parallel port that installed a file called etetnt.mpd. It has a revision date of 1997.

NOTE: In some cases, removing the following registry key corrected the issue: