Constant CTDs with error 0xc0000005 since SU6
What can I do?
With SU5, I didn’t have a single CTD over the course of more than 100 flights.
Rename your Community folder to Community_old and then create a new empty folder named Community in the same location.
Next, locate your exe.xml file - once you find it, rename it to exe_old.xml
After doing that, launch MSFS and see if the CTD still happens.
The exe.xml file is located in the same folder as usercfg.opt
Thanks for the tip and the effort,
but renaming the Community folder didn’t make any difference.
I’ll include the error message here:
Name der fehlerhaften Anwendung: FlightSimulator2024.exe, Version: 1.8.14.0, Zeitstempel: 0x00000000
Name des fehlerhaften Moduls: FlightSimulator2024.exe, Version: 1.8.14.0, Zeitstempel: 0x00000000
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00000000031f5c94
ID des fehlerhaften Prozesses: 0x2f1c
Startzeit der fehlerhaften Anwendung: 0x01dd2bab14a397c8
Pfad der fehlerhaften Anwendung: C:\Program Files (x86)\Steam\steamapps\common\MSFS2024\FlightSimulator2024.exe
Pfad des fehlerhaften Moduls: C:\Program Files (x86)\Steam\steamapps\common\MSFS2024\FlightSimulator2024.exe
Berichtskennung: 3f90fbb5-c82e-4524-82be-b18a0f99abdd
Omg, I just had my first crash in MSFS24, ever.
Faulting application name: FlightSimulator2024.exe, version: 1.8.14.0, time stamp: 0x00000000
Faulting module name: FlightSimulator2024.exe, version: 1.8.14.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000031f3194
Faulting process id: 0x14D8
Faulting application start time: 0x1DD2C047E76978F
Faulting application path: C:\Program Files\WindowsApps\Microsoft.Limitless_1.8.14.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.Limitless_1.8.14.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe
Report Id: ca1124dc-06ae-405e-95f4-6a21c3b5a100
Faulting package full name: Microsoft.Limitless_1.8.14.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
25 mins from landing, too. I’m so disappointed. It ruins the whole thing. Sim just updated to SU6.
Did you do the second part, (which was to be done at the same time) to rename the exe.xml file?
to be fair, i looked through that file, and everything is in order. why would deleting it/renaming it make a difference, other than the Fenix bootstrapper not loading and therefore not loading the fenix app? or the nool vdgs app?
Since it prevents addon from connecting via SimConnect.
Increasing Swapfiles is also worth a try.
Well, I can tell you that TenPatrol is probably one of the best MSFS troubleshooters in the world.
I suspect he has a very good reason for recommending it.
It may not work, tracking down the 0xc0000005 error is quite hard as it is a very generic code.
For the time it takes, I would recommend trying it and see if it helps, and letting him know.
As I mentioned he is quite good at this.
Every program/add-on that starts together with MSFS can have an impact on how it runs. That’s why every program listed in the exe.xml needs to be excluded from the test.
So I have to repeat and stress this: rename the exe.xml file so that none of those programs are launched together with MSFS.
Also, if you have any programs that interact with MSFS but you normally start them manually, I would not recommend running them during the test either. The whole point is to test MSFS without those programs running.
That also means do not test with the Fenix.
I’d recommend testing with one of the default aircraft instead, for example the A330. I’ve been flying it quite a lot recently and I haven’t had a single CTD with it.
BTW @TheSevenflyer thank you for the kind words. I really appreciate it.
Not running the Fenix add-on is not an option for me, as I use this add-on exclusively 99.8% of the time. If Asobo screwed something up with SU6 that is now going to regularly cause this very crash, then the sim has become a paperweight occupying hard disk space until it’s fixed.
Everything was fine until SU6.
I will, however, still try deleting the exe.xml, and starting the base minimum manually; which is easy because I run a very clean sim regardless with only the add-ons I need for any particular flight that day.
I also have, in the meantime, cleared the dat files in scenery indexes, and deleted wasm files in the wasm folder…just for ■■■■■ and giggles.
I also fixed an issue I didn’t even know I had with the rolling cache file directory pointing to an SSD which I’ve thus far removed, and all attempts to set a new directory and rollin cache file size failed. Crazy how they can’t even get that right.
I’m a bit ■■■■■■ off due to this ctd, so it may be a while before I try…maybe Sunday… regardless, I’ll report back.
Not sure if this was mentioned before or if you have tried it already. Try this and see if it works:
- Delete the Rolling Cache in MSFS folder
- Delete the simconnect HTML in the main MSFS 2024 folder
- Delete the contents of the WASM folder in MSFS folder
- Delete the contents of the Scenery Index folder in MSFS foler
- Delete Nvidia cache (maybe use a cache deleting program).
- Restart the Sim without the old community folder and start a flight.
- Exit the Sim and copy paste your old community folders back in the Sim.
Hope this resolves it…
I had the same problem and spent the whole day trying to solve it… I completely reset MSFS 24 to vanilla and tested it without any background programs. Before that, I did a clean driver installation with DDU. Turning photogrammetry off helped temporarily. Later, the crashes started again. I then realized that it always happens in the same region around Edds, regardless of whether third-party add-ons are installed or not. No crashes in Greece, Brazil, or Italy…
Since I always had crashes with the “s_ok error” in version 5.1, and only a complete reinstall helped, I decided to go down that road again. My suspicion is that there have been problems with the terrain mask in some regions since version 6.0. At least it’s not due to third-party add-ons… and yes, I’ve been able to rule them all out.
That makes a lot of sense! Both times in SU6 I got CTD was flying over or near EDDS! One time flying from EDDF to LSZH and one time flying back from LIMC to EDDF taking the eastern route. Have you been able to resolve the issue? Would it automatically happen if we start a flight at EDDS (is it reproduceable)? and can it be filed as an Error Bug here?
Yes, it must have something to do with that. Most of the crashes occurred about 1 NM northwest of EDDS. But unfortunately, not just there… I’ll continue testing tomorrow.
I can confirm that; the CTDs always happen near EDDS—it’s my “home airport” :-).
I have tried the same flight twice, which both led to CTD. The flights where EDNY to EDFM and guess what? The crashes appeared after a good while and with EDDS in clear sight just a bit south of it!
Hmm.. I was on my way from LEPA to EDDF when the crash occured about 20 mins from landing..was in descent. Will have to check if that’s near EDDS.
You may be on to something, possibly… here was my route. I must have been around NELLI when the crash happened.
Should make a new threat in Bug Reports! @MillionJeans98
