[CTD] DXGI_ERROR_INVALID_CALL (0x887a0001)

Bug Reporting Hub Crashes (CTDs)
,
44

Uninstalling the NVIDIA App helped me to get no more CTD and i can use the OpenXR toolkit

45

I have the same problem. My FPS is very good (50-70) at high settings and in VR. Then, after a few minutes, it goes plong and the sim crashes with a CTD or the PC freezes completely. However, I’ve had these problems right from the start, regardless of which updates or programmes are running.
I´m running a RTX-4070 with a AMD Ryzen-7 5800 x3D

46

image
image1094×1179 143 KB

47

I don´t use the Nvidia App :frowning:
I’m about to remove the Nvidia 4070 and order an AMD Radeon RX 7900 XTX Vapor-X 24G.

48

Any word on whether this can be fixed in a Sim Update?

Or is this fixable another way?

Am using stock settings, no overclocks, latest drivers, etc on my Alienware M15 R7 with an RTX 3070 Ti LPTOP 8GB GPU and still get these CTDs.

49

Having same issues. 2024 is a joke! I’m sticking to 2020.

1 Like
50

I’m having the same issue after about 20-30 minutes of flight. What program was conflicting with MS 2024 for you? how did you find out?

51

It was my Sim motion racing motion compensation software that was the issue.
If I enabled the motion compensation overlay, that would create a memory leak that would use up all of my 64 Gigs of my memory.

Activating and centering the motion compensation works without issue, it was just the overlay that was the culprit.

52

Thanks, I do run openxr motion compensation as well! I do remember turning on the CORS overlay in my last flight that crashed. If it’s just a matter of turning off the overlay I’ll be very happy as it’s an easy fix. I hope I can still run the motion compensation without the overlay though because it’s pretty essential to flying with a motion platform. I’m using simhub btw.
Would be good if other people having this issue can also confirm that they are running openxr motion comp.

53

I use the WIT motion hardware box attached to my rig.

In my case, just not enabling the overlay fixed it, centering and activating the motion compensation still works without causing crashes.

There is a discord called OpenXr-MotionCompensation that has a lot of good information and they addressed this issue.

Good luck to you. Can’t fly without motion!!!

54

I have not experienced this error for a while so I think it was the CORS overlay that caused this because I used to turn it on and leave it on whenever I felt my motion compensation was not feeling right.
Now I always make sure to turn the overlay back off and I have not experienced this particular issue since then.
Thanks!

55

Thank you all so much for this info regarding Open XR Motion Compensation!!!

I had just completed a multi-hour flight without issue, landed, accidentially pressed the comma key (my button mapped to toggle the overlay) and sure enough, minutes later I received the dreaded crash.

I have changed the key mapping to something I can’t press accidentally and I will report back in a few weeks after I’m confident the OpenXR motion compensation overlay was the real culprit.

Had to post to keep this thread from dying.

56

I just got in in 2020 with no input to the keyboard. I left the sim running for an hour, aircraft parked (172) at an airport.

57

20250421_180236
20250421_1802361920×1081 97.9 KB

Same error here. Was flying with Pimax Crystal Light, latest Nvidia Drivers (April 2025), Asus Astral 5090 and top cpu and ddr5.
Crashed when I was changing settings from TAA to DLSS.

58

Do you have the same issue if you follow the OP’s steps to reproduce it?

A l’ouverture du PC certaines icones avait disparu
Impossible d’ouvrir msfs2020 et 2024 SU2
RĂŠinstallation uniquement de MSFS 2024 SU2
Problème de carte graphique
•

Provide extra information to complete the original description of the issue:
RĂŠinstallation carte graphique NVIDIA RTX 4070 TI

|Processeur|13th Gen Intel(R) Core™ i7-13700KF 3.40 GHz|
|MĂŠmoire RAM installĂŠe|64.0 Go (63.8 Go utilisable)|
|Type du système|Système d’exploitation 64 bits, processeur x64|

•

If relevant, provide additional screenshots/video:

Capture d'ĂŠcran 2025-05-04 121221
Capture d'écran 2025-05-04 1212211366×927 81 KB

•

59

Hello, I have same issue - for me it seems external library cased this → UltraLeap OpenXR

Zrzut ekranu 2025-06-18 083905
Zrzut ekranu 2025-06-18 0839051572×610 76.3 KB
60

Hello,

Getting the same error now, in VR, when a flight starts, latest SU5 beta. It’s a first, I never got this before. Happens only in VR (Virtual desktop, Quest 3).

Edit: does no seem to happen if FS is set to windowed mode, I did a couple of flights in VR with no issue since then.

61

Getting the same error in VR with version 1.6.34.0. NVIDIA driver version 591.86 and app 11.06.383. No DLSS overrides or frame gen overrides applied in the app. DLSS Quality and frame gen x4 set directly in MSFS 2024. Completely disabled OpenXR Toolkit and all custom settings in PimaxPlay. Tried launching directly through PimaxPlay and through SteamVR. Changed the game from fullscreen to windows. The game launches just fine in both cases, and I can see the menu in VR. Once I start a Discovery Flight through the “activities” page, I see the error message shown above, and the game crashes. Might try installing SU5 beta to see if that resolves it as the post above references that version.

Update: Installed latest SU5 beta 1.7.9.0, and the problem persists.

62

Update #2: The game works just fine in 2D. I can play other games in VR, so this does not seem to be an issue with drivers or PimaxPlay.

The steps here were not helpful: https://flightsimulator.zendesk.com/hc/en-us/articles/6422969348508--Your-graphics-device-has-encountered-a-problem-and-Microsoft-Flight-Simulator-will-exit-error-message

The crash happens when I attempt to start a Discovery Flight in any location. I click on “Start Exploring” once the game has finished loading the selected location. I see a loading screen with the Earth set in a black background and then an external view of my plane for a split second, after which, the screen goes black, and I see the error message.

New things I tried today:

  1. Completely reinstalled and patched to latest SU5 beta. (I have this game on Steam.)

  2. Cleared rolling cache.

  3. Cleared contents of StreamedPackages and SceneryIndexes folders.

  4. Turned off frame generation and DLSS entirely.

  5. Set VR global graphics to low end and turned off the dynamic graphics setting which maintains a target frame rate.

  6. Launched the game through both SteamVR and PimaxPlay.

  7. I have OpenXR Toolkit installed which I use in other games, but the Toolkit is disabled entirely. It’s not enabled when I check OpenXR API layers. I haven’t had an issue with other games where I use it (IL-2 Great Battles and Falcon BMS). I have also been able to run DCS when I disable OpenXR Toolkit since it is not supported.

  8. I also have the OpenXR OBS Mirror, which I have tried toggling off and on, and this makes no difference.

Hardware:

VR: Pimax Crystal Super QLED 57 PPD

CPU: i7-14700K

GPU: MSI GeForce RTX™ 5080 16G INSPIRE 3X OC G5080-16I3C

63

UPDATE #3:

Found a workaround (not a solution). Please fix this.

  1. Start game from desktop using PimaxPlay Virtual Desktop overlay in the headset. Game launches in 2D, but I can see the game and navigate the menu from inside the headset.

  2. Start the Discovery Flight by clicking “Start Exploring” and then “Begin Flight.”

  3. Once the flight starts, quickly switch to VR mode by pressing the shortcut. (CTRL + Tab for me.)

After that, the flight seems to run fine so far in VR. Otherwise, starting VR too early, such as at game launch, causes the crash described above after clicking on “Start Exploring” before I can click on “Begin Flight.”