29 minutes ago, Nuno Pinto said:

No random freezes, i get "memory could not be read" and the "breakpoint CTD". Most rarely the "disappear without notice", although any of these is quite rare lately.

I see. These CTDs are notoriously hard to troubleshoot for the end user and may well be caused by poor coding. Like the "memory could not be read" errors, in which the software (in this case MSFS) asks for a reference to a memory address that doesn't exist. I.e. a "null error". A user trying to find the needle in the haystack looking at his own hardware (or software) may never be able to debug this. 

Problem is that when you request support from Zendesk (like I've done), you get the standard advice that you can find on their website. 

Another thing is that most likely hardware related issues (like overclocks or undervolts) lead to freezes, BSODs or system restarts, not CTDs. 

Edited August 29, 20223 yr by Cpt_Piett

Two flights without issues ... then another CTD. It's a joke.

Same error 0xc0000005

49 minutes ago, Jeeeno said:

Two flights without issues ... then another CTD. It's a joke.

Same error 0xc0000005

I flew for over 10 hours during the weekend. Not 1 CTD. the 0xc000005 error are 99% related to a mod/liveries. The other reason is Overclocking. 

1 hour ago, fogboundturtle said:

I flew for over 10 hours during the weekend. Not 1 CTD. the 0xc000005 error are 99% related to a mod/liveries. The other reason is Overclocking. 

 

I have not installed anything new, I have not overclocked anything. 

1 hour ago, fogboundturtle said:

I flew for over 10 hours during the weekend. Not 1 CTD. the 0xc000005 error are 99% related to a mod/liveries. The other reason is Overclocking. 

Right. So you don't have any mods/liveries installed?

EDIT: Sorry for the snarky remark. Just been plagued by CTDs for the last month or so and getting very sick of it. And it's really not helpful having someone popping in to these threads saying they've been flying for 10 hours with no CTD. 

Edited August 29, 20223 yr by Cpt_Piett

12 minutes ago, Cpt_Piett said:

Right. So you don't have any mods/liveries installed?

EDIT: Sorry for the snarky remark. Just been plagued by CTDs for the last month or so and getting very sick of it. And it's really not helpful having someone popping in to these threads saying they've been flying for 10 hours with no CTD. 

It's not an exact science and 0xC000005 is the most generic error of them all. I would need to spend time with you to figure out which one is causing issue.

4 minutes ago, fogboundturtle said:

It's not an exact science and 0xC000005 is the most generic error of them all. I would need to spend time with you to figure out which one is causing issue.

Thanks but I've been in this thread for over a month now and have pretty much tried "everything". 

7 minutes ago, Cpt_Piett said:

Thanks but I've been in this thread for over a month now and have pretty much tried "everything". 

I, too, had very frequent CTD's with my fancy new RTX 3080 and DDR5 motherboard; I ended up giving up and getting a DDR4 motherboard, as I had a 'hunch' that DDR5 was just too new to be stable for me and my abilities to combat the CTDs. 😕

4 minutes ago, rlk281 said:

I, too, had very frequent CTD's with my fancy new RTX 3080 and DDR5 motherboard; I ended up giving up and getting a DDR4 motherboard, as I had a 'hunch' that DDR5 was just too new to be stable for me and my abilities to combat the CTDs. 😕

Yeah, I suspected the DDR5 to be involved in this somehow, so I ran Memtest to find lots of errors when having XMP enabled in BIOS. I turned down the mem clock, rested and no mem errors. But you're right, DDR5 is new tech that will take time to mature. Jayztwocents had a video some time ago where he tested a lot of the new DDR5 modules and found that in a lot of cases, they led to system instability. The worst case scenarios were trying to run 4 DDR5 modules i.e. occupying all the channels. I'm running 2x16GB.

EDIT: But yeah, my system was stable before the hardware upgrade.  

Edited August 29, 20223 yr by Cpt_Piett

19 minutes ago, fogboundturtle said:

It's not an exact science and 0xC000005 is the most generic error of them all. I would need to spend time with you to figure out which one is causing issue.

MSFS just closes and gives no error at all. That's what the windows event viewer says. MSFS crashing out of nowhere without any changes and Asobo still denying the issue.

6 minutes ago, Jeeeno said:

MSFS just closes and gives no error at all. That's what the windows event viewer says. MSFS crashing out of nowhere without any changes and Asobo still denying the issue.

when it closes without creating any event, it's thermal overclocking type of issue. That's because it's an abnormal exit. He doesn't even take the time to gather telemetry and write the event, it just exit out. I know people like to blame MSFS for everything. The only time I had CTD in MSFS is because I had a defective CPU. It was causing random crashes. After a full week of troubleshooting, it was determine it was the CPU, After it was replace. 0s CTD. As stable as it gets. 

2 minutes ago, fogboundturtle said:

when it closes without creating any event, it's thermal overclocking type of issue. That's because it's an abnormal exit. He doesn't even take the time to gather telemetry and write the event, it just exit out. I know people like to blame MSFS for everything. The only time I had CTD in MSFS is because I had a defective CPU. It was causing random crashes. After a full week of troubleshooting, it was determine it was the CPU, After it was replace. 0s CTD. As stable as it gets. 

Don't believe at all it's an hardware issue because there are tons of people on the forum reporting crashes since 20th of August approximately. Everyone with hardware issue at the same time? 

PS: my computer is perfectly fine with any other software apart from MSFS. 

Edited August 29, 20223 yr by Jeeeno

1 minute ago, Jeeeno said:

Don't believe at all it's an hardware issue because there are tons of people on the forum reporting crashes since 20th of August approximately. Everyone with hardware issue at the same time? 

Not all CTD are created equal. Also I am not stating that there isn't any issue with MSFS. In my experience though, MSFS is a pretty stable platform. Per example. I never got the write memory error on my PC but I do have a 11GB VRAM GPU so I might never see it. It doesn't meant the issue doesn't exist. But you guys are making very broad general statement that MSFS is unstable and it's just not true.

I got 2 of the memory cannot be read errors today. Both times, the location it was trying to read was 0x00000000000000000. Clearly, some pointer is not getting an address pushed to it before something else tries to read where it is pointing.

Just had the 'could not read memory' error.  First CTD in a long time.  I just got a little windows pop-up.  When I clicked OK the sim just vanished.     Like a lot of people, I only started getting these recently.