Every option listed above is an excellent option-there are many causes for drives behaving like this. For most, cases,
un-checking the box in Properties/Power Management for EVERY USB
Root Hub in your Device Manager can fix the issue (again, for most but not all).
I'm going to mention some info I didn't see (or missed) through these answers,any one of which could be the solution to someone's problem. I too had the same problem of my 5TB Seagate disconnecting, and I run a daily image of my system @ 4 a.m. everyday which started failing every morning when I woke up. Here's a few other things I've learned along my troubleshooting....
- Make sure you have a big enough power supply (PC obviously, laptops you have no control). Multiple hard drives with a high end Processor and lots of RAM plus your added video cards/PCIe devices/Raid Controllers can eat quite a bit of the power available. This means less power running down your USB Bus.Devices requiring power like a hard drive may dip just below their minimum required threshold, and then quickly return to an acceptable power amount - the end user just sees their drive disappear then reappear. From what I've read, there is honestly no software that can accurately measure power information about your system correctly. Many are advertised to do so, but reading through threads you start to realize the marketing is a bunch of crap. You need a physical tester to truly know the power levels. Don't cheap out with the 400W power supply and expect to run a lot of things. My 600W is right at the brink now, and I've moved most of my studio equipment to a powerful hub with an a/c adapter. I run 8 SSD's and 2 7200rpm Sata drives and a video card. If I plug two USB devices into my boards ports, things will stop working. It actually caused 1 of my raid arrays shown as failed on boot up, and those drives weren't accessible. When I unplugged the two USB devices, everything started working fine again. So I know my 600W cant handle anymore lol. So Powered Hubs are how I had to go.
dezign August 17, 2015 7:01:39 PM
Part of the problem could be this Intel flaw ...
http://www.techpowerup.com/181269/lynx-point-usb-3-0-co...
The problem ''went away'' on my Asus G750 when I disabled XHCI in the bios (... also referred to as the USB 3.0 Host Controller specification). https://en.wikipedia.org/wiki/Extensible_Host_Controller... as the Asus G750 has the ''Lynx Point controller'' mentioned in the article. XHCI also handles power to USB device
This is a rare one, and you can see it tanked his xfer rate, but there can be other power settings in your BIOS depending on manufacturer that might be the cause. Check with your motherboards specs, and see if you have the ability to change any power management options. ***DISCLAIMER-Don't mess with your BIOS if you're unsure what you're doing. If you see a setting you suspect might have an impact, google it and see what that setting does. Not every BIOS is the same obviously, make sure you have the most up to date version of BIOS and Chipset drivers. The Intel Controller mentioned quite a few times here might be the issue.
Disable things you never use and any associated controllers that go with it. If you use WiFi, and always WiFi, disable your LAN network card. In my case, I have an external soundcard so I've disabled all the Nvidia Hi Def Audio controllers (from having HDMI) and my onboard sound because I'm never going to use it. Some folks may have an older computer with a 56k modem-disable it if you have hi speed internet and use WiFi or an Ethernet (NIC) card. I always disable them in device manager AND the BIOS. Just because Windows has it disabled in Device Manager doesn't mean it's fully disabled. It's only disabled in Windows. (For example if you ran a dual boot system, say Windows and Linux or whatever) disabling it in Windows will have no effect on the Linux OS.) So to be safe, I disable what I'm positive I'm not going to use within my BIOS. I have a PCIe video card I use and don't use the on board VGA/DVI/HDMI ports-disabled in BIOS so they're powered off per the hardware-not the OS.
CABLES MATTER, but not just length! Just as someone mentioned earlier in this thread (which I cant seem to quote here unfortunately :/ but they said the "Cable was tooo loooong" I laughed but they are correct! The length DOES matter, especially with devices sending lots of data and that require power.
It's not just length, but the gauge also - On all of my USB "B" cables (I believe its the "B" one-with the square end we use for printers) the gauges are listed on the wire, either 28awg or 24awg/2c. I have 9 large USB devices (3 midi keyboards, 2 controllers, 1 audio interface plus my drive, Razer gaming mouse, back-lit Logitech Keyboard, etc) for my recording studio. Since they all require power, and some quite a bit of power, its obviously causing a bigger load on my PC. My Audio Interface kept failing, and after hours of research I found I had simply used the wrong cable to connect it. My Native Instruments Audio Interface's FAQ's gives an explanation of the different gauges and I learned then that the 24AWG/2C carries more power and was needed. I had one of my 28awg cables hooked to it. Quick swap to a 24AWG/2C, problem solved. Strangely, on all my USB 3.0 cables, there's no listing printed - but I can see obvious differences in the gauge size of my many different cables. I haven't gotten to the bottom of that yet, but my personal rule of thumb now is I always use the shortest/fattest one I can find.
USB 3.0 Hubs-don't go super cheap when purchasing one, and they come in a variety of ports #'s and wattages. If you HAVE to use a hub like I do, get one that's going to have a lot of power to supply your devices. If you fail to use the ac adapter, the hub still works, but you're back to drawing power from the PC to power your stuff, which defeats the point of buying the hub.
Finally, a rare possibility these days, but there may be an IRQ conflict between two of your devices. Highly doubtful and it's been probably 10 years since I've had to work around an IRQ conflict, but it is Windows, so who knows.
This was a nice thread without any really bad advice to try. In the end, my issue was the Power Management in Device Manager turning off my root hubs. I do have issues with my two front USB ports on my case, so I'm going to look into the grounding issue someone mentioned.
Thanks to everybody for good advice for others to try.