Reverting to 572.83 have solved it like before with the 4090 and now with the 5090, to the previous more stable in FS24 and FS20, though I don´t recommend it for the black screens maybe, I have a copy to restore and the iGPU, and starting the SO with the iGPU, change the NVIDIA driver, hope all go well.
Hi, when this happens to me I just ensure these two options are disabled
Then I start and it works
So I would say this is not on MS but on Nvidia
Regards
Carlos
576.28 seems to have worked for me. Previous to this I would constatly crash with the DXGI error after about 4 - 6 minute flight. Reverting to 576.28 has just let me complete a 25 minute flight. I will be trying a longer one tomorrow.
I certainly hope Nvidia or Microsoft/Asobo sort this one out soon. I have not seen any official developer acknowledgement of this issue yet.
I never had that error before, but now, with a new system and nvidia driver:
576.52-desktop-win10-win11-64bit-international-dch-whql I can’t get rid of it.. : (
Asus 4090 GPU, AM 9800
Rolling back to Nvidia driver 576.28 worked for me too, after trying everything else!
when changing the driver to 6653 and below this error disappears just check when approaching in the free flight settings and there is a departure at the border of land and sea at the coastline
With 576.52 and RTX 5080 I just had this happen 2x in a row during pushback. Super annoying.
Never had these crashes before with MSFS2024.
I’m going to DDU and try 576.28
1 Like
I used to get this error every time I tried to use MFS2024. Since I rolled back to 576.28 I haven’t had any CTDs.
This is becoming increasingly irritating. Every time I try to play, I receive this error. I have done all the aforementioned troubleshooting steps to no avail. Currently rolled back to the March 12th drivers, 572.83 but may have to try rolling back even further.
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:
Start the game. Maybe get a few minutes into the flight (mission) then crash. Sometimes it takes longer but each time. Sometimes I can get to the very end of a 1h 30min flight and then it crashes when going to the parking stand.
If relevant, provide additional screenshots/video:
If on PC, Fault Bucket ID - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:
Faulting application name: FlightSimulator2024.exe, version: 1.4.20.0, time stamp: 0x00000000
Faulting module name: nvwgf2umx.dll, version: 32.0.15.7652, time stamp: 0x6824e711
Exception code: 0xc0000005
Fault offset: 0x0000000000de163a
Faulting process id: 0x3384
Faulting application start time: 0x1DBD152ABC22CD3
Faulting application path: C:\Program Files\WindowsApps\Microsoft.Limitless_1.4.20.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe
Faulting module path: C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_2c61c4d89b199ea8\nvwgf2umx.dll
Report Id: cb58250e-ec96-43f2-85da-09037f9c6f68
Faulting package full name: Microsoft.Limitless_1.4.20.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
==================================================================
Fault bucket 1845292997727459629, type 5
Event Name: MoAppCrash
Response: Not available
Cab Id: 0
Problem signature:
P1: Microsoft.Limitless_1.4.20.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.4.20.0
P4: 00000000
P5: FlightSimulator2024.exe
P6: 1.4.20.0
P7: 00000000
P8: c0000005
P9: 000000000cdbb43d
**P10: **
**Analysis symbol: **
Rechecking for solution: 0
Report Id: 3aff787a-2e7b-485f-93b9-faf691ec76aa
Report Status: 268435456
Hashed bucket: 153be0730ebcd283f99bcc34640f992d
Cab Guid: 0
=================================================================
The description for Event ID 153 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
**The following information was included with the event: **
\Device\Video3
Error occurred on GPUID: 2d00
The message resource is present but the message was not found in the message table
ReplyClose
I come to reinforce this topic, in an attempt to bring attention to this problem. Unfortunately, I arrived at this forum too late. I just bought the game which has a quite high price and I can’t play it. Imagine my disappointment when I realized that many people have the same issue. The specs of my computer are as follows:
-Ryzen 5 7600X
-Intel Arc B580
-32G Ram
-1Tb SSD Nvme
I have searched all over the internet for solutions and I must have tried all of them without success, from the regedit trick to underclocking the GPU, reinstallations, different drivers, experimenting with graphics settings, and so on. The GPU shows no signs of overheating or strain, nor does the VRAM, and the RAM is also fine.
It is important to note that this only happens with msfs2024 and no other game or sim. And even here, I can enter missions, get the plane working, with perfect graphics, and then randomly the game crashes.
I plan to make a report to Steam as well, where I bought the game, because this is not acceptable at all.
Do you know if they are already doing something real about this?
Are people asking for refunds?
2 Likes
I am also having the errors as the OP. Rolled back to 576.28. Did DDU first, then NVCleaninstall with literally everything removed from the install except for the required drivers. Also disabled telemetry. 1hr flight in a cesna 172 over Brisbane, no issues. /crosses fingers.
edit:
welp, false alarm. Still having the same issue. 
1 Like
First flight in SU3 Beta .4 ended shortly after takeoff with this error.
C185, auto-gen KRBL, no traffic, no static aircraft, no fauna.
AMD RX 7900 XTX w/ 25.5.1.
I have this issue and made an account to report some information and add another voice to the chorus. I did a bunch of testing and found that I can reliably reproduce the issue any time the game renders a large amount of water (oceans or lakes). My system runs the game fine (~60fps) using High-End settings over land, but even on Low-End settings the game will crash as I go near water. For example, taking off from PDX and flying west, the game runs fine until approaching the coast. Career mode wise, the Madagascar mission and Instrument Training over Shetlands also cause the crash instantly.
Ryzen 9700x
Intel B580
64 GB RAM
All drivers up to date, including BIOS and chipset.
I know some of my friends who had this worked it through as an issue of too many devices like M2 drives that aren’t compatible (e.g. using mixed gen4/gen3/gen2 m2 drives with mixed keys) running on the PCI-E lane causing issues where the machine would crash. Also I’ve seen this happening if you are not running a swap file, finally as a suggestion try disabling rebar in the bios and see if that makes a difference).
i also have the same issue, its only started today (07/06/25) and i have changed nothing from when it was working okay last weekend, so between then and now something has upset the sim, i just can’t think what apart from Microsoft or Asobo messing about with stealth updates, have never had this message before and i have been using MSFS24 for months
And still this bug does not appear in the published BUG LIST. Why is that mods??
I recently decided to go back to 2020 because of the problem with ridiculously long control setting times in 2024. When I tried using 2020 again I got this device hung error whenever I started a flight. I never saw this error before in 2020 or 2024 (I have been using 2024 exclusively since November). But when I switched from DLSS to TAA, I was able to start a flight in 2020 without seeing the error. I could then switch to VR with DLSS and fly OK. I haven’t seen the device hung error since I started doing this.
1 Like
I get this error too since I updated my Nvidia drivers this morning to version 576.52. I did clean install it 2 times just to be sure.
Did a flight yesterday in FS20 with no issues with an older driver version (can’t remember which one).
Tried to go to the page that is suppose to have consolidated this issue, does not work
Also, this error just started for me today, tried the regedit fix, did not work.