Driver Detected Controller Error Cdrom1
Contents |
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 I feel it is fully resolved, I thought
The Driver Detected A Controller Error On Device Ide Ideport0
I’d share my conclusion (and the process) – hopefully it will help few others out the driver detected a controller error on device harddisk2 dr2 there who are struggling with this. Ridiculously, many people are likely affected by this issue, but unless they open Event Viewer and search for the driver detected a controller error on device harddisk0 this event id 11, they will not realize that hanging is not “normal” behavior, even for Windows! OS seems to silently recover from this problem 10 to 60 seconds later, which is really strange in my book – considering
The Driver Detected A Controller Error On \device\ide\ideport1.
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 is that this is likely a disk controller error, which is especially problematic since nowadays disk controllers are built into the Motherboard. If
The Driver Detected A Controller Error On \device\ide\ideport2.
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 clean install. Few days ago a fresh HDD became available (separate long story), so I tried replacing the “dying” HD. Guess what, it being newer HD, it was instantly affected by the same issue, even though I put clean Windows there also. Thus it was concluded tha
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 Hardware & Devices » User Name the driver detected a controller error on \device\harddisk3\dr3. Remember Me? Password Advanced Search Show Threads Show Posts Advanced Search Go to Page... Windows 7:
The Driver Detected A Controller Error On \device\harddisk1\dr2.
The driver detected a controller error on \Device\CdRom0. Page 1 of 2 1 2 > 29 May 2010 #1 john13134 windows 7 Home Premium the driver detected a controller error on \device\raidport0. 83 posts The driver detected a controller error on \Device\CdRom0. The title says it all friends... i have recently been burning some dvd's DVD+R by the way and all was going well until i reinserted a disk and when i http://www.adir1.com/2012/01/solved-the-driver-detected-a-controller-error-on-deviceideideport2/ went to Start,Computer and E Drive it would go milky white and would get the infamous NOT RESPONDING message i successfully burned 10 out of the 15 disk the other 5 take forever to appear with the open file option and i get the not responding message i go to check my Event Viewer and the exact number of attempts made to play the non responding 5 disk this message or error shows ''The driver detected a controller error on \Device\CdRom0.'' 5 times..what http://www.sevenforums.com/hardware-devices/88013-driver-detected-controller-error-device-cdrom0.html does it mean? i have had this problem for a while now and sorta happens at random times i even tried burning different files with a new disk but while my software [imgburn] says it's complete i continue to get prolonged waiting followed up by not responding very frustrating, and help anyone can give me would be appreciated thanx in advance My System Specs OS windows 7 Home Premium Memory 5gb Graphics Card Nvdia john13134 View Public Profile Find More Posts by john13134 . 29 May 2010 #2 john13134 windows 7 Home Premium 83 posts anyone? My System Specs OS windows 7 Home Premium Memory 5gb Graphics Card Nvdia john13134 View Public Profile Find More Posts by john13134 29 May 2010 #3 derekimo Win 10 Pro x64 17,234 posts East Bay Area, CA Quote: Originally Posted by john13134 anyone? It's only been 20 minutes, It might take awhile but someone will definately post something once they see this. My System Specs Computer type PC/Desktop System Manufacturer/Model Number Self Built OS Win 10 Pro x64 CPU Intel I5-2500K @3.3GHz Motherboard Asrock P67 Extreme4 Memory 16GB G.Skill Ripjaws X (4x4GB) Graphics Card EVGA GeForce 750 Ti SC 2GB Sound Card ASUS Xonar DG 5.1 Channels 24-bit 96KHz PCI Interface Sound Monitor(s) Displays auria eq2367 Screen Resolution 1920 x 1080 Keyboard Logitech Wireless Keyboard K520 Mouse Logitech Wireless Mouse M310 PSU SeaSonic X 650W 80 Plus Gold Case Corsair Obsidian 750D Cooling Corsair H60, Thr
open for further replies. philby Registered Member Joined: Jan 10, 2008 Posts: 940 Hello again I was trying to help someone else today (my first mistake ) and wanted to image their system prior to tinkering in case of disaster using Macrium boot disk. I found I couldn't boot from the http://www.wilderssecurity.com/threads/the-driver-detected-a-controller-error-on-device-cdrom1.270492/ optical drive so, once into the machine, I checked Event Viewer (Vista SP1) and found about 34000 entries (!!) under system as per thread title. I tried a number of different dvd/cd brands and the best I could get via right-click > explore or open in Explorer was a brief flash of an empty Explorer window. The optical drive was reported as present and working correctly in Device Manager. All I could think of doing was to uninstall the relevant driver in Device Manager and force the driver detected hardware to be re-detected by Windows. This had no effect at all. I also scanned with MBAM / Prevx / HMP just in case the drive had been somehow hijacked and looked for anything immediately dodgy in Autoruns - nothing obvious (to me anyway). Clutching pointlessly at straws, I also turned Autoplay off, on and then off again - no change. In short, my question is: Does the Windows error message necessarily mean it was a hardware issue (IDE cabling etc.) or could there be something else on the driver detected the soft-side that I should have looked at? Another unsatisfactory outcome - I'm having a bad week.... Thanks in advance for any pointers. philby philby, Apr 17, 2010 #1 Cudni Global Moderator Joined: May 24, 2009 Posts: 6,956 Location: Somethingshire what is the error id code? I think you are right in suspecting hardware more. A new drive will be needed Cudni, Apr 17, 2010 #2 philby Registered Member Joined: Jan 10, 2008 Posts: 940 I think it was Event ID 11, but that's all I recall. I think you are right in suspecting hardware more. A new drive will be neededClick to expand... Thanks Cudni - feel a little bit better about it now. philby philby, Apr 17, 2010 #3 mvario Registered Member Joined: Sep 16, 2008 Posts: 339 Location: Haddonfield, IL Try a bootable disc, like a linux live disc. Set the bios to boot from it and cycle the power off and on. If it doesn't boot then it's likely hardware (check the cables) mvario, Apr 17, 2010 #4 Novastar 3d Registered Member Joined: May 3, 2009 Posts: 59 mvario said: Try a bootable disc, like a linux live disc. Set the bios to boot from it and cycle the power off and on. If it doesn't boot then it's likely hardware (check the cables)Click to expand... I wouldn't ever try a LINUX live CD on a windows machine again, but thats just me. I had similar problems As Philby AFTER trying it last time. Novastar 3d, Apr 19, 2010 #5 Sully Registered Member