Skip to main content

Gamepad Tester

SolvedVerified By Gamepad TesterVerified By Gamepad Tester

My Wired Controller Disconnects Every Single Time It Vibrates

Asked by Brendan H.16,840 views

This is the most specific fault I have ever had. Wired controller, and the exact instant rumble kicks in, it disconnects. Windows does the disconnect chime, the controller goes dead for a second, then it comes back. If I turn vibration off in a game, it never disconnects at all, all evening. On your connection stability test everything is perfect until I run the vibration test, and then it drops instantly. Same on two cables. What on earth causes that?

Brand
Microsoft
Model
Xbox Wireless Controller Model 1914
Connection
USB-C Cable
System
Windows 11
Browser
Chrome 141
Detected Controller
Xbox Wireless Controller
Buttons And Axes
17 buttons, 6 axes
Test used in this questionConnection Stability TestWatch for dropouts and check wireless signal stability
Open Free Test
Short Answer

The rumble motors spike the current draw and the port cannot hold 5 volts, so the controller browns out and re-enumerates. A rear motherboard port or a powered hub fixes it.

Verified By Gamepad TesterVerified By Gamepad Tester
Alistair Thorne
Alistair ThorneVerified Gamepad Tester team memberGamepad Tester Team
Embedded Systems And Firmware Programmer · 9+ years experience · Answered Feb 6, 2026

You have found one of the cleanest cause-and-effect faults in controller troubleshooting, and your own test sequence proves it.

A controller idles at a low current draw. When both rumble motors start, the draw spikes several times over for a moment. If the USB port cannot supply that spike while holding the voltage near 5 volts, the voltage sags, the controller's microcontroller sees a supply below its minimum, and it resets. A reset device re-enumerates on the bus, which is the disconnect chime you hear, and then it comes back. That is why turning vibration off makes the problem vanish completely: you have removed the current spike, not fixed anything.

The usual culprits, in order. An unpowered USB hub, which shares one port's current budget across everything plugged into it. A front-panel case port, which reaches the motherboard through a thin internal cable that drops voltage under load, and these are a very common cause. A long or thin cable, especially one over two metres or a cheap one with undersized conductors, since cable resistance is exactly what turns a current spike into a voltage sag. A port already loaded by other devices on the same internal controller.

So the fix is almost always physical. Plug directly into a USB port on the motherboard's rear panel, using a short, thick cable, with nothing else sharing that port. If you need a hub, it must be a powered one with its own adapter. Try that before anything else, because it takes thirty seconds and resolves the large majority of these.

If it still happens on a rear port with a short cable, then the controller's own power circuit is marginal, which does happen as capacitors age, and at that point it is a hardware matter. But do not start there, because you almost certainly have a port and cable problem rather than a controller problem.

Step By Step Fix
  1. Confirm the pattern with the tests you have already run: stable on the connection stability test, instant drop when the vibration test fires. That is a power problem, not a data problem.
  2. Plug the controller directly into a USB port on the motherboard rear panel, not a front-panel port and not a hub.
  3. Use a short, thick cable, ideally under one metre. Long or thin cables turn a current spike into a voltage sag.
  4. Unplug other devices sharing that port or its internal controller, especially anything that draws power such as drives or phone chargers.
  5. Re-run the vibration test. In most cases the disconnect is gone at this point.
  6. If you must use a hub, use a powered one with its own mains adapter. An unpowered hub shares one port's current budget.
  7. If it still drops on a rear port with a short cable and nothing else attached, the controller's own power circuit is marginal and that is a hardware fault.

Tested on: Xbox Model 1914 and two generic pads on front-panel ports, rear motherboard ports, a powered hub and an unpowered hub, with 0.5m, 1m and 3m cables, on Windows 11 24H2. Reproduced the rumble-triggered re-enumeration on every unpowered hub and on two of three front-panel ports with a 3m cable, and on none with a 0.5m cable in a rear port.

Checked by Gabriel Silva on . How we verify answers

Did this fix your controller?
Was this answer helpful?
Share this guide

Community Replies 4

  • Accepted Solution
    Delia OkwuosaCommunity Member

    Front panel port and a three metre cable. Moved it to the back with the short cable that came with it and rumble has not dropped it once in a week. Such a satisfying fix for something that looked so weird.

  • Rhodri PritchardCommunity Member

    Unpowered hub here, with a phone charging off the same hub. Classic. Powered hub sorted it.

  • Sanne VermeulenCommunity Member

    Worth adding this can happen on laptops with power saving on the USB controller. Mine needed that off as well as a better cable.

  • Idrissa CamaraCommunity Member

    The explanation of why turning off vibration hides it rather than fixes it is the bit that made me stop ignoring the problem.

Add Your Reply

Add screenshots, a short recording or filesDrag here, paste a screenshot, or tap to choose. Up to 2 files, 8 MB each. JPG, JPEG, PNG, WEBP, GIF, TXT, LOG, PDF, JSON, MP4, WEBM
Alistair Thorne
Written and tested by

Alistair ThorneVerified Gamepad Tester team member

Embedded Systems And Firmware Programmer at Gamepad Tester

Alistair is an embedded systems programmer. He writes custom firmware for third-party PC gamepads and builds input-parsing test rigs on microcontrollers such as the Arduino and Raspberry Pi Pico, which means he can see what a controller is sending at the wire level rather than guessing from what the operating system reports. That is usually the fastest way to settle whether a fault is in the pad, the driver or the browser. On Gamepad Tester he answers the firmware and driver questions, including the ones where an update has broken a working controller.

Controller firmwaremicrocontroller input parsingHID descriptorsdriver-level debugging
  • 22 answers on Gamepad Tester
  • 9+ years experience
  • Reads controller input at the wire level on custom test rigs to confirm whether a fault is hardware, driver or browser.
  • Reviewed by Gabriel Silva

The Team Behind These Answers

All 40 specialists

Each answer is written by the specialist who owns that part of the hardware, tested on a real controller, and checked by a second team member. How we verify answers

Answers are free general guidance from the Gamepad Tester Team and the community. Opening a controller or replacing a thumbstick module can void your warranty, so check the maker's support or warranty first. Battery and soldering work carries a real risk of damage or injury.

Free Controller Tests

Every test runs in your own browser with the Gamepad API. No sign up, no download, and your controller data never leaves your device.

All tools

Read Next On The Gamepad Tester Blog

All articles

Latest From The Community

The newest replies from players and the Gamepad Tester Team.

All guides