Xbox Series controller causing BSoD

[Victor Von Queso]

Alright, so I’ll start from the very beginning with this. I have Mass Effect: Legendary Edition on origin, but when I use my Xbox series controller all the inputs are scrambled, as in clicking left stick=start, X=A, and the camera just spins. So what I did was added all of the game executables, including the launcher, into my steam library. I then went into my steam settings to configure my controller, I selected the options for Xbox, and it installed a driver. Only thing is, now anytime my Xbox controller is connected it immediately causes a blue screen. No inputs, no game, nothing loaded. Even on a blank desktop. I’ve never had this problem, I’ve used that controller to play multiple different games, because I use a laptop and like to connect it to a tv sometimes.

I need to know what happened, what’s causing it, and how to fix it. I don’t even really care about getting my controller to work for the game right now, I just want my controller to not immediately kill my pc when I connect it.

[ReBoot]

Upload your crash dump for someone, i.e. me, to analyze with WinDbg. That'll tell which module crashes.
In the meantime, disable Steam's input mapper for XInput. It's generally not needed and really REALLY should be off by default.

[MancSoulja]

It’s because your controller is connected via bluetooth, older games and the Series controller just don’t seem to work with bluetooth, newer games work fine, but for older games you’ll either need to use a cable or the Xbox wireless adaptor.

Never has this caused a BSOD for me though, that seems like a separate issue. All I can suggest was that you completely remove the controller driver via device manager and start again, you could also try uninstalling and reinstalling your BT drivers.

[Victor Von Queso]

Originally posted by ReBoot:

Upload your crash dump for someone, i.e. me, to analyze with WinDbg. That'll tell which module crashes.
In the meantime, disable Steam's input mapper for XInput. It's generally not needed and really REALLY should be off by default.

How exactly do I find my crash dump?

[Victor Von Queso]

Originally posted by MancSoulja:

It’s because your controller is connected via bluetooth, older games and the Series controller just don’t seem to work with bluetooth, newer games work fine, but for older games you’ll either need to use a cable or the Xbox wireless adaptor.

Never has this caused a BSOD for me though, that seems like a separate issue.

This is the new version of the game that came out last year, that supports controllers by default. It worked just fine on a different computer before I got this laptop.

[ReBoot]

Originally posted by MancSoulja:

It’s because your controller is connected via bluetooth, older games and the Series controller just don’t seem to work with bluetooth, newer games work fine, but for older games you’ll either need to use a cable or the Xbox wireless adaptor.

♥♥♥♥♥♥♥♥. Games don't care how the gamepad's attached, only that it is and what it is.

Originally posted by The Noid:

Originally posted by ReBoot:

Upload your crash dump for someone, i.e. me, to analyze with WinDbg. That'll tell which module crashes.
In the meantime, disable Steam's input mapper for XInput. It's generally not needed and really REALLY should be off by default.

How exactly do I find my crash dump?

You look up online where they're stored by default. Or you open Windows' crash dump settings & look there.

[Victor Von Queso]

Originally posted by ReBoot:

Upload your crash dump for someone, i.e. me, to analyze with WinDbg. That'll tell which module crashes.
In the meantime, disable Steam's input mapper for XInput. It's generally not needed and really REALLY should be off by default.

https://1drv.ms/u/s!Auugbgn6LwOkhg2k1cnyiEnTGszN?e=ZsM9oW This is the link to my recent dumps. I think... lol

[ReBoot]

The culprit is the system XInput driver.

Or so the debug log says anyway. Mass Effect supports XInput gamepads just fine by default. The symptoms you observed point to something else entirely messing with the XInput driver. Usually, it doesn't crash and usually, it doesn't exhibit the behaviour you've described in Mass Effect.

I don't know whether you've ever touched input mappers, input injectors or whatever so let's go with what you totes have installed & even available: Steam's input mapper. Disable the one for XInput, restart Steam. See if the problem still appears.

That said, did you (or someone else using this computer with administrative privileges) install anything input-related, like, EVER?

[MancSoulja]

Originally posted by ReBoot:

♥♥♥♥♥♥♥♥. Games don't care how the gamepad's attached, only that it is and what it is.

Spot the difference;

Xbox Series controller connect via Wireless adaptor: https://i.postimg.cc/852tLYqB/JP1.jpg

Xbox Series controller connected via USB C: https://i.postimg.cc/Pxy5DGL0/JP2.png

Xbox Series controller connected via bluetooth: https://i.postimg.cc/hvVMsrnF/JP3.jpg

You're right in your presumption but that is assuming that the controller is detected as the same device in every instance, moreover it is a know bug which Microsoft has acknowledged and is addressing, a quick google search would have provided you with plenty of information on the issue,

[Arthur, King of the Britons]

Originally posted by MancSoulja:

Originally posted by ReBoot:

