Hi guys, ive never had these issues before but now plagued by CTDs all the time...

One lot of CTDs was the latest Nvidia graphics driver which i fixed by reverting to and older version... but this keeps happening...as below... sometimes 30 mins into a flight..other times 10 mins...

All of my flights have been in VR...which usually causes zero issues...

Faulting application name: FlightSimulator.exe, version: 1.34.16.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.34.16.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000001e4b7a0
Faulting process ID: 0x0x9E4
Faulting application start time: 0x0x1DA12D39BDE9E95
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report ID: f4f50211-da53-4b76-a51e-f317f44807d4
Faulting package full name: Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Ive done the scannow option and no corrupt files... im hoping i dont have to reinstall MSFS... such a pain...

Im actually lost now as to what to do... any ideas? If i have to uninstall and do it all again i guess that will be it eh!

Thanks guys

Back in the day, the sudden emergence of random CTDs could be a sign that a once-stable overclock had become unstable, perhaps through deterioration over time of the components under higher heat / voltage. Or, sometimes, that a piece of kit failed even though not overclocked (I’ve had this with RAM and graphics card).

So … do you have the option to run your PC at more conservative hardware settings and see if that makes a difference? And/or swap out components?

0xc0000005 is the RAM, probably an unstable XMP profile. Try to remove XMP from the BIOS and see if it's reproducible.

You could also try to reproduce it with OCCT which is a fast tool to detect instabilities: https://www.ocbase.com/ 

Does this happen with all addons removed/disabled?  I've seen several cases where an addon gets buggered by an update.

Obviously you need to see if this happens without any overclocks and check that your temperatures are OK - an internal clean and removal of dust and debris can help.

REX Accuseason and FSLTL maybe causing issues for some.  It seems that MSFS is breaching some new internal object limit.  GAIST reproduces a similar problem.

I've also been getting simconnect issues with Littlenavmap faulting and think it is related to the object limit in some way so make sure that nothing other than msfs is running in the background.

Hopefully SU14 will fix a few more bugs shortly.

Edited November 9, 20232 yr by cianpars

Am getting the same - 

Faulting application name: FlightSimulator.exe, version: 1.34.16.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.34.16.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000002591106
Faulting process id: 0x0x51B4
Faulting application start time: 0x0x1DA12E167D5AE4B
Faulting application path: D:\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: D:\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Report Id: c7e5eba0-f7d5-445e-9131-51ab014f059f
Faulting package full name: 
Faulting package-relative application ID: 
 

Hmm. I wonder if it's something they sneaked into WU15?

Hi,

I had yesterday a CTD when I went, for the first time, to begin a flight in Leknes Airport (ENLK). I didn't have a CTD for ages, and I have no idea what could have caused it. So I disabled a few add-ons (some Norwegian scenarios, basically), and the second time that I tried all worked fine!

Regards.

 

 

I also had a lot of CTD recently

I haven't got WU15. Never really had any CTD's until recently. Not much in my Community folder, no overclocking etc. I had one this morning, tried again and had a successful hour and a half flight and then had another CTD when I went to load the next flight. Seems pretty random. 

Lots of users with Exception code: 0xc0000005 CTD's over at the official forum. Seems to be common for some after SU13. I'm going to be playing something else for a while I think. 

12 minutes ago, St Mawgan said:

Lots of users with Exception code: 0xc0000005 CTD's over at the official forum. Seems to be common for some after SU13. I'm going to be playing something else for a while I think. 

Are you using DX12 or DX11? If you are using DX12, try DX11 for the next 5 flights or so. Because, in my opinion, CTD have started to get worse with SU13 release, using DX12 AND the driver versions after 531.29. 535.98 is still pretty stable to me with DX12, but NOT CTD free. 
I´m on LOD 200 for Terrain and Objects and when flying VR on  LODs 175 for both. In VR I get 45 - 60 FPS regardless the scenario within the FenixA320 at DLSS Quality with 37PPD in the Varjo Aero. 

System specs

Edition Windows 11 Home
Version 22H2
Installed on 20221014
OS Build 22621.2506
Windows Feature Experience Pack 1000.22677.1000.0
HAGS ON

Nvidia Driver Latest Stable for me 535.98

AMD Ryzen 9 7900X3D | PBO 2 + 150MhZ | CurvedOptimized NEG 28 | SMT ON
Mainboard ASUS Crosshair X670E Hero
2x16 GB RAM 6000 Mhz Corsair Vengeance
RTX 4090 24GB Watercooled
32" Samsung UHD Monitor @4k
Custom Water Cooling | 2x360MM
Varjo Aero | Varjo Base

Main MSFS Addons

Fenix A320
FBW Experimental Mode
FSCrew
GSX PRO
OPENXR Toolkit
FSLTL
AIGAIM | Latest Version
AIGTC | Latest Version
PSXT + RealLiveTraffic (not in Use due CTD)
+175 Addon Airports | Incl. 5 CityPacks

Edited November 9, 20232 yr by mpo910

DX12. I'll try DX11 although I much, much prefer DX12. I've also rolled back to 537.34 so lets see if that helps first as it was perfect for me before. 

From everything I’ve read this is not related to graphics. Seems to be a server side issue related to bing data 

16 minutes ago, St Mawgan said:

DX12. I'll try DX11 although I much, much prefer DX12. I've also rolled back to 537.34 so lets see if that helps first as it was perfect for me before. 

I have tried DX11 for weeks (20 flights upwards), and never had a single CTD just to test between them both. In my case, DX12 is the issue for my CTDs. The most stable Nvidia Driver for me was 531.29. And 535.98 the second best. 

I also prefer DX12 due the smoother experience and less stutters at heavy scenarios, compared to DX11. With DX11 I get up to 70 FPS in VR, with heavy addons and high to Ultra settings, where DX12 gives me 45 to 50 but smoother experience overall. 

The suggested test, using DX11, is only to check, if you are also suffering from DX12 BETA instability. The High VRAM usage with DX12 is intended, please do not think this is unwandted and faulty! But my CTD with exact the exception code you mentioned, is only occuring with DX12 in my case. 

Also, DX12 has the ground tile texture flipping issue, with BING texture groundtiles bleeding through at airports etc. Within my test with DX11 I never had that issue anymore. 
 

Now I´m on DX12 again and with 535.98 Driver I have managed to be CTD free for at least 5 flights. I think, assumption because I have not documentated this, that every 10th flight I get the error you´ve posted. That´s ok for me at the moment
 

Marcus

 

25 minutes ago, St Mawgan said:

rolled back to 537.34 so lets see

I suggest to roll further back and test with the drivers I have mentioned. In my case it helped to drastically reduce CTD (almost every second flight with newer nvidia drivers and DX12)