Before SU8, never had a single CTD. Never ever. After SU8, it’s a very frequent problem. RTX3090, 32gb RAM, I7 processor.
3 Likes
I’d like to address a couple of points:
if it was as bad as you claim, no one would be able to fly, but evry day many thou od users fly happily.
This is of absolutely no use to those of use who want to fly happily, but are not able to because of repeated crashes to desktop. blaming ‘victims’ does nothing. Consider yourself lucky you experience no issues: many do through no fault of their own and it’s ruining the experience. Perhaps add your system specs, any changes you have (or haven’t) made to address reliability, hardware or software that YOU believe may cause the issues. WE are not doing anything different or wrong. The Sim just crashes for us and not you.
I’ve now been through 2 major phases of crashing to desktop, on 2 completely different systems.
First time around, it was on my i9-10850K/RTX 3080/48GB RAM Win 10 system. I have only 2 add ins, the garmin 1000 update and a Bleriot aircraft. Otherwise vanilla. Those CTD’s started with SU6, and ended when an nvidia Graphics driver update cured them. I did not change hardware or game config at all, but did stop playing the sim a while.
Now, I have a system that is otherwise 100% stable in all games and demanding applications. I build, test and review hardware for a living, I will not tolerate faulty equipment. My equipment is not faulty.
This is an i7-12700K, MSI Z690 Carbon, 32Gb DDR5-6000MHz (Memtest 86 stress tested) RTX 3080Ti System, Win 11. It is stable under stress test loads and all other games and applications, with uptimes exceeding a week and no other errors. It now CTD’s after SU8 in FS2020.
I am running testing to try and isolate the issue.
I have: Updated drivers and rolled back to last known stable drivers, Disabled hardware GPU scheduling, Added registry GPU time out tweaks, Removed/renamed community folder, Removed/changed Rolling Cache, Reduced settings to Medium (CPU load now <60% on any core, GPU load ~70%. Temps all in good order and never an issue anyway (temps DO NOT and SHOULD not cause crashes, only throttling of components which is easy to check for. I am now running FS2020 in safe mode. Memory is fine, under 45% utlilised and no page file use. I’ve also tried the RTX 3080 (both 3080 and 3080Ti have been stable in phases in the past), running with Bing data off and photgrammetry on/off. I don’t use live weather or air traffic anyway.
CTD’s occur both in VR and using the screen.
I have removed all USB devices (as this can apparently cause crashes) except keyboard and mouse.
CTD’s remain with all of the above tested.
Common CTD Codes are:
Exception Code: c0000005
Fault Module Name: d3d11.dll
Which point to a GPU Driver issue but there are no driver crashes logged, which are what you’d normally see with GPU driver issues. 3 sets of Drivers all exhibit crashes. Next testing will involve taking the performance hit of DX12 to see if DX11 is at issue here. Although I’ve also found DX12 unstable on a test rig I run.
Unfortunately, since Asobo has had “resolve Crashes to desktop” as a primary bug fix item, and the crashes have in the past come and gone with game updates, I believe that these problems may be baked into the sim software and not within my capacity to resolve.
Asobo need to implement proper crash logging and fault reporting to understand what is going on here. I should not be dedicating days of my time to testing this issue on an otherwise rock solid system. If the game wasn’t so bloody good when it’s working, I wouldn’t be bothering.
18 Likes
Great post. I dont have nearly the technical knowledge needed to go through the rigorous testing of my system that seems to be required to resolve issues with the Sim and I have to be in the majority here. To have to troubleshoot many many different possibilities should not be needed to pinpoint an issue. I started in Sept with an Xbox Series X. We all know the challenges there so I decided to upgrade to a PC. Really didnt expect a similar level of CTDs and issues. And you are right, when it works, its amazing. Its exhausting though. I am not starting over with Xplane 11, but am absolutely going to give Xplane 12 a try when its available.
I totally understand that everyone’s setup can vary and issues can arise, but the lack of information to be able to solve/resolve the issues is to me, the biggest frustration.
5 Likes
the VCRuntime140 ?.. these also was often caused in an older topic by a driver or hardware issue ( and points so again to same cause ). The question is still, why you former have to limit the fps to 30 so that you can play the game. May be the update have an effect too and may be a mod ( free, or marketplace ) cause the issue, but we should just not forget that these limit in fps was prior necessary.
So, its realy hard to can say “its definitiv this or that”. What kind of PSU you own ? There are also other reasons possible (e.g. xmp mode) , but as said “hard to say”.
You honestly need to drop these lines: Inadequate PSU problems with RTX GPUs cause a hard system reset as they trip OCP/OVP. they’re indicated by a 'kernel 41 event in Windows event viewer. Likewise, XMP so long as it’s tested stable is stable. MSFS2020 is in no way unique or special in it’s demands on RAM it is not finding ‘faults’ in hardware that other software can’t touch.
I’m now 4 hours stable in normal (not safe) mode, Ultra settings back on, and the only substantial change I’ve made is I’m using a joypad, not my ageing flight stick with a slightly dodgy throttle. I suspect that the CTD’s may be a manifestation of FS2020’s dislike of USB connects/disconnects. I will keep testing and report back.
well,… we had cases where the system just not rebooted but users fixed the issues with a replacement of the PSU. But in general I agree, usually cause a real defective PSU results more in a reboot.
( note: these event 41 is more like a useless number, windows log this in many different cases too… e.g. HAGS related ).
Issues caused from connected devices are also common… most users had can fix it with a powered hub.
And nope… XMP is still in year 2022 overclocking… check the forum and you will notice that lots of users had issues related to xmp mode. It should work in most cases fine, but just not allways ( compatibility stuff , etc. ).
Well, I’m now 8 hours crash free at original settings, in VR and screen, and I have to put it down to my Flight Stick and USB disconnects. That’s the one thing that I’ve changed.
Until the next CTD…
1 Like
I have crashes now always around 2 hours of flight. Haven’t had them for a while before…
I get crashes (but to clarify) my CTD are with NO error messages, a black screen and the system is completely locked. I have to hold down power button to shut down system (CTl/ALT/DEL) for Task Manager does not work. Mine usually happens on longer flight and normally I have had ATC contact on approach (35+ NM out). Happens regardless oof anything in community folder or not. I am testing if running MSFS in Administrator mode makes any difference. I do NOT have answers only questions…
The PSU is an Apevia 800w. Is the potential issue a matter of capability, or an actual hardware malfunction? I have had no reboots etc.
I reinstalled Windows and am starting from scratch.
Then you have no crash to desktop, but a hardware crash.
Maybe your GPU is messed up. I had something similar in the past with my old GPU. I flashed the card to stock settings, flashed the GPU bios, which was messed up I guess. Then it worked fine.
Clean up BIOS/ drivers when you have hardware crashes
1 Like
i am not saying its the users fault, i say it is at the users end…meaning the whole
msfs environment, including windows etc etc
any way good luck in solving the issue.
this kinda proofs my point, there are sooo many variables, that makes it really hard to find
the culprit.
Not really. If is is crashing for me due to USB connects/disconnects (the only likely cause I can identify at the moment) that’s still a software fault: Flight Sim should be resilient enough to cope. They should be alive to the fact people with sims have complex peripheral set ups and they may be switched on or plugged in whilst the Sim is running.
Equally, given the huge number of variables and causes, there’s obviously more than one reason.
Step one would be for Asobo to implement proper crash logging and fault reporting, to help both themselves and users quickly identify and address the cause. I’m still not confident I have, because in the past I’ve had months of stable operation followed by months of not being able to fly for more than 30 minutes without CTD, and it’s been software updates that had fixed it.
2 Likes
Typical Miscrosoft stuff: we are talking about two MS products being not compatible between themselves… honnestly…
Personally I consider that when I paid for a 100$+ game, I can expect it to work no matter what as long as I have the minimum specs to run it. And I shouldn’t need to be a computer genius to do so. I don’t have the skills, nor the time, nor the will to run lenghty trouble shooting procedures.
Maybe they should pause the others developpments and focus on game stability improvements.
I never had that level of issues with any other games I played so far.
8 Likes
This ONLY happens with MSFS. All other applications run without this ever occurring. I appreciate your feedbaack comments but find it difficult to blame hardware when it ONLY happens with MSFS.
4 Likes
Yesterday, over 8 hours CTD free. (I’m trapped at home after a positive covid test, don’t judge me!)
Today, same set up: CTD within 5 minutes. HOWEVER: It was my game pad (which previously eliminated usb connect/ disconnect CTDs) for some reason connecting and disconnecting until the game froze and eventually CTD that did it. So I think I have my culprit: for now at least it’s USB connects/disconnects causing my issues.
I think it should be ok in point of capability, nvidia recommend min. 750W related to a 3070TI .
did you mean you do it “now” or the issue started after you installed windows from scratch ?
yeah then also a new powered usb hub will not help 
I have re-installed windows and MSFS2020. I also replaced my PSU with an RM750 to eliminate that as a potential issue.
Did a test flight in Safe Mode with only the keyboard for 15 minutes then CTD. The fault is a different one which appears to be related to Windows. Any ideas on how to troubleshoot?
Faulting application name: FlightSimulator.exe, version: 1.24.5.0, time stamp: 0x00000000
Faulting module name: ntdll.dll, version: 10.0.22000.527, time stamp: 0x931cda92
Exception code: 0xc0000409
Fault offset: 0x000000000009326f
Faulting process id: 0x1668
Faulting application start time: 0x01d8483ddfd47439
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.24.5.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: f971d6c4-d524-4713-acc8-6f5c3c7ed914
Faulting package full name: Microsoft.FlightSimulator_1.24.5.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App