There’s a possible fix here, I’ve just applied and about to test it out.
Let’s post our results here. Remember to create a Restore Point before modifying anything.
Cheers!
I use Resource Monitor (type it in the task bar search box) to monitor my memory usage.
While using the Crystal light, I can watch the commit values and the working set values for MS2024 continuously rise and my free memory continuously fall (goes to a low of about 300 MB) followed by a crash with the DXGI..CALL error.
I did notice that if I go into 2d when the memory usage is increasing, then go back into VR, the values will stabilize and I can then complete the mission without it crashing.
i did and no its not working for me
I have a gtx 480 super with 64gb ramm and 14 gen processor. I too had this error code, i used my stress testor and noticed my GPU and CPU hitting into the red . I found that lowering my settings 'sadly to a level not as graphically pleasing and using dlss auto with frame gen on and lowering LOD, the game ran without crashing after. Also i use DLSS swapper and make sure im using 3.8.10
Good luck hope this helps. 
Do you have the same issue if you follow the OP’s steps to reproduce it?
• I have the same crash also in VR using a Pimax Crystal Light and RTX4090 card. I can not get 15-20 minutes into a flight and then the crash happens no matter what I try.
Provide extra information to complete the original description of the issue:
•
If relevant, provide additional screenshots/video:
•
EDIT - I disabled the OpenXR toolkit and thought that was the issue however I tried again today without it and still got this crash. I am continuing to troubleshoot.
Just started having this issue today. Twice the sim crashed me all the way to system reset (why can it do that?) Third time, I got this error message. I haven’t been able to fly at all.
This issue also starts to happen to me today. If I disconnect my 3 monitors and connect them again, it works, don´t ask me why. But If I exit the simulator and try to enter again the error message (0x887a0020) apears again…
After a lot of reading…
I found a solution in another post: delete the nvidia new app (my issues started after I installed it), go to Nvdia website and download the 566.03 version of the driver. Install it using the exe you downloaded and not using the Nvidea GEForce Experience.
After that everithing is working perfectly again for me.
Same issue. Started today
Same issue since latest MSFS update! Had no such issue before.
Yesterday everything worked flawlessly, today the error message is back…
I installed msfs2024 (I was waiting until it became more stable) just to check if the driver will work and it did.
I then tried to flight msfs 2020 again and got the same error …
Yes it is the same for me. Yesterday i could fly without CTD the whole day.
Today after 2 hours of flying CTD again.
I’ve tried everything with this…..remove OpenXR tool, roll back the latest NVIDIA drivers to October version. Still get this CTD with about 20-30mins of starting a free flight with the Cessna 208. Also was happening with the Cessna 172 G1000. Funny thing was yesterday I was able to fly the 172 in career mode without this problem but today I still can’t begin a free flight without this crash. This was not a problem for me prior to the last MSFS 2024 patch so something in there has to be the cause. My computer is not overheating. I fly only in VR and now I can’t even use this sim. I hope this is fixed in the big upcoming patch!
I just flew 2 career flights with the Cessna 172 G1000 and then followed up with a free flight all in the same session and in the Cessna 172 and did not have this crash. This is just crazy and I cannot find a cause but my computer is not getting too hot and there was plenty of clouds and graphical goodness around to have caused an issue. I am going to try a free flight this evening in a different location and see if I have this issue there.
Tried a free flight again this evening in a different location with the Cessna 172 G1000 and got the INVALID_CALL CTD about 30 minutes in. I guess the career missions were not long enough to cause the crash even though I had a longer session in the sim I was going in and out of menus between missions so that might have been why. Seems like 30 minutes has been around my limit and this is happening now every full flight that I try to do no matter the aircraft. I’ve tried the C208 and Longitude in addition to the C172. I’m pretty certain this happened after last weeks patch as I’ve only been dealing with this since then. Prior I have completed 2 full flights since the sim was released. This has to be fixed as it is unusable for me in VR! I have not tried outside of VR because I am not set up to fly that way. I’m a bit concerned as I do not see any feedback or bug logged on this post and the next patch is coming next week.
You can use the Windows built in Resource Monitor program and then click on the memory tab.
In my case, my commit memory for the Microsoft flight simulator entry was steadily climbing while I flew.
Eventually it got to about 60 Gigabytes (I have 64) and I would get a crash with the invalid call error message.
It ended up being an external program I was running was somehow conflicting with MS 2024.
The commit memory stays pretty constant now.
After coming to an end of what I could test to make this error stop I started reading about people reinstalling their sim due to possible corrupt installations from the first day problems with the launch. I was one of the first ones to actually get a download and get into the sim but I did get hung up forever at 97% before I did.
Anyway with the speed at which you can install now I thought that I definitely could have a corrupt install so I decided to uninstall and reinstall. 2 nights ago after installing I was able to fly the Cessna 172 for over an hour with no crashes. This was completely vanilla sim with no addons active. Tonight I downloaded the latest patch and then tried another flight this time with my Navigraph stuff active in the sim which I had been using before. I had another successful flight with the C172 of over an hour. Previously this error would happen around 20-30 minutes in. I also noticed improved smoothness in VR after reinstalling.
I can only say that this worked for me and if you think that you might have a corrupt installation at all I think it’s worth a try to see if it will clear up these problems.
Do you have the same issue if you follow the OP’s steps to reproduce it?
• Yes
Provide extra information to complete the original description of the issue:
• Not using VR on my PC-RTX 3070 Ti Laptop GPU.
Happens with latest Nvidia driver when trying to lfy large or small aircraft-eg. Saab 340/Airbus A330/747-8 and TAA or DLSS with Debug mode on and AA disabled in the old Nvidia CP in Free Flight only.
No issue in Career mode for me it seems.
Disabled Dell overclocking in Alienware Command Center and BIOS.
Getting DXGI device removed and device hung errors too related to this as well.
If relevant, provide additional screenshots/video:
•
I also just got these same error messages yesterday in MS2024. I am now running a test in MS2020 and it is stable for now. I have a high end system with a Nvidia 4040 GPU and I notice my GPU with MS2024 is at 90% vs 60% with MS2020. Anyway - this error just started and happens every time I fly for about 20 minutes into the session.
I also got the error when I was just navigating in the menu and didn’t start a flight yet.
I have found out a bit more. The problem only occurs when I use the OpenXR Motion Compensation program. Without the program, I can fly without any problems. The simulator seems to have a problem with third-party apps.