♥♥♥♥♥♥♥♥. Games don't care how the gamepad's attached, only that it is and what it is.

Spot the difference;

Xbox Series controller connect via Wireless adaptor: https://i.postimg.cc/852tLYqB/JP1.jpg

Xbox Series controller connected via USB C: https://i.postimg.cc/Pxy5DGL0/JP2.png

Xbox Series controller connected via bluetooth: https://i.postimg.cc/hvVMsrnF/JP3.jpg

You're right in your presumption but that is assuming that the controller is detected as the same device in every instance, moreover it is a know bug which Microsoft has acknowledged and is addressing, a quick google search would have provided you with plenty of information on the issue,

Your computer does NOT care HOW a device is connected. Even if it names them something else, this is just asinine. I DID a quick google search, a bunch of hits from 4 and 5 years ago and NONE of the Microsoft help forum posts mentioned Bluetooth being the cause when resolved.

OP - One thing I did notice, the controller itself may need an update. I HIGHLY doubt this will fix anything but I know several Microsoft help forum users reported this as a fix for them, but again best results I get are from years ago. Best of luck.

[MancSoulja]

Originally posted by The Noid:

Originally posted by MancSoulja:

It’s because your controller is connected via bluetooth, older games and the Series controller just don’t seem to work with bluetooth, newer games work fine, but for older games you’ll either need to use a cable or the Xbox wireless adaptor.

Never has this caused a BSOD for me though, that seems like a separate issue.

This is the new version of the game that came out last year, that supports controllers by default. It worked just fine on a different computer before I got this laptop.

I can confirm the Mass Effect Legendary Edition is completely borked when using a Series controller connected via BT, when I load into the game connected via BT this is what I'm greeted with:

https://www.youtube.com/watch?v=cfNz2KMAbFg

I can't even control the menus, I had to quit using Task Manager, after doing a little testing, if you completely disconnect your pad, then load into your save, you can connect the pad and it seem to work properly.

[MancSoulja]

Originally posted by gagnrad:

Originally posted by MancSoulja:

Spot the difference;

Xbox Series controller connect via Wireless adaptor: https://i.postimg.cc/852tLYqB/JP1.jpg

Xbox Series controller connected via USB C: https://i.postimg.cc/Pxy5DGL0/JP2.png

Xbox Series controller connected via bluetooth: https://i.postimg.cc/hvVMsrnF/JP3.jpg

You're right in your presumption but that is assuming that the controller is detected as the same device in every instance, moreover it is a know bug which Microsoft has acknowledged and is addressing, a quick google search would have provided you with plenty of information on the issue,

Your computer does NOT care HOW a device is connected. Even if it names them something else, this is just asinine. I DID a quick google search, a bunch of hits from 4 and 5 years ago and NONE of the Microsoft help forum posts mentioned Bluetooth being the cause when resolved.

OP - One thing I did notice, the controller itself may need an update. I HIGHLY doubt this will fix anything but I know several Microsoft help forum users reported this as a fix for them, but again best results I get are from years ago. Best of luck.

Here's one that took me 2 seconds to find - https://answers.microsoft.com/en-us/windows/forum/all/new-xbox-wireless-controller-not-working-correctly/aceda9c7-9e89-4655-9495-4ff1489443af

As you can see it describes the issue exactly even how the issue seems to be game specific. the pad is broadcasting a bad HWID when connected via bluetooth, that's the issue,

[Victor Von Queso]

Originally posted by ReBoot:

The culprit is the system XInput driver.

Or so the debug log says anyway. Mass Effect supports XInput gamepads just fine by default. The symptoms you observed point to something else entirely messing with the XInput driver. Usually, it doesn't crash and usually, it doesn't exhibit the behaviour you've described in Mass Effect.

I don't know whether you've ever touched input mappers, input injectors or whatever so let's go with what you totes have installed & even available: Steam's input mapper. Disable the one for XInput, restart Steam. See if the problem still appears.

That said, did you (or someone else using this computer with administrative privileges) install anything input-related, like, EVER?

I have never installed anything that changes inputs, and I’m the only one with access to that laptop. All I’ve ever done is connect the controller to Bluetooth.
So how or where do I go to disable steams XInput?

[theboz1419]

I just ran into this exact issue on my Asus gaming laptop after downloading another game Metro 2033 that's currently free to get. I use a Xbox elite controller and have had no issues when playing Baldurs 3. But, I started the Metro game without the controller connected to the laptop and it started just fine. I connected the controller and was told I needed to update something so that it would work. I restarted the computer as instructed and now when the Xbox controller connects, it crashes to the same error as the OP and I have fix using the Asus rog program that fixes faults. I then was able to restart the computer without issue and soon as I connect the controller it BSOD and again I must go into Windows and Asus fix program to restart the laptop.

[June]

This thread was quite old before the recent post, so we're locking it to prevent confusion.