3 hours ago, michap7 said:

Hi there!

So, after 2 Days of reinstalling (Win 10, my necessary software and a vanilla FS2020) and after my first flight (World updates not yet installed) to good old C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll CTDs are back... Can´t understand it anymore... Hardware issue? Software issue? And think I will give up now and will stop flying... But if MSFS not looked so nice (and was rocking stable before SU5 for me) it would be easier to quit... 🤬 

If you have any memory or cpu overclock remove them. I did the same as you reinstalled windows and I still kept getting clr.dll ctd. They completely stopped when I removed my overclock and xmp profile 

3 minutes ago, devgrp said:

If you have any memory or cpu overclock remove them. I did the same as you reinstalled windows and I still kept getting clr.dll ctd. They completely stopped when I removed my overclock and xmp profile 

Yes this could be a solution for some people, but I tried it and removing oc did not help... 

To me, this could be a solution:

https://forums.flightsimulator.com/t/ctd-caused-by-capture-one-20-codec/452538/20

After removing Capture One from the Windows context menue AND renaming the .dll mentioned in the link above, ctd seem to be less frequent than before. Let´s wait an see... 

16 minutes ago, michap7 said:

To me, this could be a solution:

https://forums.flightsimulator.com/t/ctd-caused-by-capture-one-20-codec/452538/20

After removing Capture One from the Windows context menue AND renaming the .dll mentioned in the link above, ctd seem to be less frequent than before. Let´s wait an see... 

I also have capture one installed so I'll check to see if those files are loaded on my next flight 

6 hours ago, devgrp said:

If you have any memory or cpu overclock remove them. I did the same as you reinstalled windows and I still kept getting clr.dll ctd. They completely stopped when I removed my overclock and xmp profile 

Hi, 

Did you install any software after re-installing MSFS 2020?

Because I suspect that something is interfering with MSFS and causing the clr.dll errors.

In fact, if you uninstall MSFS and then re-install it, the CTDs disappear momentarily, until you, eventually, install another software  that "crushes" some MSFS file.

in that case, t would be essential to know what app causes the crashes.

Regards.

2 hours ago, John Fields said:

Hi, 

Did you install any software after re-installing MSFS 2020?

Because I suspect that something is interfering with MSFS and causing the clr.dll errors.

In fact, if you uninstall MSFS and then re-install it, the CTDs disappear momentarily, until you, eventually, install another software  that "crushes" some MSFS file.

in that case, t would be essential to know what app causes the crashes.

Regards.

In my case it could be Capture One which is interfering with MSFS. But unfortunately I reinstalled some software (including Capture One) before reinstalling MSFS. I will have to further check it later...

Edited September 13, 20214 yr by michap7

3 hours ago, John Fields said:

Hi, 

Did you install any software after re-installing MSFS 2020?

Because I suspect that something is interfering with MSFS and causing the clr.dll errors.

In fact, if you uninstall MSFS and then re-install it, the CTDs disappear momentarily, until you, eventually, install another software  that "crushes" some MSFS file.

in that case, t would be essential to know what app causes the crashes.

Regards.

Only other software I have installed are Capture One, Photoshop and Davinci Resolved and a few plugins

Edit* 

Just fired up the sim and it is indeed loading those files. Just got to find out what those files do

Edited September 13, 20214 yr by devgrp

42 minutes ago, devgrp said:

Only other software I have installed are Capture One, Photoshop and Davinci Resolved and a few plugins

Edit* 

Just fired up the sim and it is indeed loading those files. Just got to find out what those files do

In Windows, I think they belong to the shell intergration of Capture one. For what reason MSFS loads them Idon´t know... Yesterday I disabled the explorer shell integration of Capture one and did some short flights in areas usually prone to CTDs without any problems. Now I have to do some real world work and have to try more flights later.

Edited September 13, 20214 yr by michap7

57 minutes ago, michap7 said:

In Windows, I think they belong to the shell intergration of Capture one. For what reason MSFS loads them Idon´t know... Yesterday I disabled the explorer shell integration of Capture one and did some short flights in areas usually prone to CTDs without any problems. Now I have to do some real world work and have to try more flights later.

Hi, michap7,

I think all the problems with CTDs could point to Capture One. I realize now that I had installed Capture One 21 and I have continuous CTDs. 

I don't know if there's another software that causes issues.

Regards.

Edited September 13, 20214 yr by John Fields

For me the CTD's started after SU5 and have continued after WU6, my CTD's only happen in flight and I can't pinpoint the cause! Before SU5 I had only 1 or 2 CTD's so I think the problem lies there, I can have a couple of flights without a problem and I can have CTD's flight after flight...its very frustrating as the game is amazing when it works properly! Zendesk asked me to try flying without Navigraph and I thought they had found my problem, 5 and a half hours into a flight and it crashed once again...sigh! I think everybody is trying to blame their systems but for me the problem lies with something from SU5!!!

7 minutes ago, RabH said:

For me the CTD's started after SU5 and have continued after WU6, my CTD's only happen in flight and I can't pinpoint the cause! Before SU5 I had only 1 or 2 CTD's so I think the problem lies there, I can have a couple of flights without a problem and I can have CTD's flight after flight...its very frustrating as the game is amazing when it works properly! Zendesk asked me to try flying without Navigraph and I thought they had found my problem, 5 and a half hours into a flight and it crashed once again...sigh! I think everybody is trying to blame their systems but for me the problem lies with something from SU5!!!

Yes, It's annoying!

I've read (flightsimulator.com forums) that, apart from Capture One, the Logitech Panel plugins can cause CTDs!

In my case I use both (CO and Logitech Multi Panel). 

You should not give up software that normally does not give any problems in Windows and that you use normally.

I think Asobo must check that question. 

2 minutes ago, John Fields said:

Yes, It's annoying!

I've read (flightsimulator.com forums) that, apart from Capture One, the Logitech Panel plugins can cause CTDs!

In my case I use both (CO and Logitech Multi Panel). 

You should not give up software that normally does not give any problems in Windows and that you use normally.

I think Asobo must check that question. 

Exactly, I don't have any of those and still get regular CTD's!

The information about Capture One is very interesting indeed. Running Capture One Pro 20 (or is it 21..?) myself. Will absolutely have to examine this further. Odd thing, though, that WU6 seems to have solved the CTDs (6 out of 6 flights completed with no issue).

1 minute ago, Swe_Richard said:

The information about Capture One is very interesting indeed. Running Capture One Pro 20 (or is it 21..?) myself. Will absolutely have to examine this further. Odd thing, though, that WU6 seems to have solved the CTDs (6 out of 6 flights completed with no issue).

Hi, Richard!

As you know, I had to re-install Windows and MSFS. Everything was fine, but I began to have CTDs after I installed a few apps (one of them Capture One Pro 21). I don't know what is the cause, but it could be CO (or another app).

Regards.

2 minutes ago, John Fields said:

Hi, Richard!

As you know, I had to re-install Windows and MSFS. Everything was fine, but I began to have CTDs after I installed a few apps (one of them Capture One Pro 21). I don't know what is the cause, but it could be CO (or another app).

Regards.

Have you tried renaming the Capture One file in question? Seems like it is certainly worth a try!