Driver Detected A Controller Error On Device 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 the driver detected a controller error on device harddisk1 dr1 blue screen. Now that I feel it is fully resolved, I thought I’d share the driver detected a controller error on device harddisk0 my conclusion (and the process) – hopefully it will help few others out there who are struggling with this. Ridiculously, the driver detected a controller error on device harddisk2 dr2 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 for Windows! the driver detected a controller error on device ide ideport0 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 or another
The Driver Detected A Controller Error On Device Cdrom0
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. During the troubleshooting process I r
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside
The Driver Detected A Controller Error On Device Harddisk0 D
Veritas Vision 2016 Developers Blogs Groups Vision 2016 Sign In the driver detected a controller error on device raidport0 CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps the driver detected a controller error on device raidport1 you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX : http://www.adir1.com/2012/01/solved-the-driver-detected-a-controller-error-on-deviceideideport2/ Backup and Recovery : Backup Exec : The driver detected a controller error on \Device\... VOX : Backup and Recovery : Backup Exec : The driver detected a controller error on \Device\... Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top https://vox.veritas.com/t5/Backup-Exec/The-driver-detected-a-controller-error-on-Device-CdRom1/td-p/575685 Bookmark Subscribe Printer Friendly Page The driver detected a controller error on \Device\CdRom1 leeweedon Level 5 12-03-2012 12:51 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Good morning. For the last few weeks we keep getting the following Alert: Storage Information message on our BackupExec 2012 server. The following event was reported on 11/30/2012 10:10:13 AM: The driver detected a controller error on \Device\CdRom1. -------------------- This error signifies controller errors. These errors are generally caused by hardware that is not functioning correctly. To resolve these errors, try the following actions: - Slow the SCSI bus. - Verify that the latest SCSI drivers and firmware are loaded. If these errors continue to occur, contact the hardware manufacturer. This message happens every 15 minutes, to an hour. Even when there is no backup job running or any
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 http://www.wilderssecurity.com/threads/the-driver-detected-a-controller-error-on-device-cdrom1.270492/ wanted to image their system prior to tinkering in case of disaster using Macrium boot disk. I found I couldn't boot from the optical drive so, once into the machine, I checked http://www.techspot.com/community/topics/the-driver-detected-a-controller-error-on-device-cdrom0-error.105092/ 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 > driver detected 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 hardware to be re-detected by Windows. This had no effect at all. I also scanned with MBAM / Prevx / driver detected a 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 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 mvar
TechSpot RSS Get our weekly newsletter Search TechSpot Trending Hardware The Web Culture Mobile Gaming Apple Microsoft Google Reviews Graphics Laptops Smartphones CPUs Storage Cases Keyboard & Mice Outstanding Features Must Reads Hardware Software Gaming Tips & Tricks Best Of Downloads Latest Downloads Popular Apps Editors Picks Device Drivers Product Finder New Releases New PC Games Laptops Smartphones Routers Storage Motherboards Monitors Forums Recent Activity Today's Posts News Comments TechSpot Forums Forums TechSpot Core Storage Today's Posts The driver detected a controller error on \Device\CdRom0error Bykimboy May 17, 2008 I bought a Samsung SH-S202N DVD Writer. I installed it properly but whenever I insert a CD or DVD into it Windows hangs (nothing happens,even the mouse pointer doesn't move, Task Manager can't open, dead nothing). Checking Event Viewer I found the following: "The driver detected a controller error on \Device\CdRom0." When I remove the media from the drive Windows ceases hanging. Can anyone help me out? Thanks in advance. P.S: I don't think it's the IDE cables, I've already replaced them 3 times but no change. :evil: May 17, 2008 #1 CCT TS Evangelist Posts: 2,653 +6 Is that the only drive on that IDE cable? What jumper setting and what connector is it using (end/middle) ? May 17, 2008 #2 kimboy TS Rookie Topic Starter Posts: 39 I have 1 HDD and the DVD drive. The HDD is on the end. I have set the jumper settings to Cable Select on both drives. Now it keeps on hanging, I'm also receiving errors and warnings in the Event Viewer about event ID's 51("An error was detected on device \Device\CdRom0 during a paging operation") and 7("The device,\Device\CdRom0,has a bad block"). What can it be? Could the drive's firmware be faulty? May 17, 2008 #3 CCT TS Evangelist Posts: 2,653 +6 Change the CD to slave and the HD to Master. Is that a 80 pair 40 connector cable? If so, the HD goes on the end - see; http://www.mikeshardware.com/howtos/howto_connect_ide_hd.html May 17, 2008 #4 (You must log in or sign up to reply here.) Show Ignored Content Topic Status: Not open