USB 3.0 only works at USB 2.0 speeds

Slobodan-888

Reputable
Jul 17, 2014
417
0
4,860
This is the motherboard: http://www.gigabyte.com/products/product-page.aspx?pid=4716#ov

I have the latest BIOS installed (I have aslo tried other versions) and also the AMD chipset driver (includes chipset \ sata RAID \ VGA \ USB driver).

OS is Windows 7 64 bit. I wanted to tried whether it works on Linux but I was not able to run a live Ubuntu 14.04 (that supports UEFI).

Whenever I connect USB 3.0 capable device (external HDD) to and USB 3.0 port, I get message saying "This device can run faster if you connect it to an USB 3.0 port". And I only get USB 2.0 speeds.

What is the problem?
 
Solution
Gigabyte have replied and the solution was:

"uninstall USB controller under device manager and reboot the OS to let OS detect on the hardware again."

It now works. So it was probably some bug in their driver.

hans_pcguy

Distinguished
Nov 13, 2010
584
1
19,160
It is often, bios settings, or drivers, but it looks like you have covered those. There have been many many problems with usb controllers throughout the development of usb. One would think that they would have ironed them out by now. I would try contacting gigabyte and see what they say.
 

Slobodan-888

Reputable
Jul 17, 2014
417
0
4,860
Of course I have tried other devices and other ports.

I will contact Gigabyte.

I do not know what RMA stands for, but I really don't want to return the board. It will take enormous amount of my nerves to to that (due to bastards in the computer store and the need to get everything out and then back in the case again, and maybe even reinstalling the OS and all that bollocks). If the MB is faulty, I will not bother to replace it, it is just not worth it...

P.S. I bought these components like half a year ago. I thought that it was a software issue (Windows "working" as intended). And I have an extremely bad experience with returning faulty parts to this particular computer store.
 

Slobodan-888

Reputable
Jul 17, 2014
417
0
4,860
Gigabyte have replied and the solution was:

"uninstall USB controller under device manager and reboot the OS to let OS detect on the hardware again."

It now works. So it was probably some bug in their driver.
 
Solution