Driver Detected Controller Error Event Id 11 Source Disk
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 a controller error... Windows Server > event id 11 the driver detected a controller error on device harddisk1 dr1 Windows Server 2008 R2 General - Read Only Question 0 Sign in to the driver detected a controller error on device harddisk2 dr2. event id 11 vote In the Sytem log, I am seeing Event ID 11 - The driver detected a controller error on \Device\Harddiskx\DRy, where the driver detected a controller error on device raidport1 event id 11 x is either 3 or 4 and corresponds to one of two USB hard drives, and y seems to vary (DR5, DR6, DR15, etc.). Usually this event occurs at logon, but not all the driver detected a controller error on device ide ideport2. event id 11 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 connections to different USB ports has no effect, so it seems like the particual USB port is not
Event Id 11 Disk
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 writing your own device drivers.if you need still more indepth detailIOCTL_VOLUME_GET_VOLUME_DISK_EXTENTS can determine the PhysicalDisk# given a volume handle.sainath !analyze Wednesday, July 01, 2009 6:37 PM Moderator 0 Sign in to vote Thanks for your quick reply.I'm only seeing Even
Analyzer Sample report Advanced filtering Direct links to www.eventid.net Email notifications Scheduled reporting Free for subscribers EventReader Event Viewer Sample report Custom views/filters Servers list, organized in groups Integration with EventID.Net Consolidated view for all logs Free for
Event Id 11 Atapi
subscribers Event ID: 11 Source: Disk Source: Disk Type: Error Description:The driver detected event id 11 windows 7 a controller error on \Device\Harddisk0\DR0 English: This information is only available to subscribers. An example of English, please! Comments: Sf4000 We had event id 11 wininit it due to failing battery on PERC 6/i. Changed Write Policy from Write Back to Write Through - the event stopped popping up. P.S. The Write Through Policy was a temporary solution till the new controller 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 battery has arrived. x 233 Anonymous I've had three of these errors pop up on our Level Platforms alerts. One of them I was able to find the cause by simply installing Dell OpenManager Server Administrator and taking a look at the storage.The firmware driver was out of date. That would be a good first place to start. The other two alerts did not have a similar find. x 309 W4tch3r http://www.eventid.net/display-eventid-11-source-Disk-eventno-616-phase-1.htm I am getting this error using multiple drives in a Shintaro USB3 drive caddy. After lots of drive and cable swapping I have discovered it happens because I have the drive caddy plugged into a Noontec USB3 hub. When I bypass the hub and go straight to the PC it does not happen. I do not know yet if the problem is with the Noontec hub or the Shintaro drive dock. x 315 Alexander Freudenberg In certain conditions, this error message is related to the S.M.A.R.T attribute 187 (Reported uncorrectable errors). When a physical sector of the disk is read by an application (e.g. a SMART test tool or a simple copy command) and a sector is "unstable", meaning that the drive electronics (hardware ECC) is unable to correctly read the sector, then Windows logs Event ID 11. To solve the error, a full SMART scan with repair (reallocation of unstable sectors) should be performed. x 352 Anonymous I got this error after buying a new power supply. Luckily I found the reason after trying every solution I found on the Internet. It seems that the jumper setting from my IDE drive, which worked with my old power supply, wouldn't do so with the new supply. My jumper setting was "Force Dev1 present"
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 http://www.adir1.com/2012/01/solved-the-driver-detected-a-controller-error-on-deviceideideport2/ I’d share my conclusion (and the process) – hopefully it will help few others out there who are struggling with this. Ridiculously, many people are likely affected by this issue, but unless they open Event Viewer and search for http://superuser.com/questions/141064/system-event-id-11-disk 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 that event id 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 event id 11 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 that contr
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 System Event ID 11 Disk up vote 3 down vote favorite Upon starting Windows Server 2008 R2 I get this error message: Event ID 11 Disk The driver detected a controller error on \Device\Harddisk3\DR3. There are also also 3 more similar messages for Harddisk 2, 4, and 5, but not zero or 1. Checking the event viewer reveals it's been going on for 3 months. I ran chkdsk - no bad sectors. Any advice on the cause, better still, a solution? hard-drive windows-server-2008-r2 controller share|improve this question edited May 14 '10 at 9:22 quack quixote 31.3k1068114 asked May 14 '10 at 8:44 Guy Thomas 2,39282544 add a comment| 1 Answer 1 active oldest votes up vote 1 down vote accepted I saw these errors when one of my RAID controllers was failing. You may find the below knowledge-base article helpful, although it provides general starting points rather than in-depth troubleshooting. In almost all cases, these messages are 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. http://support.microsoft.com/kb/154690 Note that it can also be caused by using consumer grade drives with a RAID controller that expects writes to complete quickly. Although a write using a consumer grade drive my complete successfully, the RAID controller will report a timeout. I think Western Digital drives are more prone to this than any other. This may also be helpful. share|improve this answer answered May 14 '10 at 10:09 ta.speot.is 12.7k12142 Thanks for the info. However, I should have mentioned that I had scanned those kbs, but dismissed them as I don't have SCSI, RAID or Clusters. Just a basic disk system. –Guy Thomas May 14 '10 at 11:48 The