Driver Detected A Controller Error On Device Harddisk1 Dr4
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 driver detected a controller error on device harddisk1 dr1 Server > Windows Server 2008 R2 General - Read Only Question 0 Sign driver detected a controller error on device harddisk1 dr2 in to vote In the Sytem log, I am seeing Event ID 11 - The driver detected a controller the driver detected a controller error on device harddisk1 dr6 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 (DR5, DR6, DR15, etc.). Usually this event occurs the driver detected a controller error on device harddisk1 d 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 connections to different USB ports has no effect, so it seems
The Driver Detected A Controller Error On Device Harddisk1 Dr2 Windows 7
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 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
Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks. Windows 7 Help
The Driver Detected A Controller Error On Device Harddisk1 Dr9
Forums Windows 7 help and support BSOD Help and Support » User Name Remember the driver detected a controller error on device harddisk1 dr1. usb Me? Password Advanced Search Show Threads Show Posts Advanced Search Go to Page... Windows 7: The driver detected a controller the driver detected a controller error on device harddisk1 dr11 error on \Device\Harddisk1\DR1 Page 1 of 4 1 23 > Last » 13 Jul 2011 #1 urusai11 Windows 7 Ultimate 32bit 3 posts The driver detected a controller error on \Device\Harddisk1\DR1 Hello 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 to everyone, I Just want to confirm something, I'm using Windows 7 Ultimate 32bit and not encountering any freezing nor BSOD, but everytime I check the EVENT VIEWER it annoys me to see the error message "The driver detected a controller error on \Device\Harddisk1\DR1" ... I check the disk manager and from what I see in there my primary harddisk is located in channel0/Disk 0 while Disk1 is from my removable http://www.sevenforums.com/bsod-help-support/175034-driver-detected-controller-error-device-harddisk1-dr1.html USB flash drive. Does that mean the one mentioned in the EVENT was just actually my flash drive? Why was it called a harddisk??? Please someone confirm this for me because I'm getting paranoid if my harddisk is already starting to fail. Thanks for any helpful reply... My System Specs OS Windows 7 Ultimate 32bit urusai11 View Public Profile Find More Posts by urusai11 . 14 Jul 2011 #2 zigzag3143 Win 8 Release candidate 8400 2,137 posts Quote: Originally Posted by urusai11 Hello to everyone, I Just want to confirm something, I'm using Windows 7 Ultimate 32bit and not encountering any freezing nor BSOD, but everytime I check the EVENT VIEWER it annoys me to see the error message "The driver detected a controller error on \Device\Harddisk1\DR1" ... I check the disk manager and from what I see in there my primary harddisk is located in channel0/Disk 0 while Disk1 is from my removable USB flash drive. Does that mean the one mentioned in the EVENT was just actually my flash drive? Why was it called a harddisk??? Please someone confirm this for me because I'm getting paranoid if my harddisk is already starting to fail. Thanks for any helpful reply... Yes it is the USB Cal
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, http://www.adir1.com/2012/01/solved-the-driver-detected-a-controller-error-on-deviceideideport2/ 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 https://www.experts-exchange.com/questions/26299634/We-occasionally-get-a-driver-controller-error-event-ID-11-but-drives-check-out-ok-Cause-for-concern.html 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 driver detected 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 driver detected a 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
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 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 > We occasionally get a driver controller error (event ID) 11, but drives check out ok. Cause for concern? Want to Advertise Here? Solved We occasionally get a driver controller error (event ID) 11, but drives check out ok. Cause for concern? Posted on 2010-06-30 Storage Hardware Windows 7 Hardware 2 Verified Solutions 58 Comments 5,687 Views 1 Ratings Last Modified: 2012-05-09 Hi Experts, we run three different external hard drives on our main system for keeping copies of important data. These drives are used regularly. They are all fairly new and so is the system. The system itself is a brand new install of Windows 7, and the diagnostics have been run on the system and it seems to be running flawlessly and with the latest drivers. However, we occasioanlly get the following error in the system log "The driver detected a controller error on \Device\Harddisk1\DR5." It's USUALLY when the drive is first plugged in for the day, however, not necessarily. Sometimes it occurs sporadically once or twice throughout the day. It is NOT when the drive is being used. Full backups are sent to these drives regularly and it never seems to throw these events then. Backups complete fine and verify fine. The drives are all Seagate (purchased within a week or two of each other) and Seatools has been run on all of them, says they are all good. Also, it seems to happen with all three drives. Anyone have any input on the error? Thanks! Log Name: System Source: Disk Event ID: 11 Task Category: None Level: Error Keywords: Classic User: N/A Computer: PC1 Description: The driver detected a controller error on \Device\Harddisk1\DR5. Event Xml: