I’ve been using the original and the beta aviators version with no issues until the last update to SU1.
Any flight and any aircraft - after 25-35 minutes of flight msfs CTD. Crash dump says ntdll and/or kernelbase errors. MSFS2020 runs for hours in same scenario.
system is intel 7700k at 5ghz - 32G ram rtx 3090 on 4K monmitor
what I have done with no effect
complete memory, drive and system tests - no temp CPU or other hardware issues.
Ran SFC and DISM to refresh system
uninstalled and reinstalled MSFS
deleted all caches including NVidia
Chose low end option
removed Community
no other add on programs running
tried 3 different NVidia drivers
Remember, everything was working perfectly until the RTM beta and final version.
I am assuming all I can do is wait until next beta drops and hope the issue is resolved.
Anyone have any ideas?
Thanx
1 Like
That’s a comprehensive list of troubleshooting. One thing to maybe try is to get Hwinfo64 and have it create a log file with all of the data about your system and if you know the CTD happens about the same time turn in the log file a few minutes before…can then try to see what might be happening at the CTD (is it vram or something unique to MSFS 2024 that doesn’t happen in say a stress test you might have already run). Feels like this is msfs2024 related if you have no msfs2020 problems and have run OCCT or some other stress test of the system. And the fact it happens repeatably, but it’s odd that it’s any airplane and even on lower graphics settings where maybe it’s not a vram leak bit something else accumulating in the background. Is it on any route you fly or on the same route? Good luck and I hope you get it figured out
I’ll check out HWInfo.
OCCT is my main stress tester and this system has ben solid as a rock for years.
Yup, any plane any flight. One thing I just realized is that in all cases I have been using the AP. I might try a manual flight and see if the same occurs. For me, the error is easily repeatable so I should know right away.
One other note, found a ms2024 crash dump and it indicates “bad allocation” which seems to support memory issues whether it be vram or system.