I'm seeing Error 11 "The driver detected a controller error on \Device\Ide\IdePort1" in the event log of a Windows 7 machine.
The motherboard is a Gigabyte GA P35 DS4 v2. It has 6 SATA ports connected to the ICH9, and two Gigabyte SATA ports connected to a separate controller.
I'm trying to understand which drive corresponds to the "IdePort1" in the error message.
The term "IdePort" does not occur in the registry.
In examining the disk controller and disk properties in Device Manager and Disk Management, I have found the following information:
The Boot drive properties are:
Location 0, Channel 1, Target 0, Lun 0
Parent: PCIIDE\IDEChannel\5&6882b60&0&1
Physical Device Object Name: \Device\Ide\IdeDeviceP1T0L0-1
Instance Path: IDE\DISKTOSHIBA_THNSNH256GBST___________________HTRAN101\6&15A9375D&0&1.0.0
Another drive has these properties:
Location 0, Channel 1, Target 0, Lun 0
Parent: PCIIDE\IDEChannel\4&23c85994&0&1
Physical Device Object Name: \Device\Ide\IdeDeviceP3T0L0-4
Instance Path: IDE\DISKST31500541AS____________________________CC34____\5&36A55C2A&0&1.0.0
In Device Manager, under IDE ATA/ATAPI controllers, there are three instances of "ATA Channel 0, followed by three instance of ATA Channel 1. I can find the drives in these listed under Detailed Properties "Bus Relations".
But there is nothing that indicates what number in all these strings corresponds to the "IdePort1"
Does the number in IdePort# correspond to Location, Channel, Target, or LUN?
Or is it the number in the "physical device object name" string "IdeDeviceP1T0L0-1" or "IdeDeviceP3T0L0-4"? Or something else?
Best Answer
I would guess that for the Boot drive, "IdeDeviceP1T0L0" likely means "IDE device port 1 target 0 lun 0".
More info can be found in the Microsoft article Understanding Disk Location Paths, which also explains how to display disk details using the utility diskpart.
Windows device information is to be found in the registry under the key
HKEY_LOCAL_MACHINE\Hardware\Devicemap, that you could share here.I remark that error 11 is usually either a bad SATA cable or a dying disk (not the only reasons).