Event Error 11 Disk
Contents |
360 games PC games event id 11 disk the driver detected a controller error Windows games Windows phone games Entertainment All Entertainment event id 11 the driver detected a controller error on device harddisk1 dr1 Movies & TV Music Business & Education Business Students & educators event id 11 windows 7 Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet event id 11 atapi Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Lumia All
Event Id 11 Kerberos-key-distribution-center
Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
Server: Disk Event 11 in the System Event Log Article Summary: This article provides information on event ID 11 (source Disk) in the System log of a Windows server. The error description reads
Event Id 11 Wininit
as follows: The driver detected a controller error on Device\Harddisk#\DR#. event id 11 rpc This description is followed by several lines of hexadecimal data that can be used in troubleshooting if event id 11 custom dynamic link libraries necessary. Microsoft has published several articles about this and other related errors. If a hardware issue is suspected, these articles may be useful in determining exactly what https://support.microsoft.com/en-us/kb/154690 hardware is at fault: How to Troubleshoot Error Messages about Event ID 9 and Event ID 11 How to Troubleshoot Event ID 9, Event ID 11, and Event ID 15 Error Messages The error does not necessarily indicate a problem with the server, especially if the disk number in Harddisk# is greater than the highest http://www.dell.com/support/article/us/en/04/SLN167235/en disk number that appears in Disk Management. In this case, the error is likely associated with a USB drive attached to the server. There is no authoritative list of USB drives compatible with different versions of Windows Server; however, the Windows Small Business Server (SBS) team has compiled a list of USB drives and the degree to which they function with SBS. It can be assumed that a drive which is compatible with a particular version of SBS will also be compatible with the corresponding version of Windows Server, as they are built upon the same kernel. Quick Tips content is self-published by the Dell Support Professionals who resolve issues daily. In order to achieve a speedy publication, Quick Tips may represent only partial solutions or work-arounds that are still in development or pending further proof of successfully resolving an issue. As such Quick Tips have not been reviewed, validated or approved by Dell and should be used with appropriate
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 subscribers Event ID: 11 Source: Disk Source: http://www.eventid.net/display-eventid-11-source-Disk-eventno-616-phase-1.htm 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 due to failing battery on PERC 6/i. Changed Write Policy from http://www.adir1.com/2012/01/solved-the-driver-detected-a-controller-error-on-deviceideideport2/ 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 event id 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 ‹•ż•› 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 event id 11 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" and I changed it to "Master". x 307 Anonymous I got this error in my event viewer along with these: Event ID: 129 Source: HpCISSs2 Description: Reset to device, \Device\RaidPort0, was issued. Event ID: 24800 Source: Cissesrv Description: Logical drive 1 configured on array controller [Embedded] returned a fatal error during
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 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 i