My earlier post was a ctd about 30 seconds into flight.
Then i reloaded and flew fine for about half an hour. Exit to main, start another flight, same aircraft and CTD just after clicking fly now
Fault bucket 1690715553070627739, type 5
Event Name: MoAppCrash
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: mimalloc.dll
P6: 0.0.0.0
P7: 6703ed67
P8: c0000005
P9: 00000000000018f3
P10:
Attached files:
\\?\C:\Users\smitty\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\AsoboReport-Crash.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD877.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDBD4.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDC03.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDC01.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDC22.tmp.txt
These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.Limitl_db82f5cb3fab0c7af6625e962ee68b4fbf01ec7_4c2ce5b9_7229accb-b116-4eec-a44c-b99b250d949a
Analysis symbol:
Rechecking for solution: 0
Report Id: e6886174-c837-49e9-bdda-58ac55920b15
Report Status: 268435456
Hashed bucket: c5200776ff12f240a776a0d67500bb9b
Cab Guid: 0
Faulting application name: FlightSimulator2024.exe, version: 1.4.7.0, time stamp: 0x00000000
Faulting module name: mimalloc.dll, version: 0.0.0.0, time stamp: 0x6703ed67
Exception code: 0xc0000005
Fault offset: 0x00000000000018f3
Faulting process id: 0x4062c
Faulting application start time: 0x01db9dd94b410a6a
Faulting application path: C:\Program Files\WindowsApps\Microsoft.Limitless_1.4.7.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.Limitless_1.4.7.0_x64__8wekyb3d8bbwe\mimalloc.dll
Report Id: e6886174-c837-49e9-bdda-58ac55920b15
Faulting package full name: Microsoft.Limitless_1.4.7.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
with switching to taa from dlss I still have ctd’s from time to time, but not every flight
For those running into this CTD, can you confirm if you are on the latest Nvidia driver v572.83?
If not, can you update and let me know if you still run into this CTD?
I cannot use any 572.xx driver because I will get a CTD every single time when I clicke fly now - or within 15 seconds into the flight. I have to use 566.36. CTD occurs if I use DLSS or TAA.
Fault bucket 1553003258757177939, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: FlightSimulator2024.exe
P2: 1.4.12.0
P3: 00000000
P4: FlightSimulator2024.exe
P5: 1.4.12.0
P6: 00000000
P7: c0000005
P8: 00000000043f771f
P9:
P10:
To confirm, I cannot run any 572.xx driver as the sim will CTD or freeze the PC requiring a reboot. I have to run with 566.36. Also, I can’t run the latest beta with the Nvidia app installed - there is an instant freeze of the PC that requires a reboot.
I have tried every 572.xx driver with the latest SU12 with a guaranteed CTD or PC feeze with all of them (when clicking on ‘fly now’, when the map starts to zoom into the departure airfield)
No go here - guaranteed crash with DLSS or TAA. I have tried with DLSS supplied with 2024 SU2 beta and with the update to DLSS 4
Same here, on latest Nvidia driver, instant sim lock-up when using TAA/FG when clicking on Fly Now that results in having to end the program through steam. Rolled back to stable build for now until resolved.
4080, 12700k, 64gb DDR4, nvme
Just an update as I was experiencing full system crashes when clicking Fly Now when using Nvidia Frame Generation on the latest beta builds.
A workaround for me for now was disabling G-Sync or lowering my monitor refresh rate from 240Hz to 144Hz.
I’m currently using the latter workaround as it gives me a smoother experience.
I suspect issues related to the 572.83 driver release as these exact issues seem to be causing problems for many across multiple titles with these latest drivers.
Not quite sure if I should report this here but I thought it might be relevant given the feedback has been logged:
I’ve been using NVIDIA DLSS Super Resolution with DLAA all along while testing SU2 Beta. I’ve been using DLSS frame generation on and off as I try different settings to see what gives the smoothest flight.
I do not get a CTD every time I click Fly Now but I do sometimes. I also get random CTDs while flying and random CTDs after I end a flight as the world map is reloading. Similarly, I experience random freezes that require an end task.
I just updated to 1.4.14 and currently have DLSS 2x FG enabled in combination with the FrameLimiter parameter set to 30 in UserCfg.opt. I have the global settings at Ultra. I was finding this to be a good solution to have the Ultra settings and maintaining 60fps in nearly all situations including busy airports. I have Live weather and traffic set.
I have stopped using the Communications system for now as I’m suspicious it’s strange behaviour may be contributing to the random CTDs I’ve been having with each build - it’s anecdotal but I do believe I’ve been experiencing less of them because of it.
In the same session after updating to “14” I had a successful, short flight around CYVR in the C172 and was able end the flight without issue and return to the world view. I then selected KLAX but made no other changes. After clicking Fly Now I had a CTD with the following info in the event log:
Fault bucket 1453260093519454333, type 5
Event Name: MoAppCrash
Response: Not available
Cab Id: 0
Problem signature:
P1: Microsoft.Limitless_1.4.14.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.4.14.0
P4: 00000000
P5: CoherentGTJS.dll
P6: 0.0.0.0
P7: 67b87deb
P8: c0000005
P9: 000000000032b59b
P10:
I then re-ran the sim and started a flight at KLAX with the same settings.
I’m running a 5070 Ti with the 572.83 drivers. (I had the newer ones installed but rolled them back when I learned about the temp sensor bug!)
In summary:
- not every time just because DLSS is enabled
- not every time due to selecting KLAX
- still getting random Fly Now CTD with the latest beta build
Your post is old as heaven at this point, but I made a post about the issue and what was causing it here.
Ignore what I wrote about the X.16 drivers and download the latest one 576.02. Not a crash since where earlier it was causing reboots four times in a row when pressing ‘start flight’ (I stopped there and decided I’ve seen enough evidence).
–If your cat explodes or MSFS2024 starts a bootloop I’m not responsible, but this works for me–
