F5F Stay Refreshed Hardware Desktop Issues with USB on the latest setup Weird behavior from USB devices on the new computer

Issues with USB on the latest setup Weird behavior from USB devices on the new computer

Issues with USB on the latest setup Weird behavior from USB devices on the new computer

A
ArchangelZ21
Member
209
12-16-2021, 03:43 AM
#1
I finished setting up my new PC a couple of weeks back, and it's been performing well overall. The only issue that bothers me is unusual (and uncommon) actions involving USB devices. It began with my VKB joystick, which connected to a 2.0 socket on the motherboard. Sometimes the stick would cease functioning completely, usually after the PC had been running for a while. When I switch from work to gaming or simming, the device stops working. Its power indicator is off, and it isn't recognized by Windows (joystick control panel, VKB software, games). It seems like it was either unplugged or put into sleep mode. Initially, I thought it was a hardware problem, but simply reinserting it resolved the problem instantly. I suspected the joystick or its port was the culprit since other devices didn't behave similarly. VKB recommended trying a different USB port on the motherboard, which I did (now using a 3.2 port), but the issue persisted. Later, some other peripherals would occasionally disconnect. My Razer mouse wasn't detected at startup, and my TM TWCS throttle stopped working—still listed as a device in the control panel, yet no inputs were shown in Windows settings. I also have a PS3 camera for head tracking that sometimes acts erratically, failing to decide whether to stay on or shut down with the PC off. Both the mouse and throttle resolved easily by reinsertion.

Hardware/config notes: Mainboard is an MSI Z690 Tomahawk DDR4 with an i5-12600K. It connects directly to the rear IO-panel via:
- HyperX Alloy Elite keyboard (2.0 USB port, works)
- Two 3.2 ports
- VKB joystick (3.2 port)
- PS3 camera (2.0 port)
- Monitor's USB extension cable
- A second 3.2 port left empty for BIOS flashing

Power supply: Seasonic FX Focus+ Gold 550W, sufficient for my setup per various calculators. I intentionally kept the second 2.0 port empty for BIOS updates.

Peripherals:
- Monitor uses four 3.0 ports; two for Razer Viper 8K and TM TWCS
- PS3 camera has two 2.0 ports, one for head tracking
- PSU is a 550W model, adequate for my needs

I've adjusted BIOS settings to default USB power management, but everything still functions as expected. The problem appears to be intermittent, possibly tied to Windows' power-saving features rather than the devices themselves. I'm open to suggestions on further troubleshooting steps. Thanks for your help! S.
A
ArchangelZ21
12-16-2021, 03:43 AM #1

I finished setting up my new PC a couple of weeks back, and it's been performing well overall. The only issue that bothers me is unusual (and uncommon) actions involving USB devices. It began with my VKB joystick, which connected to a 2.0 socket on the motherboard. Sometimes the stick would cease functioning completely, usually after the PC had been running for a while. When I switch from work to gaming or simming, the device stops working. Its power indicator is off, and it isn't recognized by Windows (joystick control panel, VKB software, games). It seems like it was either unplugged or put into sleep mode. Initially, I thought it was a hardware problem, but simply reinserting it resolved the problem instantly. I suspected the joystick or its port was the culprit since other devices didn't behave similarly. VKB recommended trying a different USB port on the motherboard, which I did (now using a 3.2 port), but the issue persisted. Later, some other peripherals would occasionally disconnect. My Razer mouse wasn't detected at startup, and my TM TWCS throttle stopped working—still listed as a device in the control panel, yet no inputs were shown in Windows settings. I also have a PS3 camera for head tracking that sometimes acts erratically, failing to decide whether to stay on or shut down with the PC off. Both the mouse and throttle resolved easily by reinsertion.

Hardware/config notes: Mainboard is an MSI Z690 Tomahawk DDR4 with an i5-12600K. It connects directly to the rear IO-panel via:
- HyperX Alloy Elite keyboard (2.0 USB port, works)
- Two 3.2 ports
- VKB joystick (3.2 port)
- PS3 camera (2.0 port)
- Monitor's USB extension cable
- A second 3.2 port left empty for BIOS flashing

