Applies To

 

Windows Server 2008, Windows Server 2008 R2, Windows 7

Details

Product

Windows Operating System

ID

11

Source

ATAPI

Version

6.1

Message

The driver detected a controller error on \Device\Ide\IdePort0.

 

Cause

Event ID 11 may be logged in your system log, although the source can be any
controller name (for example, Atdisk, Atapi, or Sparrow). In almost all cases,
these messages are being posted due to hardware problems with either the
controller or, more likely, a device that is attached to the controller in question.
The hardware problems can be associated with poor cabling, incorrect termination
or transfer rate settings, lazy or slow device responses to relinquish the SCSI bus,
a faulty device, or in very rare cases, a poorly written device driver.

User action

The Following are some troubleshooting tips to help diagnose and pinpoint the 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 npower,
    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 intermediary devices are not.
 
  • If only a single SCSI chain is used (all internal or all external), ensure that 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 long chain 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 it coincides with certain
    processing schedules (such as backups) or heavy disk processing. This will help to determine
    what device may be causing the errors.

The reason that drives tend to have these types of problems under heavy stress is often slow
microprocessors. In a multitasking environment, the processor may not be fast enough to
process all the I/O commands that come in nearly simultaneously.