"I woke up my system"
Are you allowing your USB Ports to Sleep?
Turn Off Sleep Mode and just turn off your computer overnight.
Computers of Today are not like computers of the 80s and 90s.

joshf87
Not allowing USB to suspend didn't make a difference, leaving the power off for a while will allow USB hard drives to work again on the USB 3.1 ports (they appear to be receiving power but are nowhere to be found)?

More Issues with Windows 10 Anniversary Sleep Mode, this is why I turned it off.

Or Windows 7 or any Windows I turn off Sleep no need for it in the home. Still a Sleep Mode Issue.
This is NOT in Reference to LapTops only to DeskTop Computers.
 You do also need to turn it off in your Bios that is if you want to turn off Sleep Mode on your Computer.

Sajin

joshf87
The USB hard drives work fine on another computer. I've tried reinstalling the USB drivers or trying another version, different cables, restore UEFI to defaults and even reinstalled the OS without success.

Sounds like the ports are dead.

It seems cutting the power fixes it and not simply rebooting. Sleep/suspend apparently has issues with the 3.1 ports.
 

Is there some way to reset the USB ports without having to power down and disconnect the power?

I've always been using ASMedia's driver, the initial encounter with this problem occurred in Windows 7 (so I'd have to use the ASMedia driver), I have been on Windows 10 since then, and have been using ASMedia's drivers but right now I decided to do a clean install and stick with Microsoft's driver (Creator's Update (1703) as of writing). Driver downloads from WU are disabled, so it doesn't install anything without me knowing. I don't believe it will make a difference, if I accidentally leave an external desktop HDD powered on or portable drive connected (or connect/power them on) when the system is turned off then I have to go through disconnecting the power cable to get the 3.1 ports to work again for external HDDs.
 
After the initial BSOD, I reinstalled Windows 7 and 10, tried multitude of driver versions ad nauseam, and the only thing that fixed it was completely cutting the power for a few minutes.
 
My board has 1.04 and that is the one I am still using. I usually jump on BIOS updates even if they aren't necessary but the feedback from the 2.00 releases deterred me, if it was 100% certain to address this issue I may try it but I believe ASMedia controllers can have their firmware updated separately as well.
 
I don't believe RMAing board will solve the issue, the ASMedia chipset is probably just crappy, or my theory is that the ASMedia controller has some sort of charging support for when the PC is turned off but the controller just doesn't know how to come out of this state unless the main power is completely disconnected. There is no option to disable charging support in UEFI setup, unlike other boards. I have actually used what I learned in this thread to help someone not 2 months later with the same issue on an ASMedia controller but a different brand, solution was the same.
 
I was hoping for some cheat to not have to power off the system when the 3.1 ports randomly decide not to work when I want them to.

mike406
I wouldn't recommend using a USB hard drive on a 3.1 port anyway as there is no native 3.1 support in Windows. Windows 10 has native USB 3.0 support so I'd stick with that simply for stability and reliability purposes.

A USB port is a USB port, Windows 10 has native support for 3.1/ASMedia, at least in 1703.  The two 3.1 ports are much less often used any way and am only using the four USB 3.0 ports for permanent devices, only connecting a My Passport drive once in a while to synchronize data for other computers. A My Passport drive won't come close to saturating a 3.1 port but I should be able to connect it and it should work without randomly having to go through the power disconnect ritual. I have every sleep option in UEFI and Windows disabled but the 3.1 ports have a mind of their own if they want to let me use external HDDs.
 
 
I could buy a USB 3.0 hub and connect it to one of the 3.0 blue ports so I can avoid ever using the red 3.1 ports, but why should I have to do that? USB 3.1 has a throughput of 10 Gbps and is supposed to be backward-compatible, but the chipset randomly acts ups and will only allow mice/KB and thumb drives to work .
 
 
CPU: Intel Core i7-6700K
Motherboard: EVGA Z170 Classified K (142-SS-E178-KR)
PSU: EVGA SuperNOVA 750 G2 Power Supply (220-G2-0750-XR)
Graphics: EVGA GeForce GTX 1060 GAMING ACX 3.0 (06G-P4-6262-KR)
Memory: G.SKILL TridentZ Series 16GB (F4-3200C14D-16GTZSK)
SSD: Samsung 850 EVO (250GB)
HDD: 2x Western Digital WD1003FZEX
OS: Windows 10 Professional 64-bit (1703)

mike406

joshf87

mike406
I wouldn't recommend using a USB hard drive on a 3.1 port anyway as there is no native 3.1 support in Windows. Windows 10 has native USB 3.0 support so I'd stick with that simply for stability and reliability purposes.

A USB port is a USB port

One other thing I can recommend is download WD Drive Utilities and turn off the sleep timer feature of the drive. I have had issues with my WD external drive waking itself up when attached to my NAS often causing my nightly backups to fail.
https://support.wdc.com/downloads.aspx?lang=en
 

I tried every sleep option imaginable except that, the default Windows 10 CU 1703 driver didn't make a difference. When the ASMedia 3.1 controller decides to allow external HDDs to work there's no reliability or data integrity issues while the drive is in operation, it's just the next power on of the drive may or may not work (portable or with power supplies). I guess I'll just live with it for now, I will just turn my UPS off when I leave for work every day (any means of cutting the mains power will work, flipping the on/off switch on a PSU, turning off battery backup or power strip) so it can be assured the ports are ready to use when I want it.