My guess is that the sim has really bad error handling. It would be great if the sim wouldn’t load mods that weren’t compatible, X-Plane manages to do that. Even some sort of logging would be beneficial, rather than the unhelpful Event Viewer messages which mean nothing.
1 Like
I found this solution on a forum, it works for me. If you have CTD since the last nvidia update, do not look for it comes from there, as said PaisleyThyme817 install the old version 457.51. For info I have a 2080 super
The problem is, so many things will cause crash to desktop in this game - real time traffic, mods, drivers, etc, etc. It’s just not written very well when the game comes up against an issue, say, instead of not loading a particular module - whether that is traffic, weather, scenery - it just crashes to desktop. TBH in 30 years of PC gaming I’ve never known an app like it.
2 Likes
Agree, exception handling could be improved - but not the first time I see something like this. Often error messages are not very well defined. Can happen with any application.
1 Like
True, although most apps don’t have this many problems. I’m not denying it’s a complicated app, but I think maybe Asobo underestimated its complexity.
Some sort of logging of the loading of modules would be a great help IMO.
1 Like
Your connexion is unstable, that’s why. You need to complain to your internet operator.
On my fiber at 200 Mbps, it takes about one hour.
Agree, it would also help the support team to identify the root cause - now it’s more of a guess. Certainly knowing the core sim is going to keep growing (+new mods and addons), the risk of an exception will increase.
Same here.
Old FSX code base is probably plain C. They didn’t have object-oriented code and exception handling back then, and writing good error handling was so cumbersome that almost nobody did a good job of it. Even with today’s OO languages and exception handling, it still takes a large amount of time to write good handlers that propogate and report meaningful, specific, issue information.
TLDR: You’re right. The error handling isn’t very good in this sim – but neither is it good in most software. More information can be found – anywhere there’s software that crashes!
1 Like
Logging kills performance, you can’t do that.
I’m only suggesting logging during the loading of modules, not necessarily during flight. However, if you can’t have logging then you need proper error handling, not just generating a 0xc0000005 error in Event Viewer, which is totally useless for narrowing down the fault.
I have no clue what this means, this event happened (after my ctd), Does this mean anything to anybody?
Log Name: Application
Source: Application Error
Date: 12/27/2020 9:04:48 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP-KP39CQR
Description:
Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x5fda32ba
Faulting module name: CoherentUIGT.dll, version: 0.0.0.0, time stamp: 0x5fc6aa59
Exception code: 0xc0000005
Fault offset: 0x000000000013f507
Faulting process id: 0x2bac
Faulting application start time: 0x01d6dc4e01008059
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.12.13.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.12.13.0_x64__8wekyb3d8bbwe\CoherentUIGT.dll
Report Id: 9e40427b-dd57-4a5d-9f75-9ad46680424c
Faulting package full name: Microsoft.FlightSimulator_1.12.13.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Event Xml:
1000
0
2
100
0
0x80000000000000
22025
Application
DESKTOP-KP39CQR
FlightSimulator.exe
0.0.0.0
5fda32ba
CoherentUIGT.dll
0.0.0.0
5fc6aa59
c0000005
000000000013f507
2bac
01d6dc4e01008059
C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.12.13.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.12.13.0_x64__8wekyb3d8bbwe\CoherentUIGT.dll
9e40427b-dd57-4a5d-9f75-9ad46680424c
Microsoft.FlightSimulator_1.12.13.0_x64__8wekyb3d8bbwe
App
there are some threads in the bugs & issues forum section regarding some of these CTDs, i’d recommend checking them out and/or posting there as well.
also, this might help some people: CTD but maybe sorted by Clearing Rolling cache
I get most of my CTD’s during stormy weather. A few random CTD’s.
Not sure if it’s linked to my favorite aircraft the Cessna Citation Longitude.
I’m also using some fix mods for the Cessna Citation Longitude and using a stream deck via sim connect.
My computer is high end.
GPU - RTX 2080 TI GAMING X TRIO
CPU - Ryzen 9 3900X
Memory - G.SKILL Trident Z Neo 2x16 32GB
Storage - Sabrent 2TB ROCKET NVMe PCIe M.2 x3
Mainboard - MSI MEG ACE
Windows 10
just flying in cruise from LOWI to EDDK, live weather all fine and suddenly CTD! what are the reasons for it??
1 Like
CoherentGT is the third-party HTML5 rendering engine that the sim uses for building and drawing the cockpit instruments. You can read more at this link (programmer knowledge needed):
https://coherent-labs.com/Documentation/cpp-gt/d4/dcd/workflow.html
What this error means – and that it is producing CTDs – is that you probably have a mod (like G1000, G3000, or other) or a custom livery (that uses panel.cfg) that is causing a problem. Empty your community folder and try again.
2 Likes
Just an update, flew the exact same flight and it crashed within 60 seconds of me saving my spot right before it crashed last time. So it’s definitely a repeatable crash. Even have video.
No suggestions have helped yet, not an nvidia card, increased my page file, community folder is empty, no rolling cache…
Based on the cannonball run contest sounds like a LOT of people are getting sim crashes. It’s likely an Asobo problem that needs to be fixed ASAP.
4 Likes
ditto
I did a clean reinstall before installing MSFS keeping documents and folders
Start fresh with a clean installation of Windows 10 (microsoft.com)
My PC is Dell Inspiron- no dedicated graphics card -no CTD-no peripherals
1 Like
Just to add a bit of technical information, in particular regarding Nvidia drivers.
After the last update I still did not suffer a single CDT (I had several before).
I have an i9-9900 (non k), 32 GB Ram, GTX 1660 Super and 460.79 Nvidia drivers.
Had one today.
Second in a week.
Reverb G2 HMD.