ISSUE DESCRIPTION
CTD (Crash to Desktop) with Microsoft .NET error that occurs on arrival into BIKF, Iceland, passing the waypoints ELROS and UMTAL (~50nm from the airport) at the altitude ~11000-12000ft.
The crash only occurs during the translatlantic crossing, if I take off elsewhere from Iceland and make the approach to the airport, everything is fine. Crash occurs independent whether BIKF is vanilla or payware airport or whether photogrammetry is used or not.
FREQUENCY OF ISSUE
CTD every time plane is approaching the airport, from different arrival directions.
REPRODUCTION STEPS
Please list clear steps you took in order to help our test team reproduce the same issue:
-
Start transatlantic crossing, fly for 3 hours
-
Initiate descent into BIKF using different arrival routes
-
The sim will CTD when plane is approaching waypoints ELROS or UMTAL
[Fault buckets]
Two fault buckets, first empty ID, type 0, then Fault bucket 2255405186427640856, type 4
[PC Only] Are you using Developer Mode or have you made any changes to it?
NO
[PC, MSFS 2020 Only] Are you using DX11 or DX12?
DX11
[PC Only] What GPU (Graphics Card) do you use?
NVIDIA 5090
[PC Only] What other relevant PC specs can you share?
Ryzen 9 9950x3d
@HursSokira, I’ll see if I can recreate this on my end. In the meantime, if you check the Event Viewer “administrative events” section for the time when your CTD occurred, see if any other events appear for the same time. This may provide an additional clue as to the nature of the CTD.
Look at this, from Auguust 2020, just after the MSFS release date: Sim crashes when loading in to BIKF (Keflavik)
It’s hard to believe, but it could be that they have reinstated their error.
It wouldn’t be the first time.
There are no warnings, but there is an MSFS Application Error right before the Windows Error at 1:05:51.
Related question: which version of .NET environment should I be running?
Several months ago, on a different PC, I had CTDs on approach being induced by a scenery add-on that installed an outdated .NET version which was creating issues. Deleting this .NET fixed it.
Just finished a transatlantic flight from CYYT to BIKF, and made it all the way there with no CTDs. So here are some things to check, @HursSokira.
- I have never flown in this region before, so I don’t have any World Updates for this area applied. Do you happen to have World Update V: Nordics installed? If so, it’s possible some element in this update is causing the CTD. For example I’m getting a CTD that is caused by POIs from World Update XII that worked perfectly during the beta. If you have the Nordics WU installed, search for it in your content manager, and then you can try uninstalling just the “point of interest” using the button shown below (obviously type “nordics” in the search for “installed” items) and then see if the CTD still happens. If it does, next try uninstalling the entire WU package, and see if that makes a difference.
-
Another possibilty to consider: Have you tried and succesfully completed other transatlantic flights of the same length but to a different destination? Is it possible that your CTD has nothing to do with BIKF in this case, but everything to do with the fact that you always reach these waypoints after about 3 hours of flying. This seems to be confirmed by the fact that if you start in BIKF it works fine. What if you take off from BIKF fly the reverse of your transatlantic flight? Have you successfully completed that flight? You don’t mention it above.
-
I’m also curious if you make the same atlantic crossing in the same direction but from a totally different start and end point. Does the CTD maybe occur after 3 hours across the atlantic in the southern hemisphere?
Just a couple of ideas to test, along with the checking the event viewer as shown in my post above. Good luck, and hopefully you can figure out a more precise cause for the CTD.
OK, thank you for suggestions, I do have both Nordics Updates V and XV installed. I will test and report back. Will try to cross from CYQX to LPLA.
Should I also update the .NET, or currently keep it as it is (ver. 8)?
So, spawning in the air approximately 200nm from BIKF and performing the same arrival procedure: everything is fine, no CTD.
Is this some kind of resource leak issue, where the problem manifests itself when the flight is longer that 1.5-2 hours? MSFS2020 is over 5 years old by now, why these problems still persist?!?
@HursSokira, during the beta, in v1.39.8.0, there was in issue for me where a slow memory leak would lead to all VRAM being exhausted about 90 minutes into a flight, leading to a CTD. I could increase the available flight time by drastically increasing the size of my paging file, but that only meant the CTD would happen later in the flight.
This specific issue was fixed in 1.39.9.0, but perhaps there is a more obscure instance of the same type of error that is contributing to your CTD. This is where you also need to check your event viewer “administrative events” section (from my earlier post above) to see if there are any other indicators of problems that happen at the same time as the CTD.
I don’t think a .NET update is necessary. The fewer things you change the better. If the CTD doesn’t happen with Nordics Update Points of Interest removed, then you have your most likely cause there, and the devs will know where to focus their attention when they have time to investigate the code.
I just finished almost 4-hour flight from CYQX to LPLA (with an extra hold thrown in) with no CTD, so it is not the memory leak. Did not change anything, just went the Southern route instead of Northern one.
And as I mentioned before, spawning in the air ~200nm away and doing arrival into BIKF went fine as well, so it is not the scenery either.
Just mind-boggling that such complex piece of software has zero error-tracking tools.
1 Like
@HursSokira, i just noticed your event viewer screenshot above. When the CTD occurs, do you always see the two Windows Error notifications at the same time? If so, I’d be curious what the details for both of these errors are.
Also after a CTD, click here to see if there are other alerts that occur around that same time.
Those Windows errors are related to .NET crashes, I run the FSUIPC and ACARS programs alongside the MSFS, so they throw errors when stop receiving data from MSFS.
I haven’t had CTDs flying in the other locations under the same configurations. The error might me related to the airspace around BIKF.
1 Like
