Constant CTDs with error 0xc0000005 since SU6

I have a buddy that’s still on windows 7 lol. He swears by it. Uses the version where MS still releases security updates for it. Tried to get me to use Windows 7, cause it’s the best Windows. He doesn’t seem to understand software and hardware compatibility matters to most people.

Just to put your mind at ease :innocent: :wink: :slightly_smiling_face: :upside_down_face: :hugs:

Of course, I do want to switch to Windows 11; I’ve just been too lazy so far, since I only use the Windows PC for MSFS and it it is behind a solid firewall.

I use Linux for work.

I stream the City Updates for Germany and the World Updates for Germany, they are not installed; should i do it ?

For testing purposes, please download and install the City Updates and World Updates that also cover Germany. Also, please download and install EDDS.

EDIT

If you have plenty of free disk space, it would be best to download and install all the City Updates and World Updates. Just don’t install them all at once, as MSFS may freeze.

Thanks for your great help :hugs:

EDDS ist installed; and i will install City Updates for Germany and the World Updates for Germany!

I’ll report back, though I don’t know if I’ll get to it today;
I still want to take the dogs out :guide_dog: :service_dog:definitely without a CTD. :joy:

Unistall and Quit to Desktop.
Clear cache (msfs and nvidia cache)
Restart PC
Install EDDS, City and World updates.

EDIT

It would be best if you install all the City Updates as well.

Hi folks,

As it seems EDDS is the central focus of this issue, and a report has been made in our Bug Reporting Hub, I’ve created an internal entry for the Development Team to investigate.

I encourage those of you encountering CTDs around EDDS without any 3rd party products installed to contribute any findings via this thread: SU6 - Sim CTD near EDDS (Stuttgart)

Thanks
The MSFS Team

4 Likes

I’ve not tried this yet, but one thing I have used in the past when diagnosing crashes in certain geographic locations is to have Littenavmap open, and connected, in the background. I can track you planes progress and will show your flight path right up to the point of the CTD.

This can all of the guesswork out of where it happens, as reports of “It’s somewhere North Easy of Lewisham” isn’t terribly helpful.

One other thing i would add is that on those crashes years ago, the crash log at the time inidcated the autogen scenery, back then being the Blackshark technology, which IIRC is no longer used. The workaround back then was to reduce the quality of autogen scenery from Ultra to Medium or Low, which stoppped the crashes. This could well be a similar issue.

I’ve been getting these CTDs for the past 3–4 days, and almost every time I spawn at Stuttgart (EDDS), start up the Fenix A320, and begin going through the aircraft startup, I get a CTD. At first, I thought it was an addon problem, so I tried spawning in with a cleared Community folder, leaving only Fenix and GSX, but I still got the crashes. The weird thing is that they usually happen while I’m still on the ground and starting the aircraft, which really surprised me. My PC is also fairly high-end (RTX 5070 12GB, Core Ultra 5 245K, 32GB DDR5), so I don’t think performance should be the issue. I’ve also tried disabling HAGS in Windows, as ChatGPT suggested, but unfortunately that didn’t help either. I did get one CTD at Zurich as well, but most of them have happened at EDDS during startup. It’s been really frustrating spending the last couple of days spawning in, starting the aircraft, and crashing over and over again. At first, I thought it was a problem on my end, but finding this forum and seeing that other people are experiencing something similar has given me a bit more hope. Hopefully this gets fixed soon, and thanks for writing about this in the first place!

FYI, see:

Thank you very much sir!

Do you have any tips or suggestions for CTDs that I’m having while flying in the states? Ever since SU6 my sim crashes, without any error pop up, every time. Sometimes it’s within 10 minutes just sitting at the gate, sometimes it lets me takeoff then 20 minutes later crashes. I haven’t had a single CTD in months but after SU6 it’s unplayable. I’ve emptied the community folder, deleted caches, tried different planes and airports, same results. I’ll post my synopsis below that includes specs and error code according to the crash report file.

MSFS 2024 SU6 CTD – 0xC0000005 ThreadProc/FiberProc with PMDG 737, including idle-at-gate crash

