20 minutes ago, Jeeeno said:

Yesterday night, 2h flight, no issues. Today 1h flight, crashed on short final, same 00005 error and no other hints. My simulator is useless since 20th of August, I've made no changes, and still it crashes randomly and frequently. 

It's very frustrating, yes. Are you overclocking anything? XMP enabled in BIOS? DDR4 or 5? Addons? There's so many things that potentially can influence these type of CTDs. But they seem to be random, at least for me. I've been flying for 8 hrs or so now, stable, after I stopped using AIG TC and FSRealistic. Could be a coincidence, could be relevant. Almost impossible to tell.  

Edited August 31, 20223 yr by Cpt_Piett

My report is: from August 2020 to 20th of August 2022 I had I think two crashes in total: both caused by a faulty scenery. 

Then on 21 of August I had a crash while preparing the aircraft at the gate (PMDG B737 on a freeware scenery which I've been before and I've never had any crash). The cause was NTDLL.dll.

Restarted MSFS and managed to takeoff but after 30 minutes another CTD caused by 0xc0000005.

Then I parked MSFS for a week without touching anything.

Came back on 28 of August, installed some Windows 10 updates, restarted the PC completed two flights without reloading the sim, using PMDG B737 and freeware sceneries. 

Started a flight on 29th of August, crash during taxi-out for takeoff (PMDG B737 using Italy Update scenery, CTD caused by 0xc0000005).

I did a sfc/scannow and deleted the old rolling cache then on 30th of August I managed to complete a 2 hour flight without issues.

Started a flight on 31th of August, crashed on short final using PMDG B737 at Benelux World Update scenery, CTD caused by 0xc0000005

 

 

Edited August 31, 20223 yr by Jeeeno

16 minutes ago, Cpt_Piett said:

But they seem to be random, at least for me.

I have been reading in this thread about your CTD issue with compassion, it is indeed very frustrating. One possible idea to help, did you recently make a MEMTEST of your RAM?

If not, it would be worth spending the two hours needed to do it (approximate time for your 32 GB).

Good luck.

10 minutes ago, Jeeeno said:

My report is

Thanks for the detailed report. You didn't do any hardware changes at all? 

3 minutes ago, Bernard Ducret said:

I have been reading in this thread about your CTD issue with compassion, it is indeed very frustrating. One possible idea to help, did you recently make a MEMTEST of your RAM?

If not, it would be worth spending the two hours needed to do it (approximate time for your 32 GB).

Good luck.

Oh thanks 🙂. Yeah I did a few weeks ago. Got plenty of errors with XMP. No XMP and no errors. 

8 minutes ago, Cpt_Piett said:

Thanks for the detailed report. You didn't do any hardware changes at all? 

Nothing at all. Not even Nvidia drivers. 

today I had my first CTD in more than 6 months. And it is showing the ntdll error on the event viewer.

Some changes from the last flight on monday to today:

1. changed my 32" 4k oled 60hz monitor (amd freesync only) SDR. Now running a LG C1 48" with GSync and VRR on HDR.

2. previously i had the msfs Vsync on with 50% refresh rate to run the sim at 30fps. never had stutters or anything like that. since moving to the C1 I turn off vsync and lock my FPS at 30fps via RivaTuner.

3. for the first time I tried reshade and I was blown away with the colors.

Again never had a CTD until today, but these are the changes since monday...I will go back to see if I can pinpoint the root cause but if you can share any thoughts I would appreciate it.

24 minutes ago, ttbq1 said:

for the first time I tried reshade and I was blown away with the colors.

Congrats on the 48" OLED 🙂 I had more CTDs with a different version of reshade, but it seems stable for now (knock on wood) after I changed to a different version. 

Although the ntdll CTDs was were supposedly fixed after they occurred very frequently last weekend https://forums.flightsimulator.com/t/constant-ctd-every-flight-now-ntdll-dll/537543?u=cptpiett8113

Edited August 31, 20223 yr by Cpt_Piett

For those who are getting CTDs in MSFS, but you are also sure that you have emptied your community folder and you aren't using any add-ons, even add-ons from the MSFS marketplace (because add-ons are probably the #1 source of MSFS CTDs), you definitely want to do a MemTest to make sure your CPU + RAM aren't giving you memory errors. I ran MemTest and it gave me memory errors, which explained my CTDs in MSFS. Once I fixed the issues with MemTest by lowering the clock speed of my RAM and MemTest passed on an overnight test, MSFS was then stable for me.  Also double check that your GPU is also not overclocked.

In general add-ons are the biggest reasons for CTDs in MSFS.  Probably the second biggest reason for CTDs is overclocking - but this is tricky, because you may not even realize that a component in your system is overclocked like me, when I purchased my system.

 

Edited August 31, 20223 yr by abrams_tank

Just now, abrams_tank said:

For those who are getting CTDs in MSFS, but you are also sure that you have emptied your community folder and you aren't using any add-ons, even from the MSFS marketplace (because add-ons are probably the #1 source of MSFS CTDs), you definitely want to do a MemTest to make sure your CPU + RAM aren't giving you memory errors. I ran MemTest and it gave me memory errors, which explained my CTDs in MSFS. Once I fixed the issues with MemTest by lowering the clock speed of my RAM and MemTest passed on an overnight test, MSFS was then stable for me.  Also double check that your GPU is also not overclocked.

