Setting XMP in BIOS May Make FS2024 Unstable and CTD

User Support Hub Hardware & Peripherals
, , ,
1

Using the template below will greatly help the team reproduce the issue and ease the process of fixing it. Before posting, search for an existing report. If you are not sure it’s a bug, please first report in User Support Hub.

2 tags are required - add them in the tag section next to the title above:

Feel free to delete this quote section after adding your appropriate tags.

ISSUE DESCRIPTION

MSFS 2024 has been stable for me over the last 4 months, a couple of days ago I was getting all sorts of crashes, I upgraded my bios, I tried different Nvidia drivers, I used different RAM chips, sometime 2 sometimes 4 from my stack of RAM in my draw, reinstalled the sim, cleared caches, I tried everything. I’d get different types of crashes, some after 2 hours, others after 10 minutes, some got logged in problems and reports and event viewer some never got logged, sometimes I’d get a GPU device error. So it ranged.

I spent hours replaying what I’d changed on my system, and eventually worked out I’d set XMP in my bios, changing my memory speed from 4800 to 5200, which my RAM (Corsair) is certified for. This caused MSFS 2024 to become very unstable. However every other game works flawlessly, no RAM issues as I checked this with memtest, only MSFS 2024. So logging this in case it helps anyone else.

[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue?
Yes - vanilla game

FREQUENCY OF ISSUE

How often does this occur for you (Example: Just once, every time on sim load, intermittently)?
Every time just on this mission.

REPRODUCTION STEPS

Please list clear steps you took in order to help our test team reproduce the same issue:

  1. Set XMP in the bios
  2. Load MSFS 2024
  3. Indeterminate amount of time the sim will CTD.

[PC ONLY] FAULT BUCKET ID

If you experienced a crash on PC, sharing your Fault Bucket ID would be extremely helpful. You can learn how to find that ID here: How to find your Fault Bucket ID after a crash [PC]

Fault bucket 1867394620749150806, type 5

YOUR SETTINGS

If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.

What peripherals are you using, if relevant:
Thrustmater 1600 joystick

[PC Only] Are you using Developer Mode or have you made any changes to it?
No

[PC, MSFS 2020 Only] Are you using DX11 or DX12?

DX12

[PC Only] Many issues may be due to an outdated graphics card. Please state your Graphics Card Driver Manufacturer (NVIDIA, Intel, AMD) and Version:

Latest version 576.52

[PC Only] What other relevant PC specs can you share?

System Information

  Time of this report: 6/17/2025, 18:17:30
         Machine name: ZOOZE-PCS
           Machine Id: {3520F7EC-4FEC-46D1-8EFB-2A417177A571}
     Operating System: Windows 11 Pro 64-bit (10.0, Build 26100) (26100.ge_release.240331-1435)
             Language: English (Regional Setting: English)
  System Manufacturer: PCSpecialist
         System Model: Intel Z790 Ddr5
                 BIOS: 1820 (type: UEFI)
            Processor: 13th Gen Intel(R) Core(TM) i7-13700KF (16 CPUs), ~3.4GHz
               Memory: 65536MB RAM
  Available OS Memory: 65358MB RAM
            Page File: 8146MB used, 66427MB available
          Windows Dir: C:\WINDOWS
      DirectX Version: DirectX 12
  DX Setup Parameters: Not found
     User DPI Setting: 96 DPI (100 percent)
   System DPI Setting: 96 DPI (100 percent)
      DWM DPI Scaling: Disabled
             Miracast: Available, no HDCP

Display Devices

       Card name: NVIDIA GeForce RTX 4070 SUPER
    Manufacturer: NVIDIA
       Chip type: NVIDIA GeForce RTX 4070 SUPER
        DAC type: Integrated RAMDAC
     Device Type: Full Device (POST)
      Device Key: Enum\PCI\VEN
  Display Memory: 44677 MB
Dedicated Memory: 11999 MB
   Shared Memory: 32678 MB
    Current Mode: 1920 x 1080 (32 bit) (60Hz)
     HDR Support: Not Supported
Display Topology: Internal

MEDIA

Fault bucket 1867394620749150806, type 5
Event Name: MoAppCrash
Response: Not available
Cab Id: 0

Problem signature:
P1: Microsoft.Limitless_1.4.20.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.4.20.0
P4: 00000000
P5: FlightSimulator2024.exe
P6: 1.4.20.0
P7: 00000000
P8: c0000005
P9: 0000000001dab9ca
P10:

Attached files:
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.37ee9d55-8eec-4540-9777-26116e6aefb1.tmp.dmp
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.cdcc2827-d170-49e0-baa2-ec885995064c.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.1d5aefa3-08e8-4357-82aa-5773814393a8.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.6256c5aa-60bb-4afb-8f8f-903d9b6d63d5.tmp.txt
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.cff75407-a313-4637-8d46-c821522d89c7.tmp.xml

These files may be available here:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.Limitl_a0f7c9ee2ce29af42a3d7936f9ed2ee6fe4522_fea788ec_eddd213e-aff8-4215-84b8-31a483ade7fc

Analysis symbol:
Rechecking for solution: 0
Report Id: 3becfd37-4dbc-42cb-9ad0-221d5d2009c0
Report Status: 268435456
Hashed bucket: 616a119cf1028aab59ea5183813a7a56
Cab Guid: 0

Faulting application name: FlightSimulator2024.exe, version: 1.4.20.0, time stamp: 0x00000000
Faulting module name: FlightSimulator2024.exe, version: 1.4.20.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000001dab9ca
Faulting process id: 0x4C4
Faulting application start time: 0x1DBDFA9CAEC6C6B
Faulting application path: C:\Program Files\WindowsApps\Microsoft.Limitless_1.4.20.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.Limitless_1.4.20.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe
Report Id: 3becfd37-4dbc-42cb-9ad0-221d5d2009c0
Faulting package full name: Microsoft.Limitless_1.4.20.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

[END OF FIRST USER REPORT]

:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?
•

Provide extra information to complete the original description of the issue:
•

If relevant, provide additional screenshots/video:
•

2

After updating your BIOS, did you install the latest chipset drivers for that motherboard?

2 Likes
3

I cannot run my memory at its rated frequency either for FS2024.

MB - Gigabyte Z790
Memory DDR 5 - G Skill, 7200 QVL

It will boot and run okay at 7200 for Windows 11 and common apps,
But it only runs okay at 6400 Mhz for FS2024.
I keep XMP set but with the speed set to 6400.
This same memory runs FS2024 okay on other motherboards.

I think the problem is not FS2024.
It is a problem with the MB and CPU memory controller.

If the memory is QVL at a certain speed, it only means that the memory has ran at that speed without problems for the manufacturer.

It does not mean that it will run okay at that speed on your particular
MB and memory chips and CPU and app.

3 Likes
4

Everyone really ought to qualify their memory since so many problems can be caused by memory errors and many errors only appear during certain circumstances. They crash some programs and don’t bother others depending on the program that sees the error and how it’s using the data.

Memtest86 is a free tool you can do it with. It beats on memory writing and reading and verifying what it read is what it wrote. If you look it over you’ll see there are a number of different routines used to ferret out memory, memory controller, and some CPU issues.

Those different tests it runs are important. They write different bit patterns to memory cells to spot issues with crosstalk between bits, weak drive, etc. Errors can depend on the data written so Memtest writes the data with various bit patterns.

It’s important to keep in mind that how a program behaves with bad data depends on how it’s using that data and which bits get erroneously set or cleared by the error. Most home computers don’t use ECC DRAM so can’t spot single bit errors. It all depends on the program.

Anyone having CTDs really ought to run Memtest and make sure their system runs clean. Only after that can you have confidence what is being seen is a program issue.

And memory can go bad too especially as summer brings a hotter operating environment for many systems. Heat can also provoke memory to throw errors. It’s super easy to run Memtest and it can help make sure efforts are made in the right place instead of spinning wheels.

Memory errors are not the fault of the program. It’s pure hardware. Some programs may tend to hit a bad DIMM more than others and it can also help to troubleshoot by swapping RAM in slots to verify the problem moves with a DIMM. Hardware problems should but deep down in a computer it’s still an analog world and it could be a slot or even the design of the motherboard can be a factor.

Added - and what @BegottenPoet228 said - motherboard bios and drivers can tweak settings to give higher speed and more reliable performance. Unless you are avoiding some known bios issue, checking the bios release notes for any revisions that improve memory compatibility may point to easier and cheaper ways to fix things.

2 Likes
5

I will definately give this a go. It has the chipset drivers installed but probably not the latest.

6

Many thanks memtest as said in the original post runs fine. Ok for a thorough run it take all night but no issues.

1 Like
7

Another tool to test memory is OCCT.

Hopefully by updating chipset + BIOS the OP will solve the problem.

8

Fingers crossed, i have to admit ive not updates chipset drivers since the PC build two years ago. So will try that next.

9

Did you or are you still running a undervolt in your bios? I had frequent CTD’s in the past. After setting a less agressive undervolt my CTD’s disapeared.

With the old undervolt I had set all kind of tests mentioned above gave no problems also all other games… no issue. Only the sim had problems, I think it causes some high volt peaks that make it CTD.

Don’t know it is helpfull for your case, just wanted to share my experience

10

No undervolt set in the bios, I even put back to intel fail safe defaults. But testing now with new chipset drivers, so far so good.

11

Same here been getting crashes, usually it’s the dxgi error, used to get it in 2020 but older driver fixed it, but with 2024 no amount of driver would fix it, then the other night I was getting crash to desktop without even getting the dxgi error. Did a bit of googling and some people said turn xmp off. My ram was on mobo qvl list and not had any issues in 2020 or memtest.

Anyway turned off xmp the other night and so far so good no more errors, except for performance degradation during longer flights.

Will revisit the xmp at a later date once I know it’s 100% but for now it seems to have finally solved both dxgi error and the recent ctd with no errors. The latter only seemed to start after trying beta 3 and removing it again, was close to doing yet another re-install

1 Like
12

Im able to run 4x16GB at their rated 5600mt DDR5 XMP. Ms2024, su3beta.
Asus recently released a Bios update for 4 memory sticks, which coud cause problems before.

Updated bios, chipset drivers, new PSU, new 600W cable for 5090…seems stable so far.

13

Hello @zooze74,

Thank you for this report. We’ve moved your topic into the User Support Hub.

The Bug Reporting Hub is for posting suspected or confirmed bugs that other users are able to reproduce without duplicating an existing bug report. Using the template or providing all the relevant information about your bug and sim setup is required in order to provide valuable information, feedback, and replication steps to our test team.

If you are not sure if your issue is a bug or need further input from the community, please use the User Support Hub category. If the community can replicate your issue, first search the Bug category to see if there’s an existing topic. If it already exists, contribute to that report. Duplicate bug reports will be closed.

If you believe it is a new report and no duplicate exists, then create a new bug topic using the provided topic template.

All issues caused by or involving third-party addons/mods should be reported to the third-party developer. Assure that no addons/mods are used when reporting issues in Bug Reports.

1 Like
14

Agree this is a tough problem to solve, I’ve stabilized the system doing multiple things. Using P cores only really helps and not had a crash since doing this, latest chipset drivers is important. And not using XMP really makes a difference as well. All now is stable, however altering these makes a difference for example if I use efficiency cores then I will get random crashes, may go for 4 hours fine then suddenly a hard lock crash, or soft lock crash, or GPU crash or something.

15

Modified title, as using XMP may or may not cause instability or CTDs, depending upon a user’s hardware. It does not universally cause these issues.

(Title originally was: “Setting XMP in the BIOS makes FS2024 CTD and very unstable”, which made sense when the topic was originally posted by the OP in the Bug Reporting Hub & referred just to the OPs system. )

1 Like