Almost certainly a hardware issue somewhere then. Run memtest86 and check for any memory errors. Sometimes just because it doesn’t happen in any other program doesn’t mean one picky program will 'find" the problem. Make sure nothing is overclocked and as someone above said, reset mobo to default settings.
Edit: Now I see you think it may be an addon. That’s quite possible. I had Zinertek (or however it’s spelled) enhanced runways causing mine. Since I removed it I don’t think I’ve had a single freeze/crash and that’s been since.. early summer.
Tried IFR flight this morning, EGNX to LEMD, a reverse of yesterdays flight, so this time it was the PMDG 737-800, the only addition in my community folder from yesterdays content and Simlink running, in the climb to 360 at around 270 wham!, CTD.
So the only two differences between yesterday and today are PMDG and Simlink.
I have never heard of any issues with either and i have been a user of PMDG for years.
The only to find out is to rename the Community Folder (again) restart the sim so it generates a new folder, transfer the PMDG into that new folder and fly again.
Update 3. Late last night, generated new Community folder with just PMDG 737 and Liveries, restart Sim, Update done, loaded 737 departing from Gatwick, no flightplan loaded, took off from runway on a random direction, cruised at 280 for around a good hour at night, no CTD!!.
So, I am baffled, what I can add is this, I am pretty sure that all my CTD’s have been when the flightplan from Simbrief has been loaded via the FMC on both Boeings and Airbus.
The 787-9 flight I did with no CTD the plan was entered manually.
So todays plan is to replicate the 737-800 flight that crashed and enter the FLP manually, and see what happens.
Well I replicated the EGNX to LEMD apart from loading the FLP compiled by Simbrief via the FMC, entered the FLP manually, same weights, etc, only the weather and winds were different.
SMOOTH AS SILK.
Now, is this pointing to a Simbrief issue?, I really do not know, never heard of there being an issue before.
Its always the same exception code 0x0000005, which is a generic code that can apply to many different errors, and the faulting module is always Microsoft Flight Simulator.
Since SU13 we can read on the forum many post with different titles about CTD and for me the origin of these CTD are the same “SU13”. I am also a victim of this update. Before SU13 very few CTD and after many. In my case CTD comes always after quick change of view in the cockpit using hotkey, for example from front view to side view. By avoiding these quick change of view I have no more problem.
In reponse to hazzer111, it has been fustrating and baffling, however through renaming my Comm folder and adding addons back one at a time into the new Comm folder I hope achieve a solution.
JCC1953, a very good point about the views, if I recall, mine occurred after going from Cockpit to either a custom wing view or the default wing view, so perhaps this is an issue for Asobo to look into.
What I would like to see from the MSFS Support team is the data whereby they have actually diagnosed the causes of CTD’s, be it an addon, a piece of scenery, external module etc etc instead of the usual response ( Vanilla State), still waiting 3 days after sending all the data they asked for following a CTD with only PMDG 737-800 in the Comm folder, seems to me if its not crashing in the Vanilla State they do not want to know, and yes I get it, they are not responsible for 3rd party addons, but I will say this, I have flown PMDG since they came out and I have never ever had issues.
just interesting to read you guys about your experience with these random crashes.
if you read around the CTD’s topics, this is a certain type of freeze, I am having it also since SU13 (?) (february 2023, definately)
mostly while panning the view in/outside the cockpit. sound freezes, picture stops, 10-15 seconds, then crash to desktop
Handle SEH and 0xc0000005 exception code
no difference in planes, scenery, add-on, peripherals; these crashes occur totally random, mostly while flying high (FL150<) and I have my “typical” regions but could not stick it 100% to any hotspots.
mostly over non add-on regions. (Balkans (sometimes near Belgrad), west of Vienna, Klagenfurt area, Ljlubljana area, middle of Germany, etc)
Asobo seems to ignore these facts, although we try to list the error codes and look for help, offer our support
it would be interesting to see how many topics relate to the same bug - I could find at least three different topics, by digging deeper into the characteristics of the crash - it seems the same.
let us vote up all these topics, keep up the pace so that it can be resolved!