USB3.0 Problem

[stevenrw]

Don't know if any of you good folks can help with this...
I have an Icy Box ID-3620 dual SATA caddy loaded with two WD Green drives that I use for backups. It is connected to my W7 Pro (64bit) desktop machine via USB3.0 ports on the back (ie straight on to the motherboard, (Gigabyte Z77-D3H) not via a pci card or hub)
All has been fine until just recently.
What happens now is that the first copy operation works fine, but if I then try to copy something else to the same drive the system crashes. Windows hangs on "discovering elements" and the only way to stop it is via Task Manager, then logging off (again via Task Manager). It then hangs on the "Logging Off" screen until I force the caddy to power down.
I've tried connecting to another laptop (W8.1) with USB3.0 connections and it works fine.
I've also tried plugging the USB3 cable into a USB2.0 port on my desktop and it works fine.
Looking at the "Block Diagram" in the mobo manual, it appears that 2 of the USB3.0 ports feed via the Eltron EJ168 controller whilst the other 4 connect via the Z77 chip. I've tried swapping connections to no avail.
I've also tried uninstalling and reinstalling the caddy via device manager in case there was a driver issue.
So it sounds like a USB3.0 controller issue rather than a disk or caddy problem but why it would work once and not again after that is a mystery. Obviously after restart the process repeats.
So I'm having to use USB2.0 speed on a USB3.0 enabled caddy which is annoying to say the least.
Ideas anybody?

[Steve]

My guess would be windows 8.1 playing up , but how to test without causing chaos. Possibly a Linux live cd that supports usb 3 if it exists.

[Glenn]

Possibly a motherboard problem http://www.tomshardware.co.uk/forum/317292-30-gigabyte-external-detection-issue

[stevenrw]

Thanks Steve & Glenn, it really looks like it is a fairly common problem. I haven't looked at updating the USB controller drivers because, as I said above, there looks to be two controllers and the same problem persists on all sets of USB3.0 connections on the back of the case. I'm surprised (and a bit disappointed) that the USB3.0 is still giving problems - its not new anymore.
I might look at the cheap option of putting in a PCIe USB3.0 card. I know you are throttled by the max speed via PCIe bus, but if it works ok it will still be faster than leaving it on USB2.0 as it is at present. I don't think its worth spending out on a new dual caddy with eSATA because I've already got a single eSATA PCIe card and its only got one port, which I use from time to time - and of course you are still limited for speed via PCIe.
I'll keep you posted. I just need to take a look inside the case tomorrow to make sure I have a spare PCIex1 slot and a spare power conn.

[stevenrw]

Well, its official (or close to official) USB3 doesn't work a lot of the time. I've Googled it and there appears to be widespread issues with it, both on W7 and W8 (.1). Some people are blaming Via for the Z77 chip, some are blaming Intel for the drivers, some are blaming Microsoft, but the peripherals manufacturers are still churing out USB3 connected kit and trotting out the max transfer speeds, which were only ever theoretical, along the lines of BB download speeds of "up to..."
I bought a PCIe USB3.0 card http://www.amazon.co.uk/gp/product/B00B6ZCNGM?psc=1&redirect=true&ref_=oh_aui_detailpage_o00_s00 and its giving me slower speeds than USB2.0.
So, as so predictably happens, its a mess.
My advice would be to tread warily if you are buying a new bit of kit and are swayed by USB3.0 speeds advertised. If possible go with eSATA, it may be (theoretically) slower, but in practice it'll be noticably faster.
And it'll work.
Probably.

[nowster]

I've also come across something odd at work. It might be USB3 related or it may just be cruddy hardware or software on the system concerned.

USB3 SSD connected directly to USB2 port. Fine. Reliable.

USB2 Memory Stick connected directly to USB2 port. Fine. Reliable.

USB3 hub connected directly to USB2 port. Fine... as long as nothing else is connected to the hub.

Attach any device to that hub and the system concerned would consistently crash within a minute or two... NMI watchdog timeout.

[Glenn]

Sounds like the hub is not getting enough power from the PC, if you have one, try a powered hub.

[nowster]

Sounds like the hub is not getting enough power from the PC, if you have one, try a powered hub.

It's a powered hub!