Thanks for joining the chipset community.
I understand you are experiencing problems with USB 3.0 external hard drive.
I would like to know if this issue happens with another USB 3.0 drive, different brand.
Have you tried updating your motherboard BIOS? According to Gigabyte, their latest version is F5.
Also, provide USB 3.0 driver version you have tested on your computer and operating system version.
I am looking forward to hearing from you.
I have updated my mobo BIOS, yes. It is currently at F5. My OS is Windows 7 Ultimate, updated with all current patches. The Intel USB 3.0 driver version I'm using is 126.96.36.199 - hope this helps.
I have not tried out a different USB 3.0 drive, however it's on my to do list. It is definitely possible that the drive is the fault here somehow. Though it is weird that the drive worked fine before the driver update, which leads me to believe that this can be fixed with software patches somehow.
I have observed the same behavior on an HP z230 workstation. Once I ran the Intel USB3 installer from the HP website (sp65041) my Patriot Gauntlet 2 enclosure was no longer recognized when attached to a USB3 port. But if I connect to a USB2 port it is seen without issue. The issue is also limited to the OS, I can boot off the drive on a USB3 port without issue and even capture a disk image from winpe. I have even encountered the same issue with my Surface Pro 2.
Thanks for the information.
I would like to know if this issue is happening to you with the latest USB 3.0 drivers posted on our site.
Please hit the link below to get latest version:
I recommend remove any USB 3.0 drivers from Control Panel and then re install it.
yes this happens even with the latest drivers from the intel site. the funny thing is the readmes show the same driver version of 188.8.131.52. However the HP download shows a release date of Dec 2013 while the Intel download shows Feb 2014.
possibly related, when you sysprep Win 7 on a z230 and get to the screen where you set the hostname, all USB devices die even with the driver loaded and the unattend set for "PersistAllDevices".
Edit - actually the latest drivers from the Intel site do not work, the device id for the controller isn't listed in the inf.
Driver version 184.108.40.2067 - 2013-02-25 does not experience this issue.
l have the same problem as TesnX built the system a week ago, using the same version usb 3.0 driver. my motherboard is Gigabyte GA-Z87-D3HP.
tho my problem is related to weirdness with my wireless, l have full signal on my adapter but the speed is all over the place jumping between 140meg and 35meg the ones that came with the original CD werent much better, that said l did update my wireless drivers and the connection didnt timeout as much after updating to the latest usb 3.0 drivers but the wireless performance could be allot better, l do have a usb 3.0 thumb drive that does work but l believe the front headers on my computer are only usb 2.0 spec but l do get a bubble noting that the drive could work faster.
either way it would be useful to sort this problem out as it seemed when l experienced a bsod (a different problem which was most likely ram related) noted the driver issue with my wireless and usb 3.0 (but as l said wireless driver has been updated) which leaves sorting out the driver for the usb 3.0 ports.
just received a message from Gigabyte recommending l update to bios version: F14b
will sort this once lm back home in a few days.. l just hope l can use @bios and that sorting it out is simple, not had good experiences updating the bios in the past, l dont want to end up with an unbootable PC.. but lm hoping if something does go wrong l can restore the backup bios (myboard had dual uefi bios from what l could tell from the manual).
I have the exact same problem.
I did have an Intel Z77 motherboard. It had two USB 3.0 controllers. Intel for the rear ports and Renesas for the front port header. My Seagate external drive would start up with the computer EVERY time when plugged in the Renesas ports but when plugged in the Intel controlled ports "error code 10 - this device cannot start". Had to unplug and plug it in every time on the Intel ports or leave it plugged into the front Renesas ports.
Now I just upgraded to a Gigabyte Z97X-Gaming 7 motherboard with a 4790K i7. All the USB 3.0 ports are controlled by the intel controller version 220.127.116.11 and guess what? My external drive will not start. I have to leave it plugged in the front and unplug-replug every time the computer boots.
I would really like an answer to this. Is it possible to use the Renesas controller instead of the Intel?
Intel USB ports do not work if you installed different manufacturer drivers. Why would you install Renesas if you have Intel USB ports?
Please bear in mind Intel provides only USB 3.0 drivers for Intel 7 and 8 series boards. For your Gigabyte Z97X chipset, you are required to contact and download drivers from Gigabyte.
Here is our download web site: Intel® Download Center
Allan thanks for your response but please read my post more carefully. I do have the Intel controller on my machine - it came right off the Gigabyte drivers cd and is the newest available. The USB 3.0 ports controlled by the Intel controller will NOT start my Seagate external drive. The previous motherboard was an Intel z77 and it had an Intel controller for the rear USB 3.0 Ports and a Renesas for the internal USB 3.0 header that runs the front ports on the case. My Seagate drive would NOT start when plugged into the Intel controlled ports but started EVERY time when plugged into the Renesas controlled ports.
I would install Renesas if I could because the Intel controller WILL NOT start my external drive. I have to unplug it and re-plug it in to get the drive to work. There's some kind of flaw in the Intel controller.
Do you understand now? My new motherboard has only 3.0 ports controlled by Intel so the drive will not start - it gives the error code 10 in device manager.
How do I get the Intel controller to start the drive like the Renesas controller did? This is the same problem the original poster has in his first post. It's the Intel controller that is the problem and nothing else.