Shortly after every time my Windows wakes from sleep I get an EventID 11 error:
The driver detected a controller error on \Device\Harddisk2\DR2
This is for a Western Digital 3TB USB 3 external drive. I have not seen any other recent problems with the drive. (I shuffled around several external drives a few days ago so I can't tie DR2 to a specific drive in older event records.)
Is this anything to worry about, or is it just a timing problem?
Hello pokeefe0001!
I'm sorry for the issue you're having!
Which model of external WD drive is this? What other drives (internal or external) do you have? Please post a screenshot of Disk Management.
This could be a problem with the controller the HDD is connected to, which is basically a motherboard issue. Still, try the drive on another system, restart a few times, see if the same error comes up.
This Microsoft KB may be able to help you:
https://support.microsoft.com/en-us/kb/154690
Post back! :)
CK_WD
As it's when the computer is waking from sleep it could be that the USB driver is experiencing a power state failure. Check that your USB 3.0 drivers are up to date.
To CKWD:
This is a WD My Book 1230 USB 3.0 3TB drive. I seem to be using a a default Microsoft driver, version 6.1.7600.16385 dated 6/21/2006. I'll see if there is a newer driver from WD.
Note that I've experienced no apparent problems with the drive - just the logged event record.
To Boozard:
I'm really vague about USB 3.0 support. In the Device Manager I see 2 USB 3 related resources:
Intel(R) USB 3.0 eXtensible Host Controller - Driver version 2.5.0.19, 3/29/2013Seems to be the same driver for both. Searching the web I see a newer driver on an Intel web site: Version 1.0.10.255, 02/03/2014. However, if I let Windows do a search via the "Update Driver" function, it says I've got the latest driver. I don't know what process Microsoft uses to search for new drivers; I suspect it is just not finding the update. Still, I'm reluctant to update a driver that Windows thinks is current.
Intel(R) USB 3.0 Root Hub - Driver version 2.5.0.19, 3/29/2013
If there's a more recent version offered on the Intel website download it the install it. Create a Restore Point before installation if you wish.
The description of the driver says "... for Intel® 7 Series/C216 Chipset Family".
I have an i7-4771 CPU. Wikipedia (an absolute authority on such things, of course) says this CPU is "used in conjunction with the Intel 8 Series chipsets and Intel 9 Series chipsets".
I just found an almost 2 year old Softpedia page describing a "new" driver version 2.5.1.28 for the 4th generation Core processor. The version number of that driver is more in line with my current driver, but I think I'd better continue searching. I'm almost certain that "version 1.0.10.255" is not for my PC.
Update:
Looks like the version 3.0.5.69, 04/17/2015 driver is compatible with my PC. I hope. The Intel Download web page says it's for (among others) the 4th generation Core processors. It would be nice if they has specifically mentioned my CPU (or even said i7-4nnn), but I read somewhere else that the "4" in i7-4771 is the "4th generation" indicator. Maybe everybody is supposed to know that, but I can guarantee that at least one person didn't.
I've definitely created a restore point!
Last edited by pokeefe0001; 26 Aug 2015 at 13:22.
I forgot to update this. I installed the update with no problem. It's now being used but did not get rid of the error.
I was under the impression that the controller for a USB-attached drive was actually in the case with the drive, not on the motherboard. I thought the MB had the USB controller but not the disk controller.
I have not yet tried the device on another PC. I'll see if I can do that later today.
I've read that, but it did not seem to address USB drive-attached drives. In fact it seems to address only SCSI-attached drives. It was last reviewed on 02/26/2007.
BTW, I have found a report of this problem on the WD forum from January 2014:
WD External USB drive causing Windows Event ID 11 - WD Community
No solution was suggested, but the poster said replacing the drive reduced the number of logged event by 90%.
Quote