Chipset driver update causing USB-C power spikes£

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   One thing to add - it was suggested I use a powered USB hub to distribute the power better.  I did get one, but only plugged in other things into it (external drives, mic, kb/m, etc), thinking the suggestion was to ease the power from the back panel.  But now I realize maybe he meant ease the power of the USB-C (w/ a USB adapter).  

I actually do have a USB adapter that was in-use for my external SSD, so I tested the XB controller using that.  I plugged it in both the powered USB hub and directly to the back panel of the PC (one USB port didn't work though...same story for external SSD when I got it a couple weeks ago, causing this whole issue of updating chipset drivers).  Both times it worked fine, at least for a few mins, but I was forcing heaving vibration for most of the time.  

So...appears to possibly be isolated to the USB-C port in the back panel?  

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
Cheese47 Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 10 Jul 2023 Location: Sacramento, CA Status: Offline Points: 85	Post Options Post Reply Quote Cheese47 Report Post Thanks(0) Quote Reply Topic: Chipset driver update causing USB-C power spikes£ Posted: 07 Oct 2023 at 5:19pm
	One thing to add - it was suggested I use a powered USB hub to distribute the power better. I did get one, but only plugged in other things into it (external drives, mic, kb/m, etc), thinking the suggestion was to ease the power from the back panel. But now I realize maybe he meant ease the power of the USB-C (w/ a USB adapter). I actually do have a USB adapter that was in-use for my external SSD, so I tested the XB controller using that. I plugged it in both the powered USB hub and directly to the back panel of the PC (one USB port didn't work though...same story for external SSD when I got it a couple weeks ago, causing this whole issue of updating chipset drivers). Both times it worked fine, at least for a few mins, but I was forcing heaving vibration for most of the time. So...appears to possibly be isolated to the USB-C port in the back panel?

Cheese47 Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 10 Jul 2023 Location: Sacramento, CA Status: Offline Points: 85	Post Options Post Reply Quote Cheese47 Report Post Thanks(0) Quote Reply Posted: 07 Oct 2023 at 4:06pm
	So...long story short. Ever since I updated my chipset drivers on my mobo, it has caused my wired XB1/X\|S controller to momentarily die after vibrating. My mobo is AB350 Gaming K4 and I updated to AMD chipset driver version 2.11.26.106 for Windows 10 64-bit. I have tested 2 separate USB-C cords, 2 separate XB controllers, and with/without batteries. After vibrating, given the aforementioned variables, the controllers turned off for about 0.5-3 seconds (various ranges at different times), then turned back on. All while wired to my back panel via USB-C. A reply I got in another thread suggested the USB-C is sending too much power to the XB controller and causing power spikes. And I can confirm that it has killed the batteries I left in the controller. Because the controllers do not even turn on if wireless, even w/ new stock batteries that are just a week old in the new controller I bought just to test this. Anyway, so my questions are: 1. Is it possible that the chipset driver update is what is causing this? Sending too much power through the USB-C to the XB controller and causing some sort of power outage spike? 2. Could the power output be increased to all ports? USB 3.0, 2.0, etc? I want to get a USB 3.0 to USB-C adapter and test that, but I wonder if it'd be futile. 3. Can or should I rollback my chipset driver version to test it further? I only updated them because an external SSD I bought wasn't reading properly on my PC and still wasn't after the update. So the update was kind of pointless in that regard. I've used a wired XB1/X\|S controller in my PC for years and this only started happening since the chipset update. So...I'm assuming that has to be the cause. Thanks for any help.