Driver detected a controller error on device ide ideport2

 · Please restart your computer when encountering the driver detected a controller error. Then, open the event log to check the error messages. 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 Estimated Reading Time: 5 mins.  · Please help, this is driving me crazy!!! I did my first self build as below: Vista Home Premium Asus P5B-MX/Wi-FI C2D E 2 x 1gb PC RAM Samsung SATA Spinpoint gb, SATA DVD-RW Arctic Freezer 7 Pro And every hour or so, usually on Explorer, Vista freezez. The 'busy' vista circle User Interaction Count: 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. 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. The driver detected a controller error on \Device\Ide\IdePort2. - System - Provider [ Name] atapi - EventID 11 [ Qualifiers] Level 2 Task 0 Keywords 0x - TimeCreated [ SystemTime] TZ EventRecordID Channel System Computer *****-PC Security - EventData \Device\Ide\IdePort2.

I believe this drive should be compatible with PE If I disable the IDEPort it reboots in 5 minutes. Any ideas what I can do to fix the. 3 nov I just noticed this error in event viewer this morning and apparently it has been ongoing since October 4th. Looking back, I believe that's. Check the drive for errors · Disconnect and reconnect all hardware and cables · Update drivers · Update BIOS · Run Hardware Diagnostics · Get the.