Atapi Driver Detected A Controller Error
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Sat, 01 Oct 2016 14:05:58 GMT by s_hv978 (squid/3.5.20)
ordeal with this Event 11 that Windows quietly generates. It took us few weeks to fully work out why Windows suddenly started hanging, misbehaving or even crashing with blue screen. Now that the driver detected a controller error on \device\harddisk3\dr3. I feel it is fully resolved, I thought I’d share my conclusion (and the
The Driver Detected A Controller Error On \device\harddisk1\dr2.
process) – hopefully it will help few others out there who are struggling with this. Ridiculously, many people are likely affected
The Driver Detected A Controller Error On \device\raidport0.
by this issue, but unless they open Event Viewer and search for this event id 11, they will not realize that hanging is not “normal” behavior, even for Windows! OS seems to silently recover from this http://answers.microsoft.com/en-us/windows/forum/windows_vista-hardware/atapi-event-id11-the-driver-detected-a-controller/7fdd47da-7c86-4f7b-bdf7-096bb4f059f4 problem 10 to 60 seconds later, which is really strange in my book – considering that user isn’t even alerted to this serious atapi error. For impatient souls among us, here are my conclusions: First thing – check the SATA/EIDE and power cable connection between your hard-drive and the motherboard. If possible, try another SATA outlet on motherboard or another SATA cable if available. If it still happens, the bad news http://www.adir1.com/2012/01/solved-the-driver-detected-a-controller-error-on-deviceideideport2/ is that this is likely a disk controller error, which is especially problematic since nowadays disk controllers are built into the Motherboard. If you are in a budget crunch, one potential workaround is to slow down your HD to use different PIO. This may avoid hangs, but will slow overall performance, so no fun solution… Proper solution appears to be to replace motherboard, hence replacing disk controller. There are many motherboards starting at just $50 and in most cases it will improve overall performance and stability for you, even if you keep the same CPU and other components. I am pretty confident that this is the right diagnosis, as we went through a lot of trial and error investigative work, in a space of few weeks, after it started abruptly. At first, I was pretty much convinced that HD is dying. The system had two hard-drives, and the older hard-drive was seemingly working just fine, even with the same SATA cable and connected to the same slot on the Motherboard. Turns out it was using slower PIO by virtue of it being older HDD. During the troubleshooting process I reinstalled fresh Windows 7 64 Bit multiple times, on various HD drives, only to see the issue start happening almost instantly after
Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks. Windows 7 Help Forums Windows 7 help and support Drivers » http://www.sevenforums.com/drivers/124022-event-id-11-atapi.html User Name Remember Me? Password Advanced Search Show Threads Show Posts Advanced Search Go to Page... Windows 7: Event ID 11 ATAPI 10 Nov 2010 #1 ManOwar2 Windows 7 x64 197 posts Montral Event ID 11 ATAPI I posted this in another thread too, but I think this might be related to some drivers maybe an expert on device/drivers can answers me here too. I got an issue, wich I already solved partially, but I need driver detected input to localize the real source of the problem. I need an input from advanced and experienced users with theses kind of problems if possible. I realized this morning that my windows start screen took 3 minutes to load up for the last 2 days. (usually takes 15 second) I opened the even viewer and started to see lot of event ID 7026 The following boot-start or system-start driver(s) failed to load: cdrom and Event ID 15 The device, driver detected a \Device\CdRom0, is not ready for access yet. In the bios, the device was detected but the name displaying was kind of random character that I cannot reproduce with my keyboard. (or I do not know how) Then I lost my second HDD who would not be detected correctly, but came back to normal after a normal reboot. After, I switched the device to another sata port. Now the Bios does not recognize the device DVD-ROM/Cd-ROM...however, windows does and the device work properly again and seen and detected by windows 7 in every services. (before I could not even see it in the device manager) Also, after finding that everything works, I reviewed again the event viewer and found this strange and alarming event : Evend ID : 11 ATAPI The driver detected a controller error on \Device\Ide\IdePort4. My question is, w** ? what about my bios, my sata reading, is something wrong ? should I try again the ''defective'' sata port ? sorry for the brutal ending My System Specs Computer type PC/Desktop OS Windows 7 x64 CPU Intel 4770k Motherboard ASUS MAXIMUS VI FORMULA LGA 1150 Intel Z87 HDMI Memory G.SKILL Ripjaws Series 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 Graphics Card XFX R9 390 OC Sound Card Mobo integrated Monitor(s) Displays Samsung 226BW 22'' Panel A Screen Resolution 1650x1080 PSU 1 x CORSAIR HX Series HX750 750W ATX12V 2.3 / EPS12V 2.91 SL Ca