Driver Detected A Controller Error On Device Raidport1
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows 10Windows 10 MobilePrevious versionsMDOPSurfaceSurface HubLibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Asked by: Event ID 11 - the driver detected ql2300 the driver detected a controller error on device raidport1 a controller error... Windows Server > Windows Server 2008 R2 General - backup exec the driver detected a controller error on device raidport1 Read Only Question 0 Sign in to vote In the Sytem log, I am seeing Event ID 11 the driver detected a controller error on device raidport0 dell - The driver detected a controller error on \Device\Harddiskx\DRy, where x is either 3 or 4 and corresponds to one of two USB hard drives, and y seems to vary the driver detected a controller error on device harddisk1 dr1 (DR5, DR6, DR15, etc.). Usually this event occurs at logon, but not all logons. Sometimes occurances are not correlated with logons.One of the USB hard drives is a Maxstor Basics, the other is a Seagate FreeAgent Go. Since instances of this event occur that reference both hard drives, it seems like the particular hard drive is not the problem. Similarly, moving
The Driver Detected A Controller Error On Device Harddisk0
the connections to different USB ports has no effect, so it seems like the particual USB port is not the problem.Any suggestion about how to eliminate this event?What does DR (as in DR5, DR6, DR15) mean?Thanks. Wednesday, July 01, 2009 5:13 PM All replies 0 Sign in to vote hi there, In almost all cases, the event id 11 message is being posted due to hardware problems with either the controller or, more likely, a device that is attached to the controller in question. The hardware problems can be associated with poor cabling, incorrect termination or transfer rate settings, lazy or slow device responses to relinquish the SCSI bus, a faulty device, or, in very rare cases, a poorly written device driver. for your convinience i have provided the below link http://support.microsoft.com/default.aspx/kb/154690=============================================================\Device|Harddisk1\DP is the device that controls PARTITION on the disk \Device|Harddisk1\DR7 repersents disk as RAW PHYSICAL DRIVE Each disk have one DR device for PHYSICAL DRIVE and one DP device per partition. You can simply use autogenerated SymbolicLink \Device\HardDiskX\Partition0 for RAW volume, and \Device\HardDiskX\Partition(1,2,3...) for logical partitions if you are w
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
The Driver Detected A Controller Error On Device Harddisk2 Dr2
even crashing with blue screen. Now that I feel it is fully resolved, the driver detected a controller error on device ide ideport0 I thought I’d share my conclusion (and the process) – hopefully it will help few others out there who the driver detected a controller error on device cdrom0 are struggling with this. 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 https://social.technet.microsoft.com/Forums/windows/en-US/0baf5650-2c1c-49c9-bfa8-268c6170fc46/event-id-11-the-driver-detected-a-controller-error?forum=windowsserver2008r2general 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 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. http://www.adir1.com/2012/01/solved-the-driver-detected-a-controller-error-on-deviceideideport2/ 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 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
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job https://www.experts-exchange.com/questions/28421463/The-driver-detected-a-controller-error-on-Device-RaidPort0.html Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > The driver detected a controller error on \Device\RaidPort0. Want to Advertise Here? Solved The driver detected a controller error on \Device\RaidPort0. Posted on 2014-04-28 Server Hardware Windows Server 2003 MS Server OS 3 Verified Solutions 6 Comments 5,575 Views driver detected Last Modified: 2014-04-30 HI Guys, I am getting this error on my windows system event logs. I only got it once, I checked my physical disks and there is not any errors, did it repair it self? raidport 0 is the first disk in raid right? thank you. 0 Question by:Kay Facebook Twitter LinkedIn Google LVL 25 Best Solution byTony Giangreco I would check the documentation on that driver detected a raid adaptor to see of it clocks bad sectors when it finds one. it sounds like that's the case, but since you already found an error, I would do it for safety. Go to Solution 6 Comments LVL 2 Overall: Level 2 Windows Server 2003 1 Message Assisted Solution by:YoursJitu2014-04-28 What Machine Make and Model you have? If this is a server you must be having some Vendor application in which you can check if you disk is at fault or not? Normally HP have HP Management Home Page and Dell have Dell Server Administrator. Similarly other vendor do have their application to monitor Hardware Part. If you can post the Make and Model we can try to search for Management Software for you. 0 Message Author Comment by:Kay2014-04-28 we have the intel raid web console and I can't see any errors there. 0 LVL 2 Overall: Level 2 Windows Server 2003 1 Message Expert Comment by:YoursJitu2014-04-28 Then most probably it would have fixed itself. You can check the same from events there after in the System Events. If Intel Web Console shows all disk Healthy then there is nothing to worry about. Just for you to be sure,