Same findings here - with SayIntention traffic enabled, a freeze will happen 95% of the time somewhere. Using SI without traffic for the past few days, not a single freeze.
I had SU3 freeze couple times on me this week, so the issue may not be SU4 related for me at least, but it was happening more often in SU4.
CTD about 5 minutes after take-off.
Not using SayIntentions or anything else, so deinitely in the sim itself.
CTDs now worse than when FS2024 was released. Iâm now getting them quite regularly.
VR gtx1080Ti 64Gb ram
Freeze is a different scenario then a CTD
I also had my first freeze (picture frozen, sound still playing) using the latest beta with SI and SI Traffic
I am having the same issue on Beta 4 1.6.11.0⊠During the flight (about 1 hour in the flight) the sim will freeze and event viewer will display different types of errors until the video driver crashes and the have to force restart.
Some of the errors are: (screenshot of the performance monitor)
it starts with .net errors for FSDT
Faulting application name: couatl64_MSFS2024.exe, version: 5.0.0.6020, time stamp: 0x68a72d4d
Faulting module name: clr.dll, version: 4.8.9310.0, time stamp: 0x67db4f32
Exception code: 0xc0000005
Fault offset: 0x000000000000657c
Faulting process id: 0x3AC4
Faulting application start time: 0x1DC3754E2D223B8
Faulting application path: D:\MSFS2024\Addon Manager\couatl64\couatl64_MSFS2024.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: 8dd2e37a-68b0-4e1b-b7e5-e0ad5ea08038
Faulting package full name:
Faulting package-relative application ID:
Then
Faulting application name: dwm.exe, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc00001ad
Fault offset: 0x00007ff990c3b5b8
Faulting process id: 0x5530
Faulting application start time: 0x1DC376C52D042B7
Faulting application path: C:\Windows\System32\dwm.exe
Faulting module path: unknown
Report Id: 6397d77a-1649-46ac-b398-8f3765db7b8b
Faulting package full name:
Faulting package-relative application ID:
Faulting application name: svchost.exe_DiagTrack, version: 10.0.26100.5074, time stamp: 0x00e1a740
Faulting module name: diagtrack.dll, version: 10.0.26100.6725, time stamp: 0x90a0d3df
Exception code: 0xc0000409
Fault offset: 0x00000000001ccd00
Faulting process id: 0x1470
Faulting application start time: 0x1DC3753CD277151
Faulting application path: C:\WINDOWS\System32\svchost.exe
Faulting module path: c:\windows\system32\diagtrack.dll
Report Id: 7c75ddc2-3c65-4412-a9c5-d88d9b5e69a9
Faulting package full name:
Faulting package-relative application ID:
The GPU has been disconnected and this application may become unresponsive.
Error code: 10
(pid=30428 tid=16584 fsrealistic.exe 64bit)
Visit NVIDIA Customer Support for more information.
Application: FileOperator.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileLoadException
at FileOperator.Program.Main(System.String)
Faulting application name: svchost.exe_DiagTrack, version: 10.0.26100.5074, time stamp: 0x00e1a740
Faulting module name: diagtrack.dll, version: 10.0.26100.6725, time stamp: 0x90a0d3df
Exception code: 0xc0000409
Fault offset: 0x00000000001ccd00
Faulting process id: 0x1470
Faulting application start time: 0x1DC3753CD277151
Faulting application path: C:\WINDOWS\System32\svchost.exe
Faulting module path: c:\windows\system32\diagtrack.dll
Report Id: 7c75ddc2-3c65-4412-a9c5-d88d9b5e69a9
Faulting package full name:
Faulting package-relative application ID:
Faulting application name: FlightSimulator2024.exe, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00007ff7b2453627
Faulting process id: 0x40F0
Faulting application start time: 0x1DC3754932C68EF
Faulting application path: D:\XboxGames\Microsoft Flight Simulator 2024\Content\FlightSimulator2024.exe
Faulting module path: unknown
Report Id: 38a557b2-abc9-4602-bb48-d12334dcefb2
Faulting package full name: Microsoft.Limitless_1.6.11.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
I did launch MSFS2024 without addons to rule them out and YES the sim still crashes. I revert to SU3 and test with all addons and was able to complete a 6 hour flight from KLAX-MPTO
Update on this post.
After further testing, I resumed beta testing and downloaded update 1.6.16.0âŠ. freezing issue continued on latest NVIDIA driver. SIM stuttered and froze after an hour in flight.
After reviewing recommendations, I did and DDU for NVIDIA and did a clean install of driver version 576.40. currently on a flight from SFO-TPE and have been in the air for 10 hours. no simfreeze, no stutters, al setting are currently set to ultraâŠ
changed DLSS settings from DLAA to Quality on the super resolution
And what are you using for traffic and weather etc
Are you using simconnect tools?
Say intensions, active sky, fs2crew, fsrealistic, realturb?
And i assume itâs 1.16.13 sim version?
SI is aware of the simconnect issue and is working on a work around to be implemented until Asobo gets it fixedâŠ.
Yes i know. BUT is the simconnect bug the cause of the freezes. Do we know that for sure?
Yes, I asked about the freezes and was told it was an Asobo simconnect issue.
I asked âIs anybody having issues in SU4 Beta that SI causes FS2024 to freeze after about 15min. I guess maybe a simconnect issue?â
Quote as from SI, âI actually think we just narrowed down that SU4 bug and implemented a workaround that will solve it, until Microsoft fixes it.â
I really hope! i will test a short flight now!
How they âImplementâ Not sure on the how or when, but we shall see. Patience wins the race.
There was a new traffic changelog with 1 point about the freezes. I donât want to say it but as for now, 3rd flight, bussy airports (were freezes came faster) and until now⊠no freezes⊠I hope this wonât bang in my face cause i am on approacht o London Heathrow ![]()
FSTL traffic, Active Sky, FSRealistic, Cabby, Realturb, GSX. Yes, I am now on 1.6.13.0
just got a freeze two hours into an LEMD to HECA in the default A321Neo, running BATC (with traffic), Volanta and LittleNavMap
Might be a coincidence, as it doesnât happen all the time, but it seems to only happens to me when the sim is minimized. Plus the above mention of launching Say Intentions while the sim is already loaded.
Or something causes the monitor to refresh, like I had a long haul freeze when I turned my second screen on which caused my main monitor the sim was on to auto adjust.
Even in SU3, i was getting lots of 0x00000005 CTDâs mid flight, but has been great since installing nvidia 581.42 (9950x3d/5090)
Mine is with the default 737 Max 8, not the 787 or any other addon


