Really struggling with CTDs

Discussion Hub General Discussion
21

BIOS up to date?

22

Two in the past day for me, just on approach. Two different airports, two different aircraft.

23

I did clean up my community folder this morning and it helped out so far. Make sure to do that. Maybe there is a mod causing this CTD problem. Cheers

24

I traced my CTD problem to one mod. After I removed it I have had no problems.

25

Well, I think I made a bit of progress. For some reason, I was only able to use the stable version of the FBW mod. I tried over 10 times in previous days to run the dev version and it would CTD before I could even get to the cockpit. For whatever reason, today I was able to run the dev version and had a troublefree flight from St. Johns to Gatwick, and it didnā€™t CTD until I was about 100ft above the runway before landing. I pasted the report from the Windows reliability log below. Maybe someone could interpret what it means better than I can. Iā€™m really hoping the only reason for the CTD was an older version of the Gatwick mod. Iā€™ll try it again with the latest version, and if it still crashes Iā€™ll go back to an empty Community folder. At least no Windows reboots for a while. I also updated Little NavMap in case it was something with the Simconnect API.

Source
FlightSimulator.exe

Summary
Stopped working

Date
ā€Ž6/ā€Ž21/ā€Ž2021 10:11 PM

Status
Report sent

Description
Faulting Application Path: C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe

Problem signature
Problem Event Name: APPCRASH
Application Name: FlightSimulator.exe
Application Version: 1.17.3.0
Application Timestamp: 00000000
Fault Module Name: FlightSimulator.exe
Fault Module Version: 1.17.3.0
Fault Module Timestamp: 00000000
Exception Code: c0000005
Exception Offset: 00000000012a657c
OS Version: 10.0.19043.2.0.0.768.101
Locale ID: 1033
Additional Information 1: c058
Additional Information 2: c0587f785a1acd437affb49880b3b270
Additional Information 3: ba22
Additional Information 4: ba2268cf0f783dc992afdff88c375fa5

Extra information about the problem
Bucket ID: fa4648efe7a773922e16abdb3e0f619e (2168109228752855454)

26

The rebooting on CTD means itā€™s almost certain hardware related. When coming close to airports, we all get frame drops, so this is the time when the game is pushing your hardware to the max. So you are going to need to figure out which piece of hardware is causing the issue. Itā€™s most likely going to be either your RAM or power supply although it could of course be something else.

So my suggestion is to download and run some stress testing software. Hereā€™s a link to an article on the subject with recommendations of different apps you can download to stress test different pieces of hardware like your RAM, CPU etc.

This will help you figure out which part of your system is unstable and causing your CTDā€™s.

1 Like
27

Hi,

A couple of things:

  1. Remove all 3rd party addons. Empty the Community folder (move out the mods and store them elsewhere).
  2. Use only default planes for a while
  3. The game does not like overclocking. It blue screens. I was getting this a lot and slowly dropped my clock speed until now I have zero issues
  4. Check your temps, check for lose RAM, other connectors etc

You want to use the game in a DEFAULT setting with NOTHING 3rd party for quite a while to establish a baseline.

This will remove the headache of wondering which addon might be causing trouble. If the base sim with stock planes and stock scenery is rock solid then you can take it from there.

If all else fails, back up your data and try a factory fresh windows resintall using the Media Creation Tool. This is a last resort option if everything else is exhausted.

Also - I have an ancient 13 year old computer with 1st gen i7 920 and I got the game running super smooth with no CTDs at all now. So there is hope! Good luck.

1 Like
28

Great infoā€¦thanks. For some oddball reason the windows crashes stopped a couple days ago. The only difference made was switching from the stable to the dev version of the FBW mode. I will definitely check out one of the stress tools if it starts happening again. Right now Iā€™m back to constant sim CTDs and they are showing the fault module as CoherentGTCore.dll

29

Clean out all fans and heatsinks, apply new thermal paste, check all cables, use a pencil eraser to lightly clean the contacts on gpu and ram and pay extra attention when reseating them, disable all autostart apps, defrag/optimise drives. If you still get reboots then chances are you have a hardware fault.

I once had a mobo that always had problems at stock speeds but always ran fine with a slight underclock regardless of cpu size, it turned out to be a single cracked contact that I spotted whilst removing the board and a dab with a soldering iron fixed it.

On the otherhand the sim is or at least was a bit finicky over some ram speeds, I had mine memtested and set at 3733 Mhz, MSFS was the only app or game that didnā€™t like it.

30

When I hear CTDā€™s consistently on approach, the first thing that comes to mind for me is your graphics settings. Have you tried setting your graphics to LOW just to see if there is a difference? If not, give that a try and see what happens. Iā€™m not saying that you will need to always run on low, but just try it for testing,

31

After a couple more days, I think the Windows crash/reboots went away. Since this started I updated Windows, my Nvidia driver and FBW dev version when they came available. I also removed a livery and only have the FBW mod in the Community folder. Keeping an eye on it. Thanks again for all the great feedback!

32

Is the power supply powerful enough? And is the system overclocked?

33

30 GB of Ram?

weirdā€¦

turn off Nvidea Freesync and undervolt your GPU.

34

850w power supply and no overclocking.I did turn off the XMP profile in BIOS, per another suggestion, so weā€™ll see if that helps. So far, Iā€™ve completed a couple flights without any CTDs, knock on wood

1 Like
35

Itā€™s 32gb of ram

1 Like
36

Thatā€™s not normal. Itā€™s possible that you have a hardware problem. This is the type of thing that happens if there is a hardware problem.

Itā€™s also not that easy to diagnose unless you have spare parts that you can swap in and out to test (if you donā€™t have the extra parts and/or youā€™re not familiar with changing parts in your computer, I donā€™t suggest you swap anything out because you can wreck your computer if you donā€™t know what you are doing).

Weird reboots or blue screen of your computer can be power supply related. But it can also be related to your motherboard.

The problem with MSFS is that it pushes your hardware to its limit. But if you have normal hardware with no defects, even if MSFS pushes your hardware to its limit, you shouldnā€™t blue screen and/or Windows shouldnā€™t force a reboot. If you have damaged hardware, that would explain the Windows reboot and/or blue screen.

37

It would be a good idea to monitor your temperatures with CPU-Zā€™s HW monitor or similar because itā€™s entirely possible a beefed up heatsink or extra fan (e.g. on your chipset) could solve all your problems.

1 Like
38

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.