CTD when connecting or disconnecting a USB device

I also have this issue. Microsoft store bought, PC, flying SFO-BOS and got almost to Chicago and needed to plug my headset in to charge.

Plugged my headset in, heard the blip of it being recognised, and the sim froze for 10-15 seconds and CTD.

Weirdly I’d booted the sim the day before forgetting to plug in my Logitech joystick and when reconnecting that prior to pushback the sim froze but quickly opened up the ‘new device detected. Customise or use default’ menu and was fine thereafter.

How on earth is this an issue in 2022!

Everything latest drivers and sim versions etc.

how relates the year here ?

I think we have to distinct the situations:

  • sound device switched / changed ( because e.g. over USB , but not special realted to USB )
  • any other USB device disconnected ( joystick, throttle , etc )

Feelt the reports with the sound-devices are a little bit less compared with first ages, but I think it is still not stable in case “somewhat is changed with the sound-device”. Handling of dynamicly switching sound-devices is not as easy as its sounds, but of course we all assume that an app not crash. I assume most players have a stable sound-device over the time and so the issue is not soooo often mentioned ( but still remember some issues where users use e.g. sound over hdmi and switching monitor off , etc. ).

Disconnecting e.g. a Joystick should of course each application can handle. But each time when I tried a redo what a user reported and disconnect wildly my joystick, throttle, etc. , the sim does at least not crash ( of course these handling with “determined new hardware dialog” is a bit , let’s say needs to be optimizated ). I start MSFS usually with all my devices connected ( its like a pre-flight-check :wink: ) and so may be I come not so often into the situation.

Yes but my sound device hadn’t changed, maybe going from wireless to wired, albeit through the same sound output device.

this sounds different:

And yes… USB vs WIFI is a change… I think you have also two different devices within the sound-settings-dialog.

But I wanted too mention only, thats the sound-switch-issue is different as (re)connect e.g. a normal joystick/throttle/controller/ device. This are two different topics ( needs different changes in implementation ).

I can’t start MSFS if my joystick is connected. When I disconnect it before I start MSFS the game starts. If I plug it in while MSFS is running it instaquits.

Faultbucket: 2027495476020482940, type 5

a question because I remember another topic: did you ever have your joystick to a different usb port connected ?

No, this was the first time I connected it to my computer. An old one.

1 Like

Hi,

Here goe smy bucket ID:

Fault bucket 1180917584865095082, type 4
Event Name: APPCRASH

Happened after connecting my Logitech G933 due to low battery warning.

Thank you for your help!

Maybe this will help everyone.

Never remove or insert a USB device when MSFS is running. :thinking:

Patient: Doctor, my arm hurts when I do this.
Doctor: Then stop doing it.

2 Likes

I had another one earlier today, triggered by my Logitech multi-panel not working correctly. I power cycled it via the button on my powered USB hub, and the sim crashed.

Faulting application name: FlightSimulator.exe, version: 1.26.5.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.26.5.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000022aecb8
Faulting process ID: 0x25b8
Faulting application start time: 0x01d882ff9d5147a4
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report ID: 96dddc1b-4e14-4569-919a-7b1e6eda2cac
Faulting package full name: Microsoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Fault bucket 1806376164310653869, type 5
Event Name: MoAppCrash
Response: Not available
Cab Id: 0

Thank you for clarifying. I indeed confirm that in my case switching off my headset will result in a sim CTD systematically. I do not recall it was always the case.

Is there any workaround to avoid that?

Sam

This bug used to be fixed for me. No longer so since WU10.

Mouse low battery warning this evening so I connected it to USB… instant game freeze and CTD. Repeatable on the ground afterwards. Immensely frustrating.

Faulting application name: FlightSimulator.exe, version: 1.26.5.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.26.5.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000001fa9310
Faulting process ID: 0xd6c
Faulting application start time: 0x01d885b06463b1fb
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report ID: a143bc15-be23-4742-880c-1d36c238de02
Faulting package full name: Microsoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

I just unplugged my wired Optical USB mouse and
wired USB keyboard and there was no change to FS2020.
Then plugged them back in.

Plane sitting on runway. Not affected.
Z390 motherboard.

i have the same issue. I unplug speedlink joystick and plug it back in when the sim is running and the sim completely shuts down.

Mine freezes as well under the same situations - - when unplugging any USB device. It also froze after disconnecting/connecting bluetooth headset during flight. I’ve had 3 flights freeze in a row because of this.

I have a KVM switch to control mouse/keyboard between two PC’s, I also control sound with the PC that isn’t the flight sim one. I am totally unable to use two PC’s in this scenario, or I will not finish the flight and CTD.

The USB input/output has been a problem with this simulator since Alpha. How much longer should we wait to get this sorted out?

Link the topics is better than split :wink: