Driver Detected A Controller Error On Device Cdrom
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 the driver detected a controller error on device cdrom0 server 2008 blue screen. Now that I feel it is fully resolved, I thought I’d the driver detected a controller error on device cdrom0 windows 7 share my conclusion (and the process) – hopefully it will help few others out there who are struggling with this. the driver detected a controller error on device harddisk1 dr1 Ridiculously, many people are likely affected 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
The Driver Detected A Controller Error On Device Harddisk0
for Windows! OS seems to silently recover from this 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 the driver detected a controller error on device harddisk2 dr2 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 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. Durin
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 the driver detected a controller error on device ide ideport0 Hardware & Devices » User Name Remember Me? Password Advanced Search Show Threads Show
The Driver Detected A Controller Error On Device Harddisk0 D
Posts Advanced Search Go to Page... Windows 7: The driver detected a controller error on \Device\CdRom0. Page 1 of 2 1 2 >
The Driver Detected A Controller Error On Device Raidport0
29 May 2010 #1 john13134 windows 7 Home Premium 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 http://www.adir1.com/2012/01/solved-the-driver-detected-a-controller-error-on-deviceideideport2/ and all was going well until i reinserted a disk and when i 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 http://www.sevenforums.com/hardware-devices/88013-driver-detected-controller-error-device-cdrom0.html non responding 5 disk this message or error shows ''The driver detected a controller error on \Device\CdRom0.'' 5 times..what 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 C
Follow 5147 Mentions744 Products Chris (Microsoft) Technical Consultant/SI GROUP SPONSORED BY MICROSOFT TECHNOLOGY IN THIS DISCUSSION Microsoft 491162 Followers Follow Microsoft Windows Server https://community.spiceworks.com/topic/304581-driver-detected-a-controller-error-which-hdd-is-device-harddisk2-dr2 Microsoft Windows Server 2012 Join the Community! Creating your account only takes a few minutes. Join Now Am seeing the following in my 2008R2 Event Viewer: * Event http://www.eventid.net/display-eventid-11-source-CdRom-eventno-1917-phase-1.htm Time: 19 Feb 2013 02:42:19 AM * Source: Disk * Event Log: System * Type: Error * Event ID: 11 * Event User: N/A * The driver detected a controller driver detected error on \Device\Harddisk2\DR2. On this server I have internal RAID volumes, an external iSCSI drive (DroboPro), and several USB 2.0 hard drives attached. How can I determine what hard drive / storage device is "\Device\Harddisk2\DR2"? Thanks in advance for any feedback. Cheers, Derek Reply Subscribe RELATED TOPICS: Driver detected a controller error The driver detected a controller error on \Device\Harddisk1\DR1. driver detected a system Error 1 2 Next ► 28 Replies Cayenne OP murpheous Feb 19, 2013 at 2:42 UTC click start, right click computer and select manage. Expand storage on the left and select disk management. That should tell you. 1 Sonora OP derektom Feb 19, 2013 at 2:56 UTC Thanks for your reply. That's the first place I looked but I'm unsure how to correlate Harddisk2\DR2 to any of those drives. Is "DR2" = "Disk 2"? Attached is a screenshot for reference. Thanks again. 0 Mace OP Rockn Feb 19, 2013 at 3:36 UTC Does diskpart give you more detailed info? 0 Mace OP LarryG. Feb 19, 2013 at 4:05 UTC Do you have any Management software installed for the RAID? That would have it's own logging and hopefully diagnostics too. 0 Jalapeno OP supasieu Feb 19, 2013 at 4:36 UTC Try this link: http://support.microsoft.com/kb/244780/en-us
0 Sonora OP derektom Feb 20, 2013 at 1:13 UTC Thanks for the feedback, Rockn, LarryG., and Fishsauce. diMonitor an unlimited number of servers with $49/year With the current low prices for servers and the need for processing power, even a small company may end up with quite a few of them. If ten years ago it was still common to see an entire company using just one server, these days that's no longer the case. New computers are added to the network with the understanding that they will be taken care of by the admins. Keeping an eye on these servers is a tedious, time-consuming process. Even with 5 minutes per server (to check the logs and other parameters), it may take an hour to make sure that everything is ok and no "red lights" are blinking on any of the servers. read more... Event ID: 11 Source: CdRom Source: CdRom Type: Error Description:The driver detected a controller error on \Device\Scsi\CdRom English: This information is only available to subscribers. An example of English, please! Comments: EventID.Net As per Microsoft: "This problem is typically caused by a failing cable that connects the drive to the computer". See MSW2KDB for more details. From a newsgroup post: "Check the UDMA settings on the IDE channel to which the CDRW/ZIP Drive are attached. I was getting peculiar behavior because Windows 2000 had turned on UDMA for my CDROM (which is definitely not UDMA capable). Also ZIP drives should not be on a port that has UDMA enabled". x 16 EventID.Net This message usually indicates a problem with the CD (especially custom written ones). See also event ID 11 from adpu1160m for a more general explanation. x 13 Private comment: Subscribers only. See example of private comment Links: ME154690, Event ID 11 from adpu1160m, MSW2KDB Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links... Custom search for *****: Google - Bing - Microsoft - Yahoo Feedback: Send comments or solutions - Notify me when updated Printer friendly Subscribe Subscribe to EventID.Net now!Already a subscriber? Login here! Recommend Us Quick Tip Connect to EventID.Net directly from the Microsoft Event Viewer!Instructions Customer services Contact usSupportTerms of Use Help & FAQ Sales FAQEventID.Net FAQ Advertise with us Articles Managing logsRecommended booksNewsletter Links Follow us on FacebookFiregen Log Analyzers Link to us © Copyright 2001-2016 EventID.Net