Hi all, in SU10 even in safe mode, if I adjust anything in the sim menus, for example traffic or now even changed graphics death of field from High to off and clicked save I get a ctd

6 minutes ago, Bill A said:

Hi all, in SU10 even in safe mode, if I adjust anything in the sim menus, for example traffic or now even changed graphics death of field from High to off and clicked save I get a ctd

Clearly you have system issues. Over clocking or failing components most probable cause IMHO

5 minutes ago, btacon said:

Clearly you have system issues. Over clocking or failing components most probable cause IMHO

Or maybe he doesn’t? There is a known problem causing CTD’s.

Are you running DX12? Is it the ‘your graphics device has encountered a problem’ error? 

I am experiencing a CTD in about half my flights - empty Community/DX12 and all forms of DLSS or TAA. It does seem to possibly related to Overclocking.  My i7-9700K is rock solid at 4.9 GHz with a slightly lowered processor voltage to aid in cooling.  I can run 3DMark (any variety for hours at a time)  or any other benchmark with no problems.  But even backing the OC off to 4.5 seems to lead to MSFS CTD.  Running at stock speed I seldom have a CTD.  

Having said all that - the same 4.9 OC and MSFS worked perfectly for many hours a day before SU10. 

And the CTD I get now with DX12 frequently kills Windows.  MSFS locks up with the sending MS a report message and I loose the mouse cursor and keyboard control.  I have to use ALT+F4 to get out of MSFS and sometimes I need to do a Windows restart to get anything to work again.  Never had that severe a problem prior to SU10. 

 

 

I removed everything from the community folder and started to put things back little by little and so far all seems good. 

good luck to you sir 

1 hour ago, TacomaSailor said:

I am experiencing a CTD in about half my flights - empty Community/DX12 and all forms of DLSS or TAA. It does seem to possibly related to Overclocking.  My i7-9700K is rock solid at 4.9 GHz with a slightly lowered processor voltage to aid in cooling.  I can run 3DMark (any variety for hours at a time)  or any other benchmark with no problems.  But even backing the OC off to 4.5 seems to lead to MSFS CTD.  Running at stock speed I seldom have a CTD.  

Having said all that - the same 4.9 OC and MSFS worked perfectly for many hours a day before SU10. 

And the CTD I get now with DX12 frequently kills Windows.  MSFS locks up with the sending MS a report message and I loose the mouse cursor and keyboard control.  I have to use ALT+F4 to get out of MSFS and sometimes I need to do a Windows restart to get anything to work again.  Never had that severe a problem prior to SU10. 

 

 

Experiencing the same though I have no Overclocking on processor or graphics card. I also get the CTDs and Windows failure on DX11 and DX12.

I have been experiencing this since SU10.  System was rock solid before. 

I used DDU to remove my Nvidia drivers and reinstalled using NVClean install....so far so good, (I installed the new Nvidia stereo drivers), but I have only tested two flights and flown less than 2hours. Usually I get the CTDs and lockups within 10 minutes of starting my flight.

PS. I fly exclusively in VR. 

6 minutes ago, Romeo_Tango said:

Experiencing the same though I have no Overclocking on processor or graphics card. I also get the CTDs and Windows failure on DX11 and DX12.

I have been experiencing this since SU10.  System was rock solid before. 

I used DDU to remove my Nvidia drivers and reinstalled using NVClean install....so far so good, (I installed the new Nvidia stereo drivers), but I have only tested two flights and flown less than 2hours. Usually I get the CTDs and lockups within 10 minutes of starting my flight.

PS. I fly exclusively in VR. 

this really look like a system issue. Unless it's specific to VR. Rock solid on my side. 

Edited September 25, 20223 yr by fogboundturtle

3 minutes ago, fogboundturtle said:

this really look like a system issue. Unless it's specific to VR. Rock solid on my side. 

Perhaps you are correct...Strange, the problem started right as I installed SU10. Also strange so many are now having similar CTDs, right after installing SU10.

Keeping my fingers crossed that the driver update that I did solves the problem. I also intend to search for a BIOS update for my motherboard.

1 minute ago, Romeo_Tango said:

Perhaps you are correct...Strange, the problem started right as I installed SU10. Also strange so many are now having similar CTDs, right after installing SU10.

Keeping my fingers crossed that the driver update that I did solves the problem. I also intend to search for a BIOS update for my motherboard.

Many people are having CTD's because they didn't update mods that need to be updated for SU10. Don't know if that is your case. Always try with an empty community folder first so you can exclude that.