System

  • MSFS 2024: PC / Steam
  • Build: 1.8.14.0 (Sim Update 6)
  • CPU: AMD Ryzen 7 7800X3D
  • GPU: AMD Radeon RX 7900 XT 20 GB
  • System RAM: 32 GB DDR5
  • GPU Driver: 26.8.1
  • Graphics API: DirectX 12
  • Aircraft: PMDG 737-800
  • Aircraft WASM: 737NG3.wasm

Problem

Since Sim Update 6, I have been experiencing repeated CTDs in MSFS 2024 involving the exception:

0xC0000005

I have now seen at least two different crash signatures:

  • Msg=“FiberProc” / 0xC0000005
  • Msg=“ThreadProc” / 0xC0000005

I would help you, but starting tomorrow my availability to help will be very limited. If I started helping you now, I wouldn’t be able to provide further guidance tomorrow or the day after. That’s why I recommend contacting support instead.
Submit a request – Microsoft Flight Simulator Support

Before you do, please take a look at the topics below.
How to restore the sim to its vanilla state to get back in game – Microsoft Flight Simulator Support

Checklist: How to troubleshoot crashing/CTDs issues – Microsoft Flight Simulator Support

Basic Troubleshooting: How to troubleshoot crashing/CTDs issues – Microsoft Flight Simulator Support

Advanced Troubleshooting: How to troubleshoot crashing/CTDs issues – Microsoft Flight Simulator Support

MSFS 2024 SU6 CTD – 0xC0000005 ThreadProc/FiberProc with PMDG 737, including idle-at-gate crash

System

  • MSFS 2024: PC / Steam
  • Build: 1.8.14.0 (Sim Update 6)
  • CPU: AMD Ryzen 7 7800X3D
  • GPU: AMD Radeon RX 7900 XT 20 GB
  • System RAM: 32 GB DDR5
  • GPU Driver: 26.8.1
  • Graphics API: DirectX 12
  • Aircraft: PMDG 737-800
  • Aircraft WASM: 737NG3.wasm

Problem

Since Sim Update 6, I have been experiencing repeated CTDs in MSFS 2024 involving the exception:

0xC0000005

I have now seen at least two different crash signatures:

  • Msg="FiberProc" / 0xC0000005
  • Msg="ThreadProc" / 0xC0000005

The latest crash I was not interacting with the simulator at all when it happened.

The PMDG 737 was simply sitting at the gate with the simulator running. I was not flying, changing views, manipulating the aircraft, or doing anything that would cause a sudden increase in workload.

Does anyone have any advice or help??? I have uninstalled, emptied the community folder.. hasn’t helped. Since SU6, I can’t even complete a flight and I am just getting discouraged. Any tips to try would be much appreciated!!!

Moderator Edit: Post edited to comply with this section of the Code of Conduct.

There have been some cases of CTDs due to lack of virtual memory, see the entry “INCREASE THE VIRTUAL MEMORY (PAGEFILE) ON YOUR SYSTEM” in this guide:

https://flightsimulator.zendesk.com/hc/en-us/articles/4406280653202-Advanced-Troubleshooting-How-to-troubleshoot-crashing-CTDs-issues

It is worth a try, since it is very easy and low risk.

I concur with what Frank just said, Increasing Virtual Memory all but eliminates this kind of error. I had this same problem when I first started using 24, and when I researched I found out that the Virtual Memory needs to be at least set to the same amount of RAM in your system to combat this.

I’m not sure whether MSFS24 has an issue or Windows does with this, but I haven’t had a crash like this since I changed my virtual memory size.

CTD’s are very rare for me but I did get one after su6 and one or two before that. I put my crash reports through Claude AI and it did point to some code from Asobo triggering or causing the crash. I reported everything in Zendesk so hopefully Asobo can confirm this or point to another cause.

To make a comparison: on my old system I did get CTD’s caused by some hardware issues. Those reports clearly showed signs of stress on hardware and happened more often. Those signs are completely absent in the crashes I got after I got my new system.

If they come up with anything useful I will report back.

On some configurations, Windows allocates an insufficient amount of virtual memory, so it’s better to set it manually. I explained how to do this a few posts above.
https://forums.flightsimulator.com/t/constant-ctds-with-error-0xc0000005-since-su6/773458/68