glad to hear that!!!
honestly - I understand the AIRAC updates of navigraph if the sim is not following - I did not get the idea why you should infuse the AIRAC if the simulator updated it itself …
I did tell the hub to delete the AIRAC and after that I did deinstall the hub too.
I am not sure since which point the sim was running without CTD again, but my guess would be that deleting the AIRAC infusion was enough…
Moin Attila, same Error happened to me in Fenix IAE version, one time during Taxi, one Time during cruise. Also using navigraph in the EFB - Do you have new findings if it’s really connected to Navigraph?
Since I deleted the navigraph AIRAC infusion like described in the forums there I had no CTD. I already re-installed the PMS GTN 750. So - for me - this was this time the culprit..
I mean lots of people do not have this CTD so it has to be a combination of several addons. I do not have the Fenix for example.
My guess is - as there are so many addons interfering with the navigation system and change core data - that navigraph is one of those…
Or even the series of installation may be the key…
Exactly thats the reason, why we (Navigraph) recommend to use a extern database. Because its much, much more easier to debug/solve issue then with the stock bgl data where you need in nearly every case MS or Asobo.
But the addon devs are switching slowly, eccluding the companies which are part of MS/Asobo.
Cheers
Richard
2 Likes
After about 4 months of trying to figure out why MSFS would crash when dealing with navigraph apps and with MSFS itself, I finally solved the issue and it didn’t have anything to do with navigraph.
The short of it is that in the bios for my Asus Z790 Prime motherboard there was a setting to overclock the PC. Once I set it from Turbo mode to normal all of my issues went away and now MSFS is smoother and faster than ever.
3 Likes
been there, done that, did not help for me, glad it helped you!
but this is one of the first official CTD counter-actions if facing problems!
edging out your PC with a game that is on the edge with edgy performance is a hot mix.
1 Like
0x000000000245bb29
again, today, did no changes to the sim, I noticed that there was az AIRAC update meanwhile …
I will install again the navigraph AIRAC updates and observe if the CTD persists. (navigraph is now deinstalled since last CTD)
Hi,
After deactivating most of my addon sceneries with AddonLinker, especially the aerial sceneries in Austria, like LOXZ aerial, LOGP aerial, LOGK aerial etc., my CTD situation with Fault offset 0x000000000245bb29, has improved a lot. I did have a CTD yesterday though, when all my other addons (over 1500) were activated for test purposes.
Seems that Navigraph does not play any role with my setup.
After installing the Navigraph hub again and the actual Airac cycle (first line), plus the airacs for my planes (PMDG) I could accomplish a 2,5 hour flight.
I flew with the Mitsubishi on a route planned by simbrief and through ctd-sensible regions.
so back to normal again. my guess is that for me the exception code signals that the several navigation components are not in line and this is causing the crash. I could observe several times that the crash happened nearly on the geographical point where the SID ended I was flying.
updating all navigation components (navigraph, pns gtn750, ingame marketplace garmin stuff, airac cycles) solved the issues the last 3 times.
fortunately, addons are not an issue these days for me now, through the months of searching the CTD cause I had several occasions where I could test them
I had a 0x000000000245bb29
again right at the spot where my SID ended.
I will now deinstall again the AIRAC circle and look if something is changing
so I did deinstall everything again, still got the CTD’s (3-times in a row at the end of my SID)
reinstalled first navigraph hub, installed the airac again, the g1000 and g3000 in the hub.
deinstalled the working title marketplace addons in the game.
did not change my flightplan this time in littlenavmap (did this in the past and then - imported it in-game)
now - some of these changes was the solution…
I hope after the next startup of msfs it will still work because last time - without changing anything the - I got into the “CTD” state again..
maybe @NAVData - has some idea which installation sequence would be the best one when installing new airacs /and/or/ navigation systems /and/or/ having navigation issues
No sorry, there is no sequence what I know. The navdata packages will be loaded as all other packages in the community folder. There is only the re-ordering tool in the MSFS, where you can change the loading order of the packages. The installation process is independet and has nothing todo with the MSFS directly - at least with the knowledge what I have.
Cheers
Richard
2 Likes
so, my speculations were right, changing the settings only lasts for one stable msfs start
today I wanted to fly again - and Fehleroffset: 0x000000000245bb29, CTD again on my SID.
I am now lost here, would be great to know which setting is “clicking” back after one msfs startup in its initial phase and causing the navigation mess.
so, first try:
launched navigraph hub
deleted all caches
deleted content.xml (now this is the interesting part, either the navigraph hub or the sim generates the content.xml at launch. after deleting (before launching the sim) it was re-generated while the sim was launching - and my guess is that with the next sim launch I will have the CTD again)
did not launch littlenavmap
something did it. no CTD after this startup.
so, generating the content.xml and using this on a second startup seems to be my navigation-CTD culprit here - by the way content.xml only includes the startup sequence for navigraph, no other lines.
now, it happens that I still get sometimes 0x000000000245bb29
playing with the navigraph hub installer (installing de-installing) resolves my issues to 90%. two days ago I had a crash again, yet I made everything according to my description above.
so, I am near the solution (navigation, AIRAC - related) but still not there yet. seems also, that I am nearly the only one having these days this exception code, so, there is nearly no one to blame 
If it were just nav data related it should affect many more users than it does. Best guess is you have confirmation bias. You made some change, and you didn’t crash, therefore its that thing. But then you still got a crash later, so now it’s that in conjunction with something else.
That’s why I tend to advise users who consistently have CTD’s to remove all non-essential third party products until a stable baseline can be established. When I was doing this I flew without any addons for nearly 2 months, then added things back piecemeal until I found the culprit.
You can’t really have one or two flights and called it good unless you have a CTD every single flight.
As @hobanagerik answered. It´s very unlikely that it´s really a navdata issue due the amount of user which have installed this packages. CTDs are in most cases a combination of many things, beginning from hardware (overclocking), driver versions, software updates, firewall rules, virus or adblocker, programs on your system which uses different frameworks, … plus a possible combination of MSFS packages (addons, sceneries) which you have installed on your system.
Your report is very isolated because when there would really existing an issue, the forum here and also our forum would be flooded with reports but that´s not the case. Also, when you follow this thread here … no one, confirm your findings - not here, nor in our forum.
Not helpful for you, but that´s the hard-fact - sorry
Richard
1 Like
I have never ever stated, the navigraph is the culprit. if I did it somewhere, please let me know, I will delete it, it is totally not true, I did shoot to quick a couple of months ago where the CTD’s came more often.
anyhow, after months of trial&error one thing I have learned is that no one is to blame, because - well - not true. Asobo is to blame that they made such a software/game/simulator where a conflict of data causes the game to end instantly without any failure notice or by any chance to detect the cause.
but - what I can say by now is - that with my configuration, with my hundreds of add-ons I can reproduce following:
- installing the navigraph hub works fine.
- installing the actual AIRAC cycle works fine, at the first time starting the simulator after the installation. anyhow - at the second start I would get a CTD with the exception code 245bb29 - just exactly after 20 Minutes flight time - very creepy.
I would get a CTD again and again after each restart after 20 Minutes - deinstalling the AIRAC cycle, starting, restarting - so after that I would not get a CTD again. after the second start I would get a CTD again with the exception code 245bb29 - just exactly after 20 Minutes flight time - again.
this steps above are reproducable, I am now testing if/how the other elements of navigraph play a role and if deinstalling the navigraph AIRAC-cycle is generally working for me, or if I get the CTD after the second start here again …
Allright, I’m crossing the finger that you find what the issue on your system is and how you can solve it. Good luck!
Cheers
Richard