Crash shortly after clicking "Fly Now" when DLSS is used

🔒 Sim Update 2 Beta | MSFS 2024 CTDs
, , , ,
1

ISSUE DESCRIPTION

Description of the issue:
crash after some seconds in every flight

Did you experience this issue before you joined the Beta?
No

[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue?
yes - and yes

FREQUENCY OF ISSUE

How often does this occur for you (Example: Just once, every time on sim load, intermittently)?
every time

REPRODUCTION STEPS

Please list clear steps you took in order to help our test team reproduce the same issue:

  1. load plane (eg pc24 from lfsb) hit fly now, after in cockpit, crash occurs after 10 to 45 sec.

YOUR SETTINGS

If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.

What peripherals are you using, if relevant:

[PC Only] Are you using Developer Mode or have you made any changes to it?
no

[PC Only] Many issues may be due to an outdated graphics card. Please state your Graphics Card Driver Manufacturer (NVIDIA, Intel, AMD) and Version:
nvidia 3090, newest driver 572.83, win11

[PC Only] What other relevant PC specs can you share?
crash details:
Name der fehlerhaften Anwendung: FlightSimulator2024.exe, Version: 1.4.7.0, Zeitstempel: 0x00000000
Name des fehlerhaften Moduls: nvwgf2umx.dll, Version: 32.0.15.7283, Zeitstempel: 0x67d4654a
Ausnahmecode: 0xc0000409
Fehleroffset: 0x0000000000f65401
ID des fehlerhaften Prozesses: 0x0x5338
Startzeit der fehlerhaften Anwendung: 0x0x1DB9DC3CBDC1930
Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\Microsoft.Limitless_1.4.7.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe
Pfad des fehlerhaften Moduls: C:\WINDOWS\system32\DriverStore\FileRepository\nvaki.inf_amd64_63ddf73a484c80cd\nvwgf2umx.dll
Berichtskennung: 1924ede0-3f4c-490b-80ca-bac65f561010
Vollständiger Name des fehlerhaften Pakets: Microsoft.Limitless_1.4.7.0_x64__8wekyb3d8bbwe
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App

MEDIA

Please add a screenshot or video of the issue occurring.

[END OF FIRST USER REPORT]

:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

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

Provide extra information to complete the original description of the issue:
•

If relevant, provide additional screenshots/video:
•

2

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

Provide extra information to complete the original description of the issue:
•

If relevant, provide additional screenshots/video:
• yep had 3 ctd in row it not working

3

same just had 737 crash on mission start wouldnt be too bad except update to SU2 removed all my career money so cant afford to fix it

4

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:
• Click fly now, when in cockpit my PC freezes and reboots within 15 seconds (after scenery is loaded). My community folder is also empty.

If relevant, provide additional screenshots/video:
• none

5

Just crashed after launching FNX A319.

Get here to have more info about my build: CTD when choosing livery on A319 - FNX since SU2

1721808544087148058, type 5

ctd1001.txt (1.8 KB)

6

I believe this may be related to very high VRAM usage. I am getting CTDs everytime I try to fly. Usually within a minute or so. Monitoring with MSI Afterburner and using the exact same graphics settings in the prior build, I am showing exceptionally high VRAM usage.
I’ll get a message sometimes stating that the GPU is unable to keep up with graphics settings. Maybe half the time prior to a CTD. I have tried lowering Texture Resolution and other settings without effect.

7

Not sure about that. I’ve had the same bug manifest when loading into the 787-10 and my VRAM never exceeded about 12GB (of 16GB available).

8

hello,

I have tried several planes and every time I launch a flight…CTD :sleepy_face:

2 Likes
9

Hi there
I changed from dlss to taa → and it works without ctd → please check this, for me it works!

3 Likes
10

hello,

it seems to work, but for me I need to choose anti-aliasing=off and then I can put it back TAA

11

Beta or not, this is just frustrating. SU2 beta just rendered the sim unusable. CTDs all over the place - I can’t even start a flight anymore. Just short after restoring the sim due to the “phantom-update”, which emptied my community folder.

12

Thnx, this solved the issue for me, for now. Hope they fix DLSS asap again.

13

This did not fix it for me - I’m on TAA and I get a crash to desktop every single time that I click Start Flight- doesn’t matter if career mode or free flight. I’ve tried 6 different times and I’m 6/6 on CTD’s. I’m done for now. Maybe tomorrow. This is a horrible, horrible release.

2 Likes
14

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

Fault bucket 2256092180961697277, type 5
Event Name: MoBEX
Response: Not available
Cab Id: 0

Problem signature:
P1: Microsoft.Limitless_1.4.7.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.4.7.0
P4: 00000000
P5: nvwgf2umx.dll
P6: 32.0.15.7265
P7: 67c2140f
P8: 0000000000f650d1
P9: c0000409
P10: 0000000000000002

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5F40.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6319.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6349.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6347.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6367.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.Limitl_df1d7c36e21c5fcd83bd4099921056cb8da5a8cc_4c2ce5b9_9235e8a3-a2e0-402a-872f-1eecc3712585

Analysis symbol: 
Rechecking for solution: 0
Report Id: c91174d1-4b14-4581-8ec6-8140f0033b67
Report Status: 268435456
Hashed bucket: 63c64556fd410e8e5f4f3fe2a2c21dfd
Cab Guid: 0

Faulting application name: FlightSimulator2024.exe, version: 1.4.7.0, time stamp: 0x00000000
Faulting module name: nvwgf2umx.dll, version: 32.0.15.7265, time stamp: 0x67c2140f
Exception code: 0xc0000409
Fault offset: 0x0000000000f650d1
Faulting process id: 0x44b6c
Faulting application start time: 0x01db9dd5a357f027
Faulting application path: C:\Program Files\WindowsApps\Microsoft.Limitless_1.4.7.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe
Faulting module path: C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_a19d45a4528cefc8\nvwgf2umx.dll
Report Id: c91174d1-4b14-4581-8ec6-8140f0033b67
Faulting package full name: Microsoft.Limitless_1.4.7.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
15

I have changed the title of your post to reflect this information so your thread can focus on this particular bug. :slight_smile:

For anyone who is experiencing CTDs whose issue isn’t solved by the workaround in this thread, we ask that you please make a new bug report so we can track and investigate it as a separate issue. Thanks!

1 Like
17

CTD still happening with TAA, only later.

18

For those who have experienced this crash, if you are able to post your Fault Bucket ID here, our test team is requesting it!

19

Same issue as OP, Fault bucket 1186172334213174968, type 5

20

EDIT:
Just got a good flight after removing FSLTL (as several others pointed out).

Fehlerbucket 1186172334213174968, Typ 5
Ereignisname: MoBEX
Antwort: Nicht verfĂźgbar
CAB-Datei-ID: 0

Problemsignatur:
P1: Microsoft.Limitless_1.4.7.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.4.7.0
P4: 00000000
P5: nvwgf2umx.dll
P6: 32.0.15.7283
P7: 67d4654a
P8: 0000000000f65401
P9: c0000409
P10: 0000000000000002

Fehlerbucket 1909655048770578518, Typ 5
Ereignisname: MoAppHang
Antwort: Nicht verfĂźgbar
CAB-Datei-ID: 0

Problemsignatur:
P1: Microsoft.Limitless_1.4.7.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.4.7.0
P4: 00000000
P5: de6e
P6: 67246080
P7:
P8:
P9:
P10:

Fehlerbucket , Typ 0
Ereignisname: MoAppHang
Antwort: Nicht verfĂźgbar
CAB-Datei-ID: 0

Problemsignatur:
P1: Microsoft.Limitless_1.4.7.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.4.7.0
P4: 00000000
P5: de6e
P6: 67246080
P7:
P8:
P9:
P10:

21

The NVidia 57x drivers are very twitchy, not just with DLSS issues.
566.36 are more stable GeForce Game Ready Driver 566.36 | Windows 11 | NVIDIA
https://www.reddit.com/r/hardware/comments/1jhkzxo/psa_nvidia_widespread_black_screen_or_hard_os/

NVidia bears a lot of responsibility for these performance issues too, it’s not just MSFS DLSS implementation issues. NVidia driver releases are a real lottery atm. So if you encounter instability issues I suggest you need to consider both as potential causes, or a mix. AMD can also have issues like this.

3 Likes