After yesterday went off without a hitch I was thrown back on the desktop today (twice).

I discovered that I was still Online (as long as Multiplayer was active) but that Photogrammetry was now off.  I turned it back on but was thrown to the desktop again.

I then recalled someone mentioning signing off and logging back into XBOX might be appropriate so I gave it a go.  When I restarted XBOX and logged in, I got a message that there had been some changes to XBOX and that I needed to log off and start again.  After I started XBOX for the second time, I was able to run MSFS2020 and fly normally.

I'm hoping that will be the end of issues - we'll find out tomorrow.

Edited December 4, 20241 yr by RandallR

Ive had crashes recently as well an im pretty sure it was me updating a NVIDIA graphics driver. I think I need to go figure what one I had before and roll back. The last time I dealt with crashes it was the same thing. Its almost not even worth updating anymore unless you want to be frustrated

I rolled my driver back to 566.03 which I used previously and I am getting the exact same CTD. I can't even get more than 5 minutes into a session. Last Friday I had a perfectly good working sim. 

Thank you Microsoft, I do not know what you did behind the scenes but whatever it was please un do it !

3 hours ago, RJC68 said:

I rolled my driver back to 566.03 which I used previously and I am getting the exact same CTD. I can't even get more than 5 minutes into a session. Last Friday I had a perfectly good working sim. 

Thank you Microsoft, I do not know what you did behind the scenes but whatever it was please un do it !

Do you have multiplayer selected?

Mike

I just got another CTD as well. Says the fault is in nvwgf2umx.dll.  I haven't updated my NVIDIA drivers for a couple of months, ironically because it's been so stable (up until this week).

It's a hit and miss, obviously. I am on the latest Nvidia drivers and have just successfuly completed a DAAG-EDDF flight while a few days ago I got a CTD after just completing preflight at DAAG.

Edited December 5, 20241 yr by Jure

I am with Bob on this one with respect to graphics drivers. If it ain't broke, don't fix it.

3 hours ago, Christopher Low said:

I am with Bob on this one with respect to graphics drivers. If it ain't broke, don't fix it.

I went back to my original driver that I used for quite a while and it is exactly the same. The sim is unplayable for me right now, I have never had this in the 4 years I owned it.

6 hours ago, mikeymike said:

Do you have multiplayer selected?

Mike

I don't think so Mike but I will check this morning

It looks like the issue I have been having with the DXGI CTD is related too the Fenix A320 after this weeks update, I spawned at the same gate in the Inibuilds A320 and had no issues and then did 2 flights in the iFly 737 Max 8 without issues. 

I have reached out too Fenix and hopefully they are aware of this.

Getting worse for me, almost every flight gives a CTD now, never had them in all the time I've owned it until the past week or two. The most recent one has the faulting module as CoherentUIGT.dll

On 12/5/2024 at 11:01 PM, RJC68 said:

It looks like the issue I have been having with the DXGI CTD is related too the Fenix A320 after this weeks update, I spawned at the same gate in the Inibuilds A320 and had no issues and then did 2 flights in the iFly 737 Max 8 without issues. 

I have reached out too Fenix and hopefully they are aware of this.

After the last Fenix update I got the first DXGI CTD ever in MSFS2020. As I switched from TAA to DLSS and resume the flight, I instantly got the DXGI error.

On 12/7/2024 at 6:14 AM, Severne said:

After the last Fenix update I got the first DXGI CTD ever in MSFS2020. As I switched from TAA to DLSS and resume the flight, I instantly got the DXGI error.

I raised a support ticket with Fenix and they had me do the following;

Please try the following, in the Fenix.exe application:

Enable Alternative Display Renderer

Uncheck Display Sync

This actually fixed my problem. I have no idea why all of a sudden this is required. I never used these settings in the past. Something happened with the last update.