4 minutes ago, Swe_Richard said:

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

No, I uninstalled Capture One.

I can't test it now. I'm not at home.

This afternoon I can tell you something.

 

2 hours 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!!!

What is the cause of your crashes? Is it clr.dll? 

2 hours 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. 

I uninstalled the Logitech Panel Plugin (just deleted the files and folder), and now I'm using SPAD.neXt instead. Works so much better. 

I have had one CTD lately though, it was with the combination of workingtitle-g3000, aircraft-tbm930-improvement and TBM930 HELLCAT Livery mods.

The second I flicked the battery switch on in the TBM, it froze for a second and went CTD. I don't know what the problem is, because it was working perfectly the day before.

I loaded up a new flight at the same airport with the Carenado Seneca and the pms50-instrumentGTN750 mod and that worked flawlessly. 

I disable and enable the mods I need for every flight with AddonsLinker before loading up the sim.

 

20 minutes ago, devgrp said:

What is the cause of your crashes? Is it clr.dll? 

Log Name:      Application
Source:        Application Error
Date:          11/09/2021 20:28:55
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-Q2EK6FG
Description:
Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000009dbead
Faulting process id: 0x103c
Faulting application start time: 0x01d7a7389da136c5
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.19.8.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.19.8.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: 95f1201c-1a23-4119-b71f-15ff39b8d54d
Faulting package full name: Microsoft.FlightSimulator_1.19.8.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2021-09-11T19:28:55.2359277Z" />
    <EventRecordID>5043</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>DESKTOP-Q2EK6FG</Computer>
    <Security />
  </System>
  <EventData>
    <Data>FlightSimulator.exe</Data>
    <Data>0.0.0.0</Data>
    <Data>00000000</Data>
    <Data>FlightSimulator.exe</Data>
    <Data>0.0.0.0</Data>
    <Data>00000000</Data>
    <Data>c0000005</Data>
    <Data>00000000009dbead</Data>
    <Data>103c</Data>
    <Data>01d7a7389da136c5</Data>
    <Data>C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.19.8.0_x64__8wekyb3d8bbwe\FlightSimulator.exe</Data>
    <Data>C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.19.8.0_x64__8wekyb3d8bbwe\FlightSimulator.exe</Data>
    <Data>95f1201c-1a23-4119-b71f-15ff39b8d54d</Data>
    <Data>Microsoft.FlightSimulator_1.19.8.0_x64__8wekyb3d8bbwe</Data>
    <Data>App</Data>
  </EventData>
</Event>

16 hours 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 too have Capture One installed on my system.  But I am not at home and won’t be for a week so I will keep an eye on what you guys find on this. Nice find though. 

4 hours ago, John Fields said:

No, I uninstalled Capture One.

I can't test it now. I'm not at home.

This afternoon I can tell you something.

 

Hi, Richard (and everybody interested, of course),

After uninstalled Capture One I've just done a few flights over the zones I was having continuous CTDs.

I'm not having CTDs at the moment, but I have very few software installed.

I'll keep my fingers crossed...

Regards.

 

 

55 minutes ago, John Fields said:

Hi, Richard (and everybody interested, of course),

After uninstalled Capture One I've just done a few flights over the zones I was having continuous CTDs.

I'm not having CTDs at the moment, but I have very few software installed.

I'll keep my fingers crossed...

Regards.

 

 

If you do need to reinstall capture 1, you can add just rename those files. I've renamed mine and redid my overclock and xmp profile and so far so good. No crashes at places I always had them even with an empty community folder 

3 hours ago, RabH said:

Log Name:      Application
Source:        Application Error
Date:          11/09/2021 20:28:55
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-Q2EK6FG
Description:
Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000009dbead
Faulting process id: 0x103c
Faulting application start time: 0x01d7a7389da136c5
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.19.8.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.19.8.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: 95f1201c-1a23-4119-b71f-15ff39b8d54d
Faulting package full name: Microsoft.FlightSimulator_1.19.8.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2021-09-11T19:28:55.2359277Z" />
    <EventRecordID>5043</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>DESKTOP-Q2EK6FG</Computer>
    <Security />
  </System>
  <EventData>
    <Data>FlightSimulator.exe</Data>
    <Data>0.0.0.0</Data>
    <Data>00000000</Data>
    <Data>FlightSimulator.exe</Data>
    <Data>0.0.0.0</Data>
    <Data>00000000</Data>
    <Data>c0000005</Data>
    <Data>00000000009dbead</Data>
    <Data>103c</Data>
    <Data>01d7a7389da136c5</Data>
    <Data>C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.19.8.0_x64__8wekyb3d8bbwe\FlightSimulator.exe</Data>
    <Data>C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.19.8.0_x64__8wekyb3d8bbwe\FlightSimulator.exe</Data>
    <Data>95f1201c-1a23-4119-b71f-15ff39b8d54d</Data>
    <Data>Microsoft.FlightSimulator_1.19.8.0_x64__8wekyb3d8bbwe</Data>
    <Data>App</Data>
  </EventData>
</Event>

Hmmm that error code looks like it's memory related 

2 minutes ago, devgrp said:

If you do need to reinstall capture 1, you can add just rename those files. I've renamed mine and redid my overclock and xmp profile and so far so good. No crashes at places I always had them even with an empty community folder 

Hi,

What files have I to rename?

Thank you for your attention.

6 minutes ago, John Fields said:

Hi,

What files have I to rename?

Thank you for your attention.

P1.WIC.NativeComWrapper.dll

The file is in

[CaptureOne install dir]\WIC\WIC64

7 minutes ago, John Fields said:

Hi,

What files have I to rename?

Thank you for your attention.

From:

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

Go to your Capture One installation folder
Rename the file “Capture One 20\WIC\WIC64\P1.WIC.NativeComWrapper.dll” to “Capture One 20\WIC\WIC64\P1.WIC.NativeComWrapper.dll.off”

i additionally disabled the Windows explorer integration in Capture ONE

2 minutes ago, Swe_Richard said:

8 minutes ago, michap7 said:

From:

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

Go to your Capture One installation folder
Rename the file “Capture One 20\WIC\WIC64\P1.WIC.NativeComWrapper.dll” to “Capture One 20\WIC\WIC64\P1.WIC.NativeComWrapper.dll.off”

i additionally disabled the Windows explorer integration in Capture ONE

Thank you, michap7!

 

Thank you, Richard!

 

14 minutes ago, michap7 said:

From:

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

Go to your Capture One installation folder
Rename the file “Capture One 20\WIC\WIC64\P1.WIC.NativeComWrapper.dll” to “Capture One 20\WIC\WIC64\P1.WIC.NativeComWrapper.dll.off”

i additionally disabled the Windows explorer integration in Capture ONE

Thank you, michap7!

 

This seems to have fixed my crashing. Been flying for a few hours now without any problems

On a slightly off-topic note; fun to see so many photographers in here.. ;)