Power supply: Seasonic FX Focus+ Gold 550W, sufficient for my setup per various calculators. I intentionally kept the second 2.0 port empty for BIOS updates.

Peripherals:
- Monitor uses four 3.0 ports; two for Razer Viper 8K and TM TWCS
- PS3 camera has two 2.0 ports, one for head tracking
- PSU is a 550W model, adequate for my needs

I've adjusted BIOS settings to default USB power management, but everything still functions as expected. The problem appears to be intermittent, possibly tied to Windows' power-saving features rather than the devices themselves. I'm open to suggestions on further troubleshooting steps. Thanks for your help! S.

L
Leiwar
Member
146
12-16-2021, 03:43 AM
#2
I suspect driver conflict. You’ve got a bajillion fairly unusual USB control peripherals all from different small companies, and mostly gaming stuff where getting something out the door asap is mission critical. If Perioheral driver conflict is confirmed a way around it that sometimes works is to get a USB card. Not for more ports, but to get another usb controller to hang stuff off of in the mix. It’s not reliable though. Edited April 2, 2022 by Bombastinator
L
Leiwar
12-16-2021, 03:43 AM #2

I suspect driver conflict. You’ve got a bajillion fairly unusual USB control peripherals all from different small companies, and mostly gaming stuff where getting something out the door asap is mission critical. If Perioheral driver conflict is confirmed a way around it that sometimes works is to get a USB card. Not for more ports, but to get another usb controller to hang stuff off of in the mix. It’s not reliable though. Edited April 2, 2022 by Bombastinator

S
ScorchSC
Junior Member
27
12-16-2021, 03:43 AM
#3
Now that you mentioned it... I had a "driver conflict" alert for the PS3Eye camera in my device manager earlier. I dismissed it then since everything was functioning properly and it was being used mainly for Opentrack headtracking, not as a webcam. Recently I rechecked its setup and...? No issues detected. The problem lies with the fact that this camera relies on a unique proprietary driver. The VKB stick works without any special software—just a few button presses to calibrate it, and while Windows recognizes it, it still treats it as a generic joystick. The track-clip requires no drivers because it’s simply a metal object with three IR LEDs; from Windows’ perspective, it’s more like a flashlight than a USB device. The only likely culprits seem to be the Thrustmaster throtte (which worked as a generic joystick before I installed its drivers) and the PS3 eye, which is somewhat improvised for headtracking purposes. But I’m not sure if those changes are permanent—there’s a possibility the camera has been altered to only detect IR light. *shrug* Since I was browsing the device manager: ... I realized I can tell Windows to keep my USB devices active, and in some cases it even allows deactivation for power savings. The main concern is that other than the Razer and a “Corsair composite virtual input device” (whose exact meaning I don’t know), nothing is clearly marked. Maybe I should unplug everything one by one and test which devices let Windows turn them off. S.
S
ScorchSC
12-16-2021, 03:43 AM #3

Now that you mentioned it... I had a "driver conflict" alert for the PS3Eye camera in my device manager earlier. I dismissed it then since everything was functioning properly and it was being used mainly for Opentrack headtracking, not as a webcam. Recently I rechecked its setup and...? No issues detected. The problem lies with the fact that this camera relies on a unique proprietary driver. The VKB stick works without any special software—just a few button presses to calibrate it, and while Windows recognizes it, it still treats it as a generic joystick. The track-clip requires no drivers because it’s simply a metal object with three IR LEDs; from Windows’ perspective, it’s more like a flashlight than a USB device. The only likely culprits seem to be the Thrustmaster throtte (which worked as a generic joystick before I installed its drivers) and the PS3 eye, which is somewhat improvised for headtracking purposes. But I’m not sure if those changes are permanent—there’s a possibility the camera has been altered to only detect IR light. *shrug* Since I was browsing the device manager: ... I realized I can tell Windows to keep my USB devices active, and in some cases it even allows deactivation for power savings. The main concern is that other than the Razer and a “Corsair composite virtual input device” (whose exact meaning I don’t know), nothing is clearly marked. Maybe I should unplug everything one by one and test which devices let Windows turn them off. S.