Driver Detected A Controller Error On Device Harddisk1 Dr 5
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 > driver detected a controller error on device harddisk1 dr1 Windows Server 2008 R2 General - Read Only Question 0 Sign in to vote driver detected a controller error on device harddisk1 dr2 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 harddisk1 dr6 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 Harddisk1 Dr1 Server 2008
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 the the driver detected a controller error on device harddisk1 dr1 windows 7 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 Event
Chris (Microsoft) Technical Consultant/SI GROUP SPONSORED BY MICROSOFT TECHNOLOGY IN THIS DISCUSSION Microsoft 491162 Followers Follow Microsoft Windows Server the driver detected a controller error on device harddisk1 dr1 server 2008 r2 Microsoft Windows Server 2012 Join the Community! Creating your account only
The Driver Detected A Controller Error On Device Ide Ideport0
takes a few minutes. Join Now Am seeing the following in my 2008R2 Event Viewer: * Event
The Driver Detected A Controller Error On \device\harddisk3\dr3
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 a 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 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 controller error on https://community.spiceworks.com/topic/304581-driver-detected-a-controller-error-which-hdd-is-device-harddisk2-dr2 \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:13 UTC Thanks for the feedbaordeal 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 http://www.adir1.com/2012/01/solved-the-driver-detected-a-controller-error-on-deviceideideport2/ 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 driver detected 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 driver detected a 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 went shopping for a new motherboard. As an aside – DDR3 me