Anyone getting CTDs with Fault offset: 0x00000000025cee09?

Hi,
Lately I am getting very RANDOM crashes with the same Fault offset : 0x00000000025cee09.
The CTDs with the Exception code 0xc0000005 occur whenever I use my addons, but not with vanilla MSFS.
I have tried to isolate the problem for months now, but to no avail. Many times I thought that I had isolated a suspicious addon and all was well for a few (short or long) flights, and then, bam! Another CTD.
Are any of you getting this Fault offset: 0x00000000025cee09 when you have a CTD?
Does anyone know what Fault offset 0x00000000025cee09 refers to?
Appreciate all the help I can get.
Thank you in advance!

0x00000000025cee09
same here, today twice, last days no CTD …

World / city updates?

If you have them, try uninstalling all world and city updates and see if that fixes it. I’ve just solved a CTD from a somehow bad world or city update and fixed it with this method.

Had this too yesterday, totally random my sim was pretty stable lately. Was flying the Fenix and roughly 10mins after takeoff suddenly stutter, pause 1/2 secs and then CTD.

Very annoying.

Hi @thecoronadian ,

Did you get a Fault offset 0x00000000025cee09 with your CTD report in the Event Viewer?
If so, were you flying near Austria or do you have any Austrian sceneries installed?

Yes (that’s how I found your post in the first place heh). I just got done trying the same flight today and it worked perfectly (both inbound and outbound).

Faulting application name: FlightSimulator.exe, version: 1.33.8.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.33.8.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000025cee09
Faulting process id: 0x0x3D24
Faulting application start time: 0x0x1D9E0EB9BD0EAA8
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.33.8.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.33.8.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: 92e011af-e258-4290-a34b-b5e2e9b52f6d
Faulting package full name: Microsoft.FlightSimulator_1.33.8.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Yes, I was flying LOWW-LDSP. It crashed somewhere over Wiener Neustadt. I do have Gaya LOWW as well as scenery for LOAN and LOXN from flightsim.to. Other stuff, as I said latest Fenix, plus GSX.

But I fly out of there many many times, I doubt it’s scenery related.

FUN fact: after long time I had a 0x00000000025cee09 now while departing from LOAN near to Lilienfeld … at approx FL 230, I have also every available austrian add-on… I also have Gaya LOWW … I was flying with the Hjet … I am having these crashes mostly at saturday, sunday evenings …

0x00000000025cee09
near Ljubljana, I can exactly send the location if anyone wants to try - I have no addon in this area, this is the odd thing:
46° 12’ 43,10" N 14° 41’ 6,99" E

I was flying an EC35 ~ 4500 Ft., departed in LJLJ (with an add-on indeed, but it was out of sight as the CTD happened)

crazy fps drops also while flying in this area - as I said very confusing as there are no potogrammetric cities, special buildings or addons

Hi,
Yesterday I had a CTD with the fault offset 0x00000000025cee09 with my Austrian sceneries deactivated, while flying in France near Lyon.
Maybe something else might cause or contribute to the CTD s.

servus!
maybe a clue? if it is possible check your GPU’s performance before before the crash.
I did have some overclocking active, now I am flying without. let us see.
my card did peak out before msfs did the CTD
!

Hi,
Might be worth a look. However I have not overclocked on my GPU (RTX 3090).

I had already again one CTD with no overclocking, so the search goes on

1 Like

armoury crate maybe installed? (asus)

Not here. I do not have any Asus components or software.

guys, I was plannig my flightplans via Little Navmap and I was loading it into the Fligtsim via the menus… Today due to a mistake I forgot to load my flightplan and had to put into the FMC manually and I could get around a CTD hot-spot, I could reproduce this issue … try this!

Update on my Armoury Crate and Ique programs relative to CTD. I have since deleted both programs and the CTD’s continue, and this is after the latest “trouble-plagued” update. I think I’ll go check to see if I have residual files there and hope to clean up anything related to that looping update yesterday.

So…the CTD’s continue so often that flying is too frustrating to do much flying other than to troubleshoot the issue. Lastly, a bit of a rant. I don’t like the idea that I have to delete a bunch of programs that might be possibly causing CTD’s rather than have MSFS identify and deal with any conflicts.

I’m thinking this CTD issue is related to something within their basic simulator and not any addon. Remember that I had cleared everything out of my community folder and still had CTD’s. I’m about ready to shelve MSFS if they can’t clean up their program so that I can actually complete a flight.

To clarify, you still getting these after SU13? Because they did say they fixed a bunch of crashes.

1 Like

I still got them, but with a new code 0x00000000025f84a9
type and location would be the same like before the update …
the method I described above solved this kind of CTD for now for me

Thanks Atkamen, I’ll give that a try. If I understand then - the problem is with the downloading of 3rd-party generated flight plans other than MSFS. If that’s so, do MSFS flight plans work or only FMS plans?

I’m skeptical because I’ve had a CTD right after starting the sim before I even selected the plane or loaded a flight plan.

I rechecked my errors, and they have varying Fault Offsets, but they are all the 0xc0000005 error codes.

To thecoronadian, Yes…even after yesterday’s troublesome update that looped around and was difficult to download, I still had CTD’s.

I was using Simbrief for my flight plans and loading them into the sim using simbrief downloader in addition to loading them into the aircraft’s FMS. Perhaps doing both things at once is related to the problem rather than just one or the other.

Thanks for your continuing efforts on this. I can’t fly any longer until I solve this problem.

Solved…My problem apparently anyway. I discovered that somehow my simulator was set to dx12 beta rather than dx11. I reset to dx11 and my CTD’s went away. Two complete flights without a CTD.