Changing view with same command for “onboard and outboard view” might cause CTD
1 Like
well I never thought of changing the view as the cause, I thought of it as a trigger.
80% of my CTD’s was while changing the camera view inside or outside the cockpit, no matter. sometimes just zooming in inside the cockpit.
but there are around 20% where the flight just ended suddenly, I was not at my PC, so there was no change of views..
these are the really annoying ones: flew 2+ hours from Salzburg to Dublin, unload/load, flew back to Klagenfurt with the PMDG 737, on the way back over Bavaria, after 1:44 into this leg, CTD without panning, left the PC for a coffee and - I was out
in total, after more than 4,5 hours of flight, more than 5 hours of the simulator running …
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00000000025f84a9
ID des fehlerhaften Prozesses: 0x0x2FD8
Startzeit der fehlerhaften Anwendung: 0x0x1DA114F6AD4ADBC
Getting a few MSFS CTD’s. SU13 seemed fine, but recently I’ve updated the NVidia drivers to the latest 546.01 (there have been a few driver updates recently) and I have had quite a few CTD’s. Random ones, on sim launch and 2 or 3 after a couple of hours in & on final. The latest one tonight into EHAM(FlyTampa) which I’ve not had any issues with. On a 2nd flight (the first one was ok). Very annoying as I’d not had any CTD’s in months before this.
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: 0x000000000153f350
Faulting process id: 0x0x57B0
Faulting application start time: 0x0x1DA119C6A4DDBC2
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: e72dd235-2c41-4dd8-9579-945a9a739fde
Faulting package full name: Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Yes may be better to use one of the older stable Drivers 528.49 - 531.18
1 Like
Jumping in this topic as well to add to the masses experiencing this issue. I’ve had 9 CTD since last night all with the same exception code, 0xc0000005. I am unable to complete a flight at this point. After combing through this thread I’ve tried a bunch of different things with no success:
-Running in safe mode
-DX11 vs DX12, both with low and ultra settings
-Removing my ram xmp setting
-Reverting Nvidia driver
-Live traffic vs no traffic. Live wx vs preset wx
If anyone is curious: i712700k 32gb ram 3070
Hopefully this issue gets some traction, the last time I was able to fly consistently without any CTD was 10/21/23
I’ve got a number of crashes taking place, I have the map zooming issue and if I get past that I find approx 1hour in to any flight I get a CTD with exception code 0x0000005. Real shame trhe sim has been rock solid for me and I stream MSFS which is unthinkable at the moment with the stability problems
I’ve had numerous crashes with this same exception code since the beginning of October. I’ve tried a number of things including reinstalling the sim to no avail. I guess the next step is a full system reinstall but I have a feeling that it won’t help.
I feel like something happened in the most recent update that really doesn’t sit well with our PC’s causing the crash, hopefully in SU14 this will be completely fixed
1 Like
Often too many variables tbh. But.
- SU13 (28 Sept.) I didn’t have any CTD’s post release with some fairly heavy sim usage.
- Three (17, 26, 31 Oct) Nvidia GRD updates were released in under a month (others have reported seeing some instability with most recent ones 545.x/546.x)
- There have been several Windows (Win11 in my case) updates recently too.
I have run Windows System File Checker tool and no windows violations found so I’m currently leaning towards #2 in my case. I have not rolled the driver back yet though.
I had been very stable (CTD free) for months on NVidia drivers prior to this, using 537.x (and previous ones) before last month’s GRD updates.
Did you try removing your rolling cache? I’d try turning it off completely instead of just deleting it first?
CTD’s of this “heavy” (i.e. since months I am looking for the cause) random kind started for me with SU12 - february~march 2023, rolling back nvidia drivers brought stability for a while but CTD’s started for me again…
I can not believe that a Nvidia driver “lets” the sim work sometimes without problems, other times for 5 hours without problems, and sometimes it lets the sim crash after departure … it makes no sense …
1 Like
I’ve voted. Same 0xc0000005 error here seemingly completely at random.
Also reporting back that I had another 0x00005 CTD after roughly 1h of flying.
Maybe turning of traffic did bring some improvement for me but still rather unstable.
I guess the reasons for those CTD‘s are not one single specific issue as they are so diverse…
Please everybody vote, so this is being looked at
oh, today I had a new one:
finished a 2+ hours flight again without any problems, back to the menus, loaded with the Guimbal into a small regional airport and after loading into the cockpit, this CTD here:
Ausnahmecode: 0xc0000005
Fehleroffset: 0x000000000184df88
ID des fehlerhaften Prozesses: 0x0x1888
Just had my first flight without a CTD in over a week. Was on VATSIM and was EPIC - miss it sooo much. I’d uninstalled Rex weather force - no idea if this is a perm fix but will keep feeding back. The map zoom in/out CTD reported in another thread is still present - and that thread talks about the weather a lot - starting to wonder if the weather is to blame for all these random CTD’s
Rolled back my (RTX3090) NVidia drivers to 537.58 from 546.01 and two flawless flights and sim just runs smoother. Definitely some issues with the 545.x and 546.x drivers. Will continue to test but so far no CTD. 
I’ve been using 537.13 with no issues.
1 Like
I’m hoping MSobo re-releases SU12 labeled as SU14. I went months without a CTD prior to SU13 and now it’s every other flight with no apparent pattern.
1 Like
thx for reminding me about that, I just checked my current settings and already had it completely turned off.
1 Like