The driver detected a controller error on \Device\Harddisk2\DR3.

[julio99]

This error has to be the most frustrating I have yet to come across. There are tons of writings on this but you never really get anywhere that is understandable to me and most of the folks that have had the same error. I know what device that is causing this because it only happens when I have either my Verbatim external drive or any one of 5 different USB sticks. I am running Windows 7 x64 with a Corsair 220 gb SSD. I have a second hard drive which is all data. I call it my D:\Drive. Everything in Event Viewer is great until one of the USB or Verbatim external drive is plugged in and then the errors start. I have run chk /dsk on all USB's and the external drive and no help. There are no BSODs or Hangs or boot problems, so you may ask why I'm concerned. Well I believe there has to be some sort of explanation for this error and I really would love to get to the bottom of it before it is an issue. It's strange that all the articles from Microsoft that concern this really say nothing. Nothing simple anyway. If anyone is familiar with this error and what it really means please let me know. I actually took this to a repair tech and he said if it's not giving me problems don't bother with it. Glad I didn't have to pay for that.

 

[Mellon Head]

Hard disk 2 would be your third hard disk, or potentially the USB disk. There might be a problem with the USB driver, or hardware (controller).

Have you tried plugging in the USB drives into other USB ports on the machine? Do you have another computer that you could plug these devices into? That would rule out damaged USB devices that may have been damaged by a faulty port on your PC.

 

[julio99]

Ok. Had to do some testing and here is pretty much what I found. At this time, none of the other times, strictly today I tested all the USB sticks and the external drive and I went to my little 15" ACER x86 and none of the usbs reacted with the error and on my 18.4" ACER x64 the only USB stick that reacted this time was the Cruzer/Sandisk 4GB USB stick. Very strange that this one is the only one that is still popping that error. By the way the Stick is formatted to FAT32

 

[Mellon Head]

I would try not using that Sandisk Cruzer for a while and see if the error comes back with the USB sticks and the drive.

 

[julio99]

I would try not using that Sandisk Cruzer for a while and see if the error comes back with the USB sticks and the drive.

That is about all I can do. You see how many people usually write in these forums and you are the only one that stepped up here. The amount of reading I have done on this error and I just can't get to the bottom of it so we'll leave it as it is and that's good. I won't be using the Sandisk Cruzer at all except to clear the Data on it to another USB.

 

[Mellon Head]

Let me know if the problem comes back with the other drives. Maybe there's something else we can try if it does.

 

[TVeblen]

Every time you connect a new storage device Windows will install a driver for it. This 'driver' essentially identifies the unique device and tells the controller how to communicate with it. If the device does not behave exactly as the controller expects, or vice versa, then it gets chalked up as an error.

If this only happens with the Sandisk stick, or after using the Sandisk stick, then it could be that the stick is simply not following proper communications protocol. Something Sandisk has been having trouble with recently.

These errors can be ignored if it is the case of miscommunication. But if it were to happen with different drives independently then it might indicate a controller driver corruption requiring the reinstallation of either the USB controller drivers or the SATA controller drivers (in the case of errors with internal hard drives).

 

[jeffshead]

I'm posting this same info to the top few search results on Google...

I spent many, many hours researching and testing to find a solution to the Event ID 11 (“The driver detected a controller error on \Device\Harddisk...”) errors in the Event Viewer as well as other related errors and it taking several minutes for a drive letter to be assigned to a USB thumb drive after insertion.

If you encounter this issue when inserting a USB thumb drive in a Win7 PC, disable Autoplay via:

gpedit.msc Computer Configuration->Administrator Templates->Window Components->Autoplay Policies->Turn off Autoplay

 

[RolandJS]

"...gpedit.msc Computer Configuration->Administrator Templates->Window Components->Autoplay Policies->Turn off Autoplay..."
Would that also affect autoplay across the board, i.e., no more simply inserting a DVD and having it acted upon by a designated program?

 

[jeffshead]

"Would that also affect autoplay across the board, i.e., no more simply inserting a DVD and having it acted upon by a designated program?

It does just as it says... It turns off Autoplay, period. I don't use DVD's or CD's anymore so it does not matter to me. As far as I know, there is no way to disable Autoplay for USB devices, only.

I added my post to help those that have encountered the originally reported issue with USB devices. Autoplay is the culprit (for me at least). I have wasted time and money on this issue. I bought new hardware and installed Windows several times before figuring out that Autoplay is causing the issue.

If you are experiencing this issue with USB devices and you need Autoplay for DVD's and CD's, then what I suggested may not be a solution for you.

 

[RolandJS]

Thanks for the info, Jeff! I will remember those things