Hi guys, I have been using MSFS since its beta version and had random CTD from time to time. Anyways, from the very end of December I am getting lots of CTDs (let’s say, I succeed in completing just 2 flights in 10!).
I have read a lot of posts regarding CTD and tried all the solution suggested by many of you, yet without any result. My CTD happen at any stage of the flight (taxing, taking off, cruising, approaching, taxing after landing!) and happen regardless of the 3rd party addons (happen also with totally empty Community folder) and of real time traffic and weather (happen also with preset weather and no AI traffic). I have no overclocking, I have updated and rolled back GPU drivers, disabled rolling cache, repaired the MSFS app, set English (USA) as my Windows default language, updated my Windows 10, increased my virtual memory pagefile. I really don’t know what to do next.
Here are my pc specs:
CPU: Intel® Core™ i7-7700K CPU @ 4.20GHz, 4201 Mhz, 4 Core(s), 8 Logical Processor(s)
OS: Microsoft Windows 10 Pro, 10.0.19042 Build 19042
RAM: 32 GB (4 x 8 GB DDR4 3200 Mhz)
GPU: NVIDIA GeForce GTX 1070
MB: ASRock Z270 Pro4
SSD: M2 500 GB (dedicated exclusively to MSFS)
Hope you can give me some new suggestion. Thanks in advance.
hmmm… also tried the depicted other settings ( Text2Speach… ) ?
It’s of course a try and that you got allready CTD before 1.12.13.0 makes the differentiation not easier
I assume with the 1070 you should use the latest nvidia drivers.
Related to overcloacking: dont forget that many users have issues with the RAM if XMP mode is enabled, thus a test without xmp-mode on might be it worth.
Hi, I’ve tried to investigate the XMP issue but can’t figure it out. In my bios, there is no option to activate or deactivate XMP, but just allows to create some sort of profiles. Here are a couple of pictures. How can I change those settings in order to optimize for MSFS? Thanks
Ah gotcha. There should be a way to turn off the XMP profile in the DRAM config or at the start screen of the BIOS. Worst case scenario, maybe resetting the CMOS by pulling the battery for 30 seconds and putting it back in may work.
It looks like (left image) you have choose “Profile 1” ( if the Light Blue is the selected ) which is not the XMP Profile ( what I can see ), thus should be fine. But I can be wrong… hard to see.
To be sure you can also re-check this with tools like CPU-Z . In it you can see the SPD profiles and the current memory settings.
If already no XMP mode, then we have to search issue on other side.
PS.: you can also see what the XMP mode try to do. It bring the memory out of JEDEC standard frequency 3200 and overvoltage the RAM from 1.2 → 1.35V ( what my eyes guess from that picture )
But it looks like you use your RAM within the JEDEC Specs (DDR4-2133) and you not use XMP Profile. It is the 15clock setting, instead the 16clock but should be okay.
So… I assume no issue from this side… ( which is good, and not good together )