Repeated CTD at Linz

[MagyarMatt]

Tried 3 times today to fly from LHBP to EDDF with the routing below.

GILE2L GILEP DCT ZOLKU DCT ARSIN DCT SUBEN T161 ASPAT/N0451F240 T161 FAWUR FAWU2A

Each time the sim dropped out to desktop with no error message.

First flight FBW A320 development version.
Second flight FBW A320 latest development version.
Third flight FBW A320 latest stable version.

Have flown this aircraft out of LHBP many times with no problems until today.

Anyone else experiencing CTDs in the Linz area?

[Hester40MT]

Topic moved into Community Support > CTD Help

The Bug Reporting category is for reporting confirmed bugs using the provided template that can be replicated by others.

The Bug Reporting category is for default MSFS content with no addons.

[MichaMMA]

please check whether you crash each time at exact same location and also report the message from windows event log.

[MrRamba]

HHi everyone. Today I wanted to fly a short hop from LKTP to LOWS. Routing was almost directly above Linz.
I did 3 flights on the same Route.
First 2 flights were in the Fenix A320, third one in the Maddog MD82.
The Sim always crashed at the same spot.
When the sim crashed to desktop during the third flight, I was fast enough to make a screenshot from Navigraph. It crashed exactly at this position all 3 times.

[MrRamba]

Edit: All 3 flights were in cruise FL280.
For the third flight I got the following error:
Name der fehlerhaften Anwendung: FlightSimulator.exe, Version: 1.26.5.0, Zeitstempel: 0x00000000
Name des fehlerhaften Moduls: VCRUNTIME140.dll, Version: 14.31.31103.0, Zeitstempel: 0x006cb796
Ausnahmecode: 0xc0000005
Fehleroffset: 0x0000000000001626
ID des fehlerhaften Prozesses: 0x5aa4
Startzeit der fehlerhaften Anwendung: 0x01d8ad01f12d6057
Pfad der fehlerhaften Anwendung: S:\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Pfad des fehlerhaften Moduls: C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll
Berichtskennung: 86a48b00-9b4d-4387-9d05-4340c652547e
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

[MichaMMA]

@MrRamba

above Linz.

Hi… I tried this with the default C172 , but then I remember " I tried this already while ago"

Here a user reported the same and with the default airplane it was not reproducable for me.

Game randomly crashes mid flight

I get exactly the same, came to this thread looking for an answer to my problem. It happens everytime exactly in this position: [CTD-location] It happened four times on me, both in normal and safe mode. I normally have no CTDs at all.

( it is the exact same spot )

The ideas was about the G1000 , but we have also other topics around LOWL

One example , where a user describe what was helpfull is:

Reproducible CTD at LOWL?

Hello - is (was) the same for me. Flying over the area LOWL (Linz) + LOLW (Wels) > CTD LOWL = Airport of departure > CTD LOLW = Airport of departure > CTD BTW: LOWL is my “home base” > BIG PROBLEM The solution in my case was: removing all content from the Community folder deleting the rolling cache deleting all *.dat files in the SceneryIndexes folder and deleting the Content.xml file Next steps: Start MSFS without content in the Community folder A short flight from LOWL …

but there are others too.

[RuffelH84]

same here, i thougt “we love VFR” is causing this, but if you say, its happen in safe mode too

[saarflight]

Same for me…

Protokollname: Application
Quelle: Application Error
Datum: 15.12.2022 18:29:24
Ereignis-ID: 1000
Aufgabenkategorie:Anwendungsabsturzereignisse
Ebene: Fehler
Schlüsselwörter:
Benutzer: DESKTOP-K93ASHL\aschw
Computer: DESKTOP-K93ASHL
Beschreibung:
Name der fehlerhaften Anwendung: FlightSimulator.exe, Version: 1.29.30.0, Zeitstempel: 0x00000000
Name des fehlerhaften Moduls: VCRUNTIME140.dll, Version: 14.30.30704.0, Zeitstempel: 0x615a9215
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00000000000015f9
ID des fehlerhaften Prozesses: 0x0x53C0
Startzeit der fehlerhaften Anwendung: 0x0x1D910894623FB4C
Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.29.30.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Pfad des fehlerhaften Moduls: C:\Program Files\WindowsApps\Microsoft.VCLibs.140.00.UWPDesktop_14.0.30704.0_x64__8wekyb3d8bbwe\VCRUNTIME140.dll
Berichtskennung: 61a46b92-8979-43fb-8d67-8eac60524480
Vollständiger Name des fehlerhaften Pakets: Microsoft.FlightSimulator_1.29.30.0_x64__8wekyb3d8bbwe
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App
Ereignis-XML:



1000
0
2
100
0
0x8000000000000000

415


Application
DESKTOP-K93ASHL



FlightSimulator.exe
1.29.30.0
00000000
VCRUNTIME140.dll
14.30.30704.0
615a9215
c0000005
00000000000015f9
0x53c0
0x1d910894623fb4c
C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.29.30.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
C:\Program Files\WindowsApps\Microsoft.VCLibs.140.00.UWPDesktop_14.0.30704.0_x64__8wekyb3d8bbwe\VCRUNTIME140.dll
61a46b92-8979-43fb-8d67-8eac60524480
Microsoft.FlightSimulator_1.29.30.0_x64__8wekyb3d8bbwe
App

[slicker55]

Where would be without these forums and the wealth of experience within them?
Tonight, flying FBW A32NX (experimental) Austrian Livery OE-LZN, IFR, LOWW - EDDF, FL380 and yes, also experienced a sudden CTD whilst passing directly over LINZ.
Two further attempts using the same flight plan (Simbrief) both resulted in a CTD at the same location.
It was at this point that I decided to check online to see if anyone else had reported a similar issue and discovered this post.
Checked Win 10 (crash reports) which, contained the same info as those previously uploaded in this thread.
I started another flight, same route etc but at NEDIX, entered a manual waypoint into the MCDU and diverted to GIMBO to avoid passing directly over LINZ.
This diversion placed my aircraft 275 miles north of LINZ, before rejoining the original route at RENKA and completing the flight without any further issues.
It would appear there is some kind of issue with the scenery in the immediate vicinity of LINZ… Once again, grateful to this forum and in particular, this post for enabling me to finish this flight successfully.