USB 3.0 port error

Alex Appleton

Reputable
Oct 7, 2015
19
0
4,510
Hey all, i recently built a new computer, at the front of the case i've 2 USB 2.0 ports 'all working fine' and 2 USB 3.0 ports 'one works one doesn't'

Whats happening is when i try connect a device to the port that isn't working i'm getting the following:

'the last USB device you connected to this computer malfunctioned and windows does not recognise it'

Below are a few screenshots showing the errors.

http://imgur.com/Cdt36Lc
http://imgur.com/Df9WKsI
http://imgur.com/S7HxgbR

Here's a few things i've tried so far:

i've updated my bios
I've tried disabling/enabling various USB options in the bios
i've tried uninstalling the effected USB in device manager and rebooting
I've unplugged/replugged my USB 3.0 cable into my motherboards port

Nothing i do can get it to work, it's not the end of the world but it's annoying that it's not working.

Anyone have any ideas?

OS: Windows 10 'up to date'
Motherboard: Asus VII hero
Case: Corsair 780T

Thanks.

Alex.
 
Solution


No, they're backwards compatible. I know Windows says it's up to date but click "check for updates" anyway and force it to check.

Also - you should get the chipset/mobo drivers directly from ASUS. You might want to re-seat the wire inside the case that goes from the front panel to the USB header on the motherboard - confirming that it's on the correct header by checking the motherboard manual


i'm not using USB drives, i've mainly been connecting devices such as my phone or ipod and all of them have the same problem, the devices i've been trying don't use USB 3.0 though, could it be that one of the two USB 3.0 ports only accepts USB 3.0 devices?
 


No, they're backwards compatible. I know Windows says it's up to date but click "check for updates" anyway and force it to check.

Also - you should get the chipset/mobo drivers directly from ASUS. You might want to re-seat the wire inside the case that goes from the front panel to the USB header on the motherboard - confirming that it's on the correct header by checking the motherboard manual
 
Solution