That was a wise debugging methodology for PC hardware to OS issues. Go back to the very basic device config (mouse and kb) and add one at a time (to MB powered USB ports, USB2 before usb3 for older devices). Once successful, add one more and repeat test cycle. Wash and rinse until all devices work or identify which is causing the issue. Then isolate the one that fails and try it by itself.
I have found that motherboards have different abilities to power and enumerate a certain number of USB devices, some more and better than others. Which is why when I build my PC, I pick the very best MB which was made for gaming and has 18 or more USB Ports (USB 2 and 3).
Being I use all of these ports (Cougar with TUSBA set, Warthog set, Saitek Throttle Quad, 3 USB LCDs, USB ICP, USB wireless mouse and kb, numpad, TIR, WEBCAM, USB rudders, USB powered hub,… (Think that’s what 16 or so there); its critical that I have a strong USB platform. I use an AUSUS Z87 something MB and Win7 with all the auto powering off. My controllers go to the primary MB backside USB ports, via a powered data switch so I can quickly switch from COUGAR to WARTHOG set as needed (BMS or DCS).
When debugging USB to controller (or any devices),Windows Devices and Printers tool provides USB connection info. To a certain degree, this tool does provide a great way to identify USB details for the devices connected to a PC and to specifically identify what device was connected to what port.