This is in the System Event log (Windows Server ) ATAPI Event 11 "The driver detected a controller error on \Device\Ide\IdePort2." It is probably a hardware problem, but I'm not sure how to determine that for sure. The machine still works most of the time, but it locks up at random. Sometimes at boot time, sometimes well after that. · Likely, the problem really is in channel 2 (DVD drive). Disabling the channel in Windows may not be enough. You may have to disable channel 2 in BIOS to get the error to go away. Keep in mind that this could be a symptom of a motherboard problem. · If you see The driver detected a controller error on \Device\Harddisk2\DR2, it means there’s a serious disk defect in the RAID systems on some servers. However, the RAID utility can’t detect the error until the disk is failed www.doorway.ruted Reading Time: 5 mins.
Try unplugging and then re-plugging your hard disk cable and see if it solves your “The driver detected a controller error on \Device\Ide\Ideport0” problem. Turn off your computer. Unplug your hard disk cable from your motherboard, wait a moment and then replug it into the motherboard. Start your computer and see if the error is fixed. If you see The driver detected a controller error on \Device\Harddisk2\DR2, it means there’s a serious disk defect in the RAID systems on some servers. However, the RAID utility can’t detect the error until the disk is failed completely. Harassment is any behavior intended to disturb or upset a person or group of people. Threats include any threat of suicide, violence, or harm to another.
8 oct Windows 7 would report this in its event log: “The driver detected a controller error on \Device\Ide\IdePort2.” every minute, sometimes The driver detected a controller error on \Device\Ide\IdePort2. SOURCE atapi. ID 11 and. The application-specific permission settings do not. 2 nov I have a HP Pavillion dvea Laptop with Windows 7 on it. Recently I discovered a Error in Event Viewer: The driver detected a controller.
0コメント