The crashes are not necessarily related to Aerosoft. Did you try downloading the fix from the link above on Aersoft’s page?
I am having CTDs near EDDB which I think is most likely a similar issue that was introduced in SU6 and continues in SU7.
I may be experiencing the same issue.
I have been getting recurrent CTDs in MSFS 2024 with Exception Code 0xc0000005, and the crashes seem to occur during relatively long flights rather than during loading or shortly after takeoff.
My current system:
- CPU: AMD Ryzen 5 7600
- RAM: 32 GB DDR5-6000 CL30
- GPU: MSI GeForce RTX 5070 Ti 16 GB
- Simulator: MSFS 2024
- Version: 1.8.16.0 (SU6.1)
- DirectX: DX12
The most recent crash occurred on a Concorde flight from LFPG to GOOY. The flight had been running for approximately 1 hour and 30 minutes when the simulator suddenly closed.
I was using:
- REX Atmos
- GSX
- IVAO / online traffic
Windows Event Viewer recorded:
Application: FlightSimulator2024.exe
Version: 1.8.16.0
Faulting module: FlightSimulator2024.exe
Exception code: 0xc0000005
Faulting offset: 0x3f51179
Interestingly, Windows does not identify nvlddmkm.sys, d3d12.dll or another NVIDIA/DirectX component as the faulting module. It identifies FlightSimulator2024.exe itself.
I have also experienced another serious CTD on a previous MMMX (Mexico City) to LEBL (Barcelona) long-haul flight, this time using the Aerosoft A340-600. The crash occurred during cruise, around FL370, while flying over the North Atlantic area, around CYYT. REX Atmos was active at the time.
That crash also produced an 0xc0000005 access violation. The crash report showed:
- GPU: RTX 5070 Ti
- DX12 enabled
- VRAM budget around 15.9 GB
- REX Atmos active
- Multiple WASM/add-on modules loaded
The fact that I have experienced similar CTDs on two different long-haul flights with two different aircraft makes me wonder whether there could be a broader MSFS-related issue, although I cannot rule out my third-party add-ons at this stage.
The approximately 1.5-hour timing of the latest crash also caught my attention, as other users appear to be reporting CTDs or other issues after long periods in cruise since SU6.
Has anyone else experienced 0xc0000005 with FlightSimulator2024.exe as the faulting module after 1–2 hours of cruise, particularly on long-haul flights?
I would also be interested to know whether anyone has found a reproducible workaround, particularly regarding Windows virtual memory/pagefile settings, since some users have reported a possible relationship between these CTDs and virtual memory.
At this point I am trying to determine whether this is:
- A general MSFS/SU6/SU6.1 issue
- A memory/pagefile-related problem
- A conflict involving one of my third-party add-ons
- An aircraft-specific issue
Has anyone experienced a similar pattern, particularly 0xc0000005 with FlightSimulator2024.exe as the faulting module after 1–2 hours of cruise?
I would be very interested to hear from other users who have experienced this on long-haul flights, especially if they were able to reproduce or resolve it.
Any information from Asobo/Microsoft regarding these long-cruise CTDs would also be appreciated.
Did you try a flight without Rex Atmos?
I’ve had two CTDs in MSFS 2024 SU6.1, both while flying the Fenix A320. Prior to SU6.1, I had never experienced a CTD in MSFS 2024.
The first was on 18 Sep, LEAS–EGKK, around 20 minutes into the flight over the Bay of Biscay. The second was tonight, EGLL–LIRF, around the French/Italian border.
Both Asobo crash reports show the same signature: FiberProc, SEH, 0xC0000005, with Purpose="QmidLoader". The raw MSFS call stack is also effectively identical in both reports.
Both were on build 1.8.16.0, but with different Fenix variants (CFM first time, IAE second time), different routes, and different NVIDIA driver versions.
Sounds like the same issue as me and some other users: Recurring CTD (0xc0000005) in "QmidLoader" during long cruise - #14 by ItzChickenYall
As a quick update, I have now flown the exact same route twice, LFPG–GOOY, without REX Atmos installed, and I haven’t experienced any CTDs or other issues on either flight.
This makes me suspect that REX Atmos could potentially be involved, although I obviously need to do more testing before drawing any conclusions.