In general add-ons are the biggest reasons for CTDs in MSFS.  Probably the second biggest reason for CTDs is overclocking - but this is tricky, because you may not even realize that your system is overclocked like me, when I purchased my system.

 

 

I can understand that most CTD are caused by addons or overclocking, but how can you explain my case where I made no changes, no new add-ons and MSFS starts crashing out of nowhere?

5 minutes ago, Jeeeno said:

 

I can understand that most CTD are caused by addons or overclocking, but how can you explain my case where I made no changes, no new add-ons and MSFS starts crashing out of nowhere?

I didn't look at your particular case in detail.  But I am seeing you are flying with the PMDG 737. To isolate the CTD issue, you want to test MSFS without using any add-ons. The PMDG 737 counts as an add-on. 

You want to test MSFS with just vanilla MSFS - no add-ons at all, no add-ons in your community folder, no marketplace add-ons either.  If vanilla MSFS runs without problems and doesn't CTD, it's likely one of your add-ons that is causing the CTDs. If vanilla MSFS without add-ons is CTDing on you, then it could be something you installed in Windows, or some other issue. At this point, if vanilla MSFS without add-ons is CTDing on you, you might want to run an overnight MemTest.

Edited August 31, 20223 yr by abrams_tank

25 minutes ago, abrams_tank said:

For those who are getting CTDs in MSFS, but you are also sure that you have emptied your community folder and you aren't using any add-ons, even add-ons from the MSFS marketplace (because add-ons are probably the #1 source of MSFS CTDs)

I think most of us prefer to fly with some addons Abrams. I'm currently trying to figure out which addon (or addon combination) causes instability. As I've ruled out hardware issues. But I think doing that is an important first step. 

EDIT: I agree with your advice though. Check hardware, then vanilla MSFS first. 

25 minutes ago, abrams_tank said:

Probably the second biggest reason for CTDs is overclocking - but this is tricky

I'm not so sure about that. Generally when I've had an unstable OC in the past (with various games) I've experienced freezes, lockups and BSODS. But I wouldn't rule out OC as a source of CTDs however. Like I've (probably) mentioned, I've been more stable after I removed XMP (memory OC) and GPU OC. 

Edited August 31, 20223 yr by Cpt_Piett

8 minutes ago, Cpt_Piett said:

I think most of us prefer to fly with some addons Abrams. I'm currently trying to figure out which addon (or addon combination) causes instability. As I've ruled out hardware issues. But I think doing that is an important first step. 

EDIT: I agree with your advice though. Check hardware, then vanilla MSFS first. 

Oh yeah, for sure, I like to use add-ons too. But this is too isolate the issue.  In software development, the first thing they teach you when you have a bug, is to try to isolate the bug. To isolate a bug, you need to simplify the issue as much as possible and eliminate all other possible factors, while trying to reproduce the bug.

Once you isolate the issue, you can rectify it and then gradually add back your add-ons.

This is what I did. I'm running with all the add-ons that I want to run now and MSFS is stable for me.  But that's because I took the time to isolate and figure out what my issue was. 

Edited August 31, 20223 yr by abrams_tank

I remember reading that post of yours. This is an important point, and somewhat unfair to the end user. If you purchased a PC (i.e. you didn't build it yourself) you may have XMP enabled in the BIOS as well as a factory OC'd GPU. This can cause stability issues with MSFS. 

EDIT: Well you may have those things even if you built your PC. The point is, you might be thinking everything is fine, as you haven't done a manual OC. 

Side-track: Anyone else getting delays and errors when posting on AVSIM?

On 8/14/2022 at 1:00 PM, abrams_tank said:

This was baffling to me, that a new CPU, the i5-12400, may not work well with DDR4 RAM above 3200 MHZ.  DDR4 is an old RAM standard, the box of my RAM clearly says 3600 MHZ, and given that some DDR4 RAM can go above 5000 MHZ, I did not consider my RAM to be overclocked at all (especially if I am following what it said on the box of the RAM, which was 3600 MHZ). But I guess my DDR4 RAM is overclocked at 3600 MHZ, because my motherboard's manual had a warning about going over 3200 MHZ for DDR4 with the new line of Intel 12th gen CPUs.

Edited August 31, 20223 yr by Cpt_Piett

24 minutes ago, Cpt_Piett said:

I remember reading that post of yours. This is an important point, and somewhat unfair to the end user. If you purchased a PC (i.e. you didn't build it yourself) you may have XMP enabled in the BIOS as well as a factory OC'd GPU. This can cause stability issues with MSFS. 

Yup. In my case, the store that sold my system to me, should have told me that my RAM, although it was 3600 MHZ RAM, and 3600 MHZ was clearly labeled in big letters on the box of the RAM, could cause system stability issues if the RAM was clocked to 3600 MHZ, exactly what was labeled on the box.

The irony is, the store that sold the system to me, probably didn't even know the i5-12400, combined with my motherboard, doesn't support RAM clocked to 3600 MHZ. I had to find that out myself after a lot of investigating.  In effect, my RAM was overclocked and I didn't even know it was overclocked (and neither did the store that sold it to me).

Edited August 31, 20223 yr by abrams_tank