I have recently upgraded my PC to a Windows 11 machine. I use AAO to interface an X-Touch Mini. With nothing in the community folder other than Lorby hooks I get an MSFS CTD a few minutes after starting AAO. I have tried starting AAO before and after MSFS, no difference. No other FS related programmes are running. If AAO is not running everything is fine.

Please can anybody suggest a possible cause, or what I can do to narrow down the cause?

Thanks, Glyn

Sorry, no idea.

What are you using the X-Touch for, what actions have been bound to it? Did you download and import any templates or scripts?

Edited January 22, 20233 yr by Lorby_SI

Thanks for the reply.

I have tried reinstalling AAO, I have no scripts and only a very basic template for the Asobo C172 with Baro and parking brake.The CTD appears to only happen if Midi devices are enabled.even if the X-Touch is not plugged in. The AAO log is:

22/01/2023 1:30:51 pm.868 : SH: Exception received: 3 from send id 123 errloc 1
22/01/2023 1:30:51 pm.870 : SH: Exception received: 7 from send id 125 errloc 3
22/01/2023 2:22:57 pm.161 : SH: SimConnect connection interrupted
22/01/2023 2:23:00 pm.679 : SH: SimConnect connection unstable
22/01/2023 2:23:00 pm.679 : SH: SimConnect connection lost - reconnecting

And the Windows event is:

Faulting application name: FlightSimulator.exe, version: 1.29.30.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.29.30.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000000b48128
Faulting process ID: 0x5070
Faulting application start time: 0x01d92e64f3939513
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.29.30.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.29.30.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report ID: 64a78256-028e-45a6-9be4-41d7f025178f
Faulting package full name: Microsoft.FlightSimulator_1.29.30.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

The failing module is sometimes different, see these 3 events for similar cases:

Faulting application name: FlightSimulator.exe, version: 1.29.30.0, time stamp: 0x00000000
Faulting module name: WwiseLibPCx64P.dll, version: 0.0.0.0, time stamp: 0x60a67fd2
Exception code: 0xc0000005
Fault offset: 0x00000000001a91b3
Faulting process ID: 0x5a0c
Faulting application start time: 0x01d92ddcf4b709a8
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.29.30.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.29.30.0_x64__8wekyb3d8bbwe\WwiseLibPCx64P.dll
Report ID: b60134a3-fc5a-46b0-b927-7b9240a54f1f
Faulting package full name: Microsoft.FlightSimulator_1.29.30.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Faulting application name: FlightSimulator.exe, version: 1.29.30.0, time stamp: 0x00000000
Faulting module name: nvwgf2umx_cfg.dll, version: 31.0.15.1740, time stamp: 0x631f83a5
Exception code: 0xc0000005
Fault offset: 0x0000000000d4b879
Faulting process ID: 0x4838
Faulting application start time: 0x01d92de061698e61
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.29.30.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\windows\system32\DriverStore\FileRepository\nv_dispsig.inf_amd64_9751f6c72c23c322\nvwgf2umx_cfg.dll
Report ID: fefb5580-a7ec-4aac-a54a-eddc5e69b82e
Faulting package full name: Microsoft.FlightSimulator_1.29.30.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Faulting application name: FlightSimulator.exe, version: 1.29.30.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.29.30.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000001f91880
Faulting process ID: 0x1704
Faulting application start time: 0x01d92de222115d02
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.29.30.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.29.30.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report ID: 9a31bacd-3c8e-4830-be4f-6fd38b4d46e0
Faulting package full name: Microsoft.FlightSimulator_1.29.30.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

 

Does this help and can I try anything else?

Thanks,

Glyn

1 hour ago, Glyn said:

Does this help

No, sorry. Only the developer of the sim might know (=Microsoft or Asobo). "wwise" is the sound library I think, that my tie in with MIDI. "nvwgf2umx" is probably the NVidia Driver, I fail to see how that could be related.

I've never heard of a case like this. It doesn't really make any sense either TBH. The only connection that AAO has to the sim is through the SimConnect API. Controllers, MIDI devices etc. are not present in this API at all. AAO does not mess with the simulator controllers or anything like that.
I would understand it if AAO would shut down unexpecetedly, but not the simulator. I could again see trouble if there was a .Net component missing or something - but then again AAO would crash, not the sim.

All computers here are also running Win11 btw.

Maybe you have another controller app running at the same time that is causing this conflict? Like FSUIPC or SPAD? 

1 hour ago, Glyn said:

The CTD appears to only happen if Midi devices are enabled.

When exactly does that happen, when you are doing what? Just start AAO, press the button, connect to the sim?? Are you certain that you've installed the MSFS version of AxisAndOhs?

Also, go to Hardware->Device Blacklist and move everything into the list on the right with the "Ignore" button that isn't a game controller or the MIDI device. All HID devices, keyboards, mice, they all must be ignored. Leave only that on the left that you are actually using with AAO.

Edit: I just remembered, two people had trouble with the WASM modules being compiled incorrectly or not at all. Try deleting the generated folders for the AAO module (lorbysi-content-hooks) here: Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\packages
But then again, this only caused the module being unresponsive, and it also has nothing whatsoever to do with MIDI.

Edited January 22, 20233 yr by Lorby_SI

1 hour ago, Glyn said:

22/01/2023 1:30:51 pm.868 : SH: Exception received: 3 from send id 123 errloc 1
22/01/2023 1:30:51 pm.870 : SH: Exception received: 7 from send id 125 errloc 3
22/01/2023 2:22:57 pm.161 : SH: SimConnect connection interrupted
22/01/2023 2:23:00 pm.679 : SH: SimConnect connection unstable
22/01/2023 2:23:00 pm.679 : SH: SimConnect connection lost - reconnecting

I just noticed, the app has been connected to MSFS for 52 minutes at this point. So this is not a systematic error that happens right away, but "something" that happens or might not happen? The different modules in the Windows Event Logs may point to different causes altogether, it may just be coincidence that you have AAO running in MIDI mode at that point?

I have kind of the same problem on my devel computer. Most of the time MSFS is not running for more than 20-30 minutes, then it crashes. This happens with AAO or without, it just happens. The last version of MSFS before the current beta was the worst, I even needed at least 5 attempts before I could even start the sim.