Rift USB device "flakey" (popping in/out device manager, doesn't initialize properl) until I re-plug

[flexy123]

Config: Win 10 x64 Creator's Update - 16GB - Asus Z87 Pro - GTX970 - Oculus 1.14 - USB 3.0 Intel, Asmedia USB 3.0, System passes Oculus Compat Test. Rift USB and Sensor 1 connected to Intel USB3.0, Sensor 2 connected to Asmedia. No problems with sensors.

This is an annoying issue which appeared here recently, approx. since 1.13
In the meantime, I already de-installed Oculus multiple times, the last time yesterday in the hope that this flakyness disappears.

Issue:
After rebooting, the USB devices (the Rift itself, not any of the sensors) doesn't "hold" the drivers. Windows is constantly showing how it detects devices and seems trying to install drivers. But it's hanging in a loop. (In the Win task tray at the bottom, I see the symbol flashing as it if detects USB devices, on/off and this goes on forever).

In device manager, I see several "Human Interface Devices" related to Oculus with yellow exclamation marks. Popping in and out, like a driver installs but then fails a second after and the thing starts over. One second there is like 3-4 devices yellow, next second they're fine, then yellow again, flashing in and out.

I can only stop this by unplugging and then re-plugging the Rift USB connection. Then it seems the system "gets" the devices and everything is ok and the Rift and everything else also works fine.

In BIOS, I disabled legacy USB, and I have Intel xHCI handoff enabled and eHCI handoff disabled. I have these settings like this for a long time.

Any idea?

Edit: Observing this behaviour, it seems also having to do with that the internal Rift USB hub at times is seen as USB3.0 "SuperSpeedHub" by Windows (ie: device manager), but not always. Sometimes it's seen as 2.1.  It may be the case that the connected Rift is already categorized as EITHER a USB3.0/SuperSpeed or USB2.1 hub in the BIOS, before Windows even starts. The flakyness to me seems related to as how the connected USB device is seen. Possible (needs more testing) if the device is already seen as USB3.0 way before Windows even starts, it's then where the Rift devices in device manager "jump" and can't properly initialize but not when the system sees and initializes the port as USB 2.1