Event Id 11 Disk Controller Error Windows 7
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Thu, 13 Oct 2016 18:04:53 GMT by s_ac5 (squid/3.5.20)
Add-on Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows
Event Id 11 Kerberos-key-distribution-center
events to www.eventid.net. TheEventId.Net for Splunk Add-onassumes thatSplunkis collecting information from event id 11 rpc Windows servers and workstation via the Splunk Universal Forwarder. read more... Event ID: 11 Source: Disk Source: event id 11 custom dynamic link libraries Disk Type: Error Description:The driver detected a controller error on \Device\Harddisk0\DR0 English: This information is only available to subscribers. An example of English, please! Comments: Sf4000 We had it http://answers.microsoft.com/en-us/windows/forum/windows_7-hardware/event-id-11-disk-the-driver-detected-a-controller/fb0e7207-2bde-4fcd-b1b8-643a9f20196a 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 battery has arrived. x 233 Anonymous I've had three of these errors pop up on our Level Platforms alerts. One of them I http://www.eventid.net/display-eventid-11-source-Disk-eventno-616-phase-1.htm 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 ‹•ż•› 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 e
Chris (Microsoft) Technical Consultant/SI GROUP SPONSORED BY MICROSOFT TECHNOLOGY IN THIS DISCUSSION Microsoft 492071 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: * http://www.adir1.com/2012/01/solved-the-driver-detected-a-controller-error-on-deviceideideport2/ Event 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 event id a controller 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 event id 11 controller error on \Device\Harddisk1\DR1. 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:13ordeal 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 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 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 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 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 faulty, and I