Additionally, the Razer Core's USB ports just flat out don't work. There's a power short of some sort in the internal USB hub, so that if you plug in a device that draws any more than the lowest amount of power, it cycles through a connecting/disconnecting state, looping forever.
This probably isn't a short; it's more likely a software problem. I can see how they could get into that mess. Remember, with USB, you're only allowed to draw 100mA until you've negotiated with your power source for more, and the power source can say no. USB interface chips enforce this[1], and cut power and send a fault signal if a device pulls too much power.
The Razer Core is basically a docking station. USB-C power is complicated to begin with, and they've set up one of the most complex situations. The way they're using this, the dock is providing power to the laptop, but the laptop is the data master for the USB ports on the dock, which is also providing power to the peripherals. This is something USB-C allows; a device can be a power slave and a USB master at the same time.
This is even more complex. The dock is a source to both sides for power management purposes, but a pass-through for data purposes. This is unusual. I've skimmed the USB-C spec but don't recall that being mentioned. They probably have to MITM the power handshake to get this to work. The laptop is running Windows 10, so they don't control the USB drivers and their power handshake. It's entirely possible that Windows doesn't support that configuration fully.
* Plugable report similar problems with their dock.[1] They also power both sides while trying to pass through data.
* Similar problems reported for Anker.[2]
* And CalDigit.[3]
This may be a generic problem with USB-C middle boxes which power in both directions. Some configurations don't work, and this is tough to troubleshoot. The standards compliance test procedure for USB-C hubs [4] doesn't seem to contain this case. The test designers were still thinking "tree with computer at root" in 2015.
This probably isn't a short; it's more likely a software problem. I can see how they could get into that mess. Remember, with USB, you're only allowed to draw 100mA until you've negotiated with your power source for more, and the power source can say no. USB interface chips enforce this[1], and cut power and send a fault signal if a device pulls too much power.
The Razer Core is basically a docking station. USB-C power is complicated to begin with, and they've set up one of the most complex situations. The way they're using this, the dock is providing power to the laptop, but the laptop is the data master for the USB ports on the dock, which is also providing power to the peripherals. This is something USB-C allows; a device can be a power slave and a USB master at the same time.
This is even more complex. The dock is a source to both sides for power management purposes, but a pass-through for data purposes. This is unusual. I've skimmed the USB-C spec but don't recall that being mentioned. They probably have to MITM the power handshake to get this to work. The laptop is running Windows 10, so they don't control the USB drivers and their power handshake. It's entirely possible that Windows doesn't support that configuration fully.
[1] https://www.onsemi.com/pub/Collateral/NCP380-D.PDF