CTD since today with or without Community empty

User Support Hub Crashes (CTDs)
,
1

CTD since today with or without Community empty.
Impossible to load in Safe mode CTD too

Here log on Event Viewer
Faulting application name: FlightSimulator.exe, version: 1.37.19.0, time stamp: 0x00000000
Faulting module name: VCRUNTIME140.dll, version: 14.40.33728.0, time stamp: 0xf3e8e773
Exception code: 0xc0000005
Fault offset: 0x0000000000001031
Faulting process id: 0x0x82C
Faulting application start time: 0x0x1DAE2E0BC5EA2B2
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.37.19.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.VCLibs.140.00.UWPDesktop_14.0.33728.0_x64__8wekyb3d8bbwe\VCRUNTIME140.dll
Report Id: 8458ac15-f6b9-4efe-956e-83ae58c49e7d
Faulting package full name: Microsoft.FlightSimulator_1.37.19.0_x64__8wekyb3d8bbwe

Faulting application start time: 0x0x1DAE2E0BC5EA2B2
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.37.19.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.37.19.0_x64__8wekyb3d8bbwe\openxr_loader.dll
Report Id: e203e81d-a320-47ea-8099-edac12d5e47d
Faulting package full name: Microsoft.FlightSimulator_1.37.19.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID:

Faulting application start time: 0x0x1DAE2E0F5AE7DD8
Faulting application path: C:\Program Files (x86)\Addon Manager\couatl64\Couatl64_MSFS.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 2746ee22-0117-4081-a2f1-31b0be5a5463
Faulting package full name:
Faulting package-relative application ID:

6

If you have the Oculus program installed, it’s been causing problems lately and there are some discussions about it here. Long story short if you have it, try uninstalling it.

1 Like
7

Thanks
I uninstalled it and now MSFS load correctly! Tomorrow (here its late) I will try to install it again to see if the issue persists.
Its maybe the last update of Oculus the problem…

2 Likes
8
1 Like
9

Finally I reinstalled Oculus Software, disabled Public Test Chanel and the CTD comeback. I tried to by disabling Developer runtime feature and no change still have CTD.
I hope Meta will do a patch soon, Im sure Im not alone to cry now :sob:

10

Disable the OpenXR Toolkit and wait for fix.

image

2 Likes
11

For me its only Oculus Software who cause the crash. I removed only OpenXR TK and problem persists.

12

Kinda how it was for me. I had been using virtual desktop for a while but kept the Oculus software installed thinking it had drivers VD needed to run. When it started crashing a lot, I tried uninstalling it and was still able to use my Q3 on VD without issue. I was never in the Oculus beta program

13

I have the same CTD, but I confirm what TenPatrol wrote. Disable OpenXR toolkit and the problem is solved for now. There is no need to do anything with Oculus Software. I hope Oculus fixes the problem because OpenXr Toolkit is an important tool for VR

1 Like
14

What is your setup on the Oculus app? MSFS always has a CTD when Oculus is installed.

Thanks for your advices

15
1 Like
16

Good: Now I can load MSFS without CTD
Bad: Quest2 link not bring me at the virtual desktop then I cant switch to VR
Maybe I did something wrong in the setup?

17

Uninstall Quest software.

Restart PC.

Install v68 and join PTC.

Meta’s developers have released a patch that fixes the compatibility issue with the OpenXR Toolkit.

I recommend participating in the public test channel v68 to install the hotfix.
https://forums.flightsimulator.com/t/fyi-oculus-software-causing-the-sim-to-crash/650460/32?u=tenpatrol

1 Like
18

The problem seems to have been resolved since last patch. I tried Oculus without OpenXR and with it and now both work together.

Thanks for your help again

1 Like
19

You’re welcome.
Please mark this as the solution if it helped you. Others can easily find it too.

1 Like