How to troubleshoot event ID 9, event ID 11, and event ID 15 error messages

Support for Windows Server 2003 ended on July 14, 2015

Microsoft ended support for Windows Server 2003 on July 14, 2015. This change has affected your software updates and security options. Learn what this means for you and how to stay protected.

This article was previously published under Q154690
For a Microsoft Windows XP version of this article, see 314093.
This article describes how to troubleshoot event ID 9, event ID 11, or event ID 15 error messages. The following event ID messages may be logged in your system log(use Event Viewer to view the log), although the source can be any controller name(for example, Atdisk, Atapi, or Sparrow).

Message 1
Event ID: 9
Source: aic78xx
Description: The device, \Device\ScsiPort0, did not respond within the timeout period.
Message 2
Event ID: 11
Source: aic78xx
Description: The driver detected a controller error on Device\ScsiPort0.
Message 3
Event ID: 15
Source: [scsi miniport driver]
Description: The device, \Device\ScsiPort1, is not ready for access yet.
Event ID 15 indicates that the device is not ready. This can be the result of SCSI host adapter configuration issues or other problems. Check with the manufacturer for updated firmware, drivers, or known issues. This could also indicate a malfunctioning device. This error occurs at the device level.

In almost all cases, these messages are being posted due to hardwareproblems with either the controller or, more likely, a device that isattached to the controller in question. The hardware problems can beassociated with poor cabling, incorrect termination or transfer ratesettings, lazy or slow device responses to relinquish the SCSI bus, afaulty device, or, in very rare cases, a poorly written device driver.
The following are some troubleshooting tips to help diagnose and pinpointthe problem:
  • Read the SCSI controller manufacturer's technical manual to determine the termination requirements. Many modern SCSI controllers require active terminators (at least one of the devices on the bus must provide termination power). Proper termination involves both a terminator(resistor) and a device that supplies a signal to the bus for termination power. The SCSI-2 standard specifies that a controller (initiator) must supply termination power. Therefore, any controller that claims to be SCSI-2 compatible probably does supply termination power, but you should check if you are unsure. Also, many devices, especially drives, give you the option of providing termination power; if you have a jumper on the drive that reads Trmpwr, you should enable this jumper.
  • If both internal and external SCSI devices are attached, make sure the last device on each SCSI chain is terminated, and that intermediarydevices are not.
  • If only a single SCSI chain is used (either all internal or external), ensure the last device of the SCSI chain is terminated and the SCSI controller itself is terminated. This is usually a BIOS setting.
  • Check for loose or poor quality SCSI cabling. When you have a longchain of cables with mixed internal and external cabling, you run the risk of degrading the signal. Even though the SCSI specification may specify a long distance, the specification assumes cabling that allows no leakage or interference, and the reality is generally a shorter distance. Whenever you have 6-foot or longer external cables, you should replace them with 3-foot cables.
  • Note when the event messages are posted and try to determine if itcoincides with certain processing schedules (such as backups) or heavydisk processing. This will help to determine what device may be causingthe errors.

    Note The reason that drives tend to have these types of problems under heavy stress is often slow microprocessors. In a multitaskingenvironment, the processor may not be fast enough to process all the I/O commands that come in nearly simultaneously.
  • Slow the transfer rate settings if the timeouts are associated with tape drives - using 5MBS transfer rate usually cures the timeouts.
  • Simplify the SCSI/IDE chain by removing devices, or move the device in question to another controller. If the problem follows the device, you should replace it.
  • Check the revision of SCSI controller BIOS and device firmwarerevisions. Contact the manufacturer for the latest revisions. See the Checking the Model Number and Firmware Revision section below for the procedure on how to do this.
  • Check the SCSI device drivers version. The SCSI driver is locatedin the %Systemroot%\System32\Drivers directory. Look at the version in the file properties, and check whether the SCSI manufacturer has a newer version.
  • Remove other controllers that may create bus contention problems.
  • A low-level format performed by the SCSI controller may resolve these event messages.
  • Use a different make or model of any suspect hardware.

Checking the model number and firmware revision

The model number of the device and firmware revision are in the Windows registry. To check the model number and firmware revision, follow the stepsbelow.

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows
  1. Run Regedt32.exe.
  2. Locate and click the following registry key, where x varies according to device number:
    HKEY_LOCAL_MACHINE\Hardware\Devicemap\Scsi\ScsiPortx\ScsiBusx\ TargetIdx\LogicalUnitIdx
  3. Look at the REG_SZ identifier value to see the model number andfirmware revision values. For example, in the following value, the firmware revision value is 0510:
    SEAGATE ST32430N 0510
  4. Record all the device model numbers and firmware revisions, and check with the manufacturer for any known issues.
Note For Windows 2000 and Windows Server 2003, you can view model and firmware revisions for hardware under the following registry location:
For more information about troubleshooting these events, click the following article number to view the article in the Microsoft Knowledge Base:
259237 Troubleshooting event ID 9, 11, and 15 on cluster servers
prodnt adic1000 adpu160m aic78u2 aic78xx cdrom cpq32fs2 disk dlttape-vtrs nfrd960 ql2200 sonysdx-vrts stek9714

Article ID: 154690 - Last Review: 02/26/2007 23:17:18 - Revision: 4.5

Microsoft Windows Server 2003, Standard Edition (32-bit x86), Microsoft Windows Server 2003, Datacenter Edition (32-bit x86), Microsoft Windows Server 2003, Enterprise Edition (32-bit x86), Microsoft Windows Server 2003, Web Edition, Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems, Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems, Microsoft Windows 2000 Server, Microsoft Windows 2000 Advanced Server, Microsoft Windows 2000 Professional Edition, Microsoft Windows 2000 Datacenter Server, Microsoft Windows NT Advanced Server 3.1, Microsoft Windows NT Server 3.5, Microsoft Windows NT Server 3.51, Microsoft Windows NT Server 4.0 Standard Edition, Microsoft Windows NT Workstation 3.1, Microsoft Windows NT Workstation 3.5, Microsoft Windows NT Workstation 3.51, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Advanced Server 3.1

  • kbhardware KB154690