oh I have been banned for just mentioning it for 3 days, so that is what we are talking about, o.k.
no, I never used things like this and I do not want to use it either.
so, to catch you up where we are:
deactivating bing maps was my golden last resort avoiding the CTD’s, just to summarize. I had my CTD’s with addons deactivated, different aircraft, different regions.
what else could it be when you are flying high and fast than the internet connection/ loading of the autogen scenery? I was proven wrong - not for the first time since February.
so thank you for the advice but try to dig into our topic and have a glance on what we did try out, what we discussed and what we shared - we did a hell of a job. several hours of research I could say… maybe some day someone of the creators/employed persons could also have an eye on that? kindly forward it if it is possible
Hi,
Yesterday I had three more CTDs with Fault offset: 0x000000000245b669.
Having asked before, why can nobody from MS/Asobo tell me what this fault code means?
Is it some kind of a secret which MS does not divulge? Would it point to something wrong their end?
I am getting the feeling that they just let us run in circles here while they laugh at us behind our backs.
yesterday was a “hot” day
had also two crashes with this code.
the game tries to access something it shouldn’t.
Asobo seems to deal with the updates and the 2024 version.
I think we are only a few persons having this kind of failure (or only a few persons can cathegorize their issues - to be honest with these failure characterstics and error code it is totally understandable) and that is why our issue is not important enough…
worked for me, 2,5 hours IFR - CTD yesterday, today fine + 0,5 hours VFR in the comanche, yesterday CTD, now fine
+1
it was reported to me (hype EC160), that using manual page file sizes could also trigger this access violation CTD, using managed mode and on C: is the best option
all these were brought to you by “EKRE” - he made e.g. the hungary VFR package - you can find it on flightsim.to
With the same setting and same addons airport, I could fly a 4hours flight HECA to EHAM and 2 hours ESSA to EPWA. But i tried 7 times fly out of EHAM, all flights got ctd 20-50 mins after departure. Well done Asobo!
Windows 11 CTD: uninstall update KB5033375 and disable windows update for 2 weeeks, every flight i made i got CTD after 20 minutes, now is working again.
no, you need exe.xml → change the view of the file browser so you can see the extensions. (I guess it is the file above your backed up “exe.xml before …” long file
but this is only a guess, I do not see the extension.
secondly, backup the original exe.xml (this will be your 3rd backup as I see…, try to keep organized here)
then delete all the codes inside exe.xml and insert the code block I was posting above
I can not tell you if the files are corrupt or what (I am not working in IT), but this change made my CTD’s disappear (for 3 flights in a row now). The sim did access things while in flight it shouldn’t. It has to do something with simconnect. That is all I can tell you.
+1 while in-game, deactivate and delete the rolling cache. just for future stuttering-free flights → I can see that you have set up 8GB rolling cache
This is my story.
Some day i want to fly with the simulator, and then error code (0xc0000005) show, and never again can fly anymore. trying uninstall somethings like logitech adds and reinstal the sim. work like 2 weeks, and again, some day i cant to fly showing the error code, im tired and mad for that.
I feel your pain.
but this seems to be another issue as we described here.
try to go through the official forum recommendation when this error appears and after that contact microsoft support.
we did gather here because we went through these steps and nobody could assist us.
@Super275327 if your Sim is still working stable (mine is - 4 flights conducted with no CTD, each over “hot spots”) you cold mark the “solution” because I feel that as our topic is highly ranked due to our activity people are throwing in more and more issues which are not related to our error.
and as Asobo/Microsoft was not very helpful here, we can thank each other, great job guys
+1 for Asobo/Microsoft → try to implement an error logging system or useful support colleagues for the FS2024 - it can be helpful and keeps the people buying your stuff!
