Driver Detected Controller Error 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 blue screen. Now that I feel it is fully resolved, I thought
The Driver Detected A Controller Error On \device\harddisk3\dr3.
I’d share my conclusion (and the process) – hopefully it will help few others out there
The Driver Detected A Controller Error On \device\harddisk1\dr2.
who are struggling with this. Ridiculously, many people are likely affected by this issue, but unless they open Event Viewer and search for this the driver detected a controller error on \device\raidport0. 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 that http://answers.microsoft.com/en-us/windows/forum/windows_7-hardware/the-driver-detected-a-controller-error-on/5344543b-a2dd-4b18-b2d4-d15f9e5e3859 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 you are http://www.adir1.com/2012/01/solved-the-driver-detected-a-controller-error-on-deviceideideport2/ 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 that controller was fault
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Sign In CommunityCategoryBoardResourcesUsers https://vox.veritas.com/t5/Backup-Exec/The-driver-detected-a-controller-error-on-Device-CdRom1/td-p/575685 turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting http://superuser.com/questions/1031926/the-driver-detected-a-controller-error-on-device-cdrom0 possible matches as you type. Showing results for Search instead for Do you mean VOX : 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 driver detected New Mark Topic as Read Float this Topic to the Top 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 driver detected 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 activity on the Backup Exec server. I have tried disabling the CR Rom drive in device manager, but this does not solve the problem. (Besides, I don't think having to disable a CD-ROM drive is a valid solution) This message used to say \Device\RaidPort1 until the 27th November where it changed to CDRom1 on the 30th November. No hardware changes have happened at all over the last 2 months. The server is fully uptodate (Windows Updates). Backup Exec is fully upto date (Live Update) The TapeDrive is a Dell PowerVault 124T (LTO4), The server is a Dell PowerEdgeR610 running the latest firmware and drivers. The OS is Windows 2008 Server R2(SP1) X64 Any help or advice woul
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Super User Questions Tags Users Badges Unanswered Ask Question _ Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top The driver detected a controller error on \Device\CdRom0 up vote 0 down vote favorite Thanks for be helping. once I opened my cdrom is server and blew the dust that was closed and then I noticed that this error " The driver detected a controller error on \Device\CdRom0." was appearing every time on events. please can you help me to fix this!? compact-disc share|improve this question asked Jan 27 at 8:49 chivas 11 add a comment| active oldest votes You must log in to answer this question. Browse other questions tagged compact-disc . asked 8 months ago viewed 97 times Related 1can't detect cdrom drive1dvd drive I/O error?4The following boot-start or system-start driver(s) failed to load: cdrom1Why is my CD-ROM device being automatically disabled at boot?1DVD driver stopped recognizing any discs1How can I troubleshoot a MATSHITA UJ8A0ASW optical drive which yelds different errors in different burning softwares?5Install a CD-ROM driver on MS-DOS0How device drivers work like USB , CD, DVD3Maxtor 40GB HDD shows fatal error while installing windows xp from internal CD-ROM0Internal Blu-Ray/DVD Drive Detected in BIOS, not Detected by Device Manager or Explorer Hot Network Questions How can we judge the accuracy of Nate Silver's predictions? How do I debug an emoticon-based URL? Why are so many metros underground? Isn't that more expensive than an elevated system? How do I make this simple program work for any string? Where is my girlfriend? What's an easy way of making my luggage unique, so that it's easy to spot on the luggage carousel? Speed and Velocity in German Why don't you connect unused hot and neutral wires to "complete the circuit"? Can 'it' be used to refer to a person? Invariants of higher genus curves Why does the ISS track appear to be sinusoidal? How to work on downloaded copies of database tables in QGIS Can my boss open and use my computer when I'm not present? 2048-l