Every time I run my sim, Chase Plane crashes... When I load it up again, there's a 50% chance it will get past the loading splash screen. When it does load, it works fine... for about 5-10 minutes... After that, I get a "ChasePlane has stopped working" alert, with no option to wait until it responds...

I can't fly anywhere or anything without this happening and I kid you not, I managed to get about 20 icons loaded into the systray before taking off from Abu Dhabi!!! Of course, there aren't 20 processes open, they are just left there from the last time it ran and they disappear when i hover over them...

 

This is just a small variety of the errors that appear in Event Viewer:

Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: ChasePlane.exe
P2: 0.3.66.0
P3: 59877897
P4: clr.dll
P5: 4.7.2102.0
P6: 593710c8
P7: c0000005
P8: 00019080
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER15B2.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1788.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1797.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER17A7.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_ChasePlane.exe_28e170f96931d9e1736456a6383186d55ee43256_f71cd038_2023237d

Analysis symbol: 
Rechecking for solution: 0
Report ID: 4604c904-eaa8-4885-94a6-06483b55dec8
Report Status: 97
Hashed bucket: 

Faulting application name: ChasePlane.exe, version: 0.3.66.0, time stamp: 0x59877897
Faulting module name: clr.dll, version: 4.7.2102.0, time stamp: 0x593710c8
Exception code: 0xc0000005
Fault offset: 0x00019080
Faulting process ID: 0x2c4c
Faulting application start time: 0x01d315934bd434b6
Faulting application path: C:\Program Files (x86)\OldProp Solutions Inc\ChasePlane\ChasePlane.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
Report ID: 4604c904-eaa8-4885-94a6-06483b55dec8
Faulting package full name: 
Faulting package-relative application ID: 

Application: ChasePlane.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an internal error in the .NET Runtime at IP 70C49080 (70C30000) with exit code 80131506.

Fault bucket , type 0
Event Name: BEX
Response: Not available
Cab Id: 0

Problem signature:
P1: ChasePlane.exe
P2: 0.3.66.0
P3: 59877897
P4: StackHash_2beb
P5: 0.0.0.0
P6: 00000000
P7: PCH_D2_FROM_ntdll+0x000722CC
P8: c0000005
P9: 00000008
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA704.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA89B.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA8CB.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA8EB.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_ChasePlane.exe_edaeb160741125eadc9a62b23b97a9e7a8cc_f71cd038_045cb5f8

Analysis symbol: 
Rechecking for solution: 0
Report ID: 954a2c18-a696-445d-9e7a-7a579f654c03
Report Status: 97
Hashed bucket: 

Faulting application name: ChasePlane.exe, version: 0.3.66.0, time stamp: 0x59877897
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0xfc001810
Faulting process ID: 0x1d88
Faulting application start time: 0x01d315931e07f51d
Faulting application path: C:\Program Files (x86)\OldProp Solutions Inc\ChasePlane\ChasePlane.exe
Faulting module path: unknown
Report ID: 954a2c18-a696-445d-9e7a-7a579f654c03
Faulting package full name: 
Faulting package-relative application ID: 

Application: ChasePlane.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
   at SlimDX.DirectInput.Mouse.GetCurrentState(SlimDX.DirectInput.MouseState ByRef)
   at SlimDX.DirectInput.Mouse.GetCurrentState()
   at ChasePlane.MainWindow.Device_MouseInput()
   at System.Threading.ThreadHelper.ThreadStart_Context(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Threading.ThreadHelper.ThreadStart()

 

This is absolutely ridiculous!!! I can't fly without ChasePlane, and I can't fly with these stupid crashes... Can anyone explain what's going on???

I'm running P3Dv3 and the issues happen even on a clean installation.

The report you posted seems to point to an error in the .Net Framework:

The process was terminated due to an internal error in the .NET Runtime at IP 70C49080 (70C30000) with exit code 80131506.

Try reinstalling .Net framework with the latest version available on Microsoft's website.

On 8/16/2017 at 3:49 AM, Keven Menard said:

The report you posted seems to point to an error in the .Net Framework:

The process was terminated due to an internal error in the .NET Runtime at IP 70C49080 (70C30000) with exit code 80131506.

Try reinstalling .Net framework with the latest version available on Microsoft's website.

I've tried that, but then it just says this:

.NET Framework 4.7 or a later update is already installed on this computer.

I've completely uninstalled any versions of .NET and i still get that. I am unable to uninstall 4.5.1, nothing happens when i click uninstall.

I am having same issue when trying to load FSLabs A320 in P3D V4. Worked perfectly the first time except ezdok views were a bit messed up. So I ran the EZCA confiscator, relaunched and error ever since. Have tried so many things. Most pain full CTD issue ever!!

 

Faulting application name: Prepar3D.exe, version: 4.1.7.22841, time stamp: 0x59d67e95
Faulting module name: clr.dll, version: 4.7.2600.0, time stamp: 0x59d78bb6
Exception code: 0xc0000005
Fault offset: 0x00000000004104fb
Faulting process id: 0x2e4c
Faulting application start time: 0x01d36bf71267cd89
Faulting application path: C:\Prepar3D v4\Prepar3D v4\Prepar3D.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll

2 hours ago, jwd146 said:

I am having same issue when trying to load FSLabs A320 in P3D V4. Worked perfectly the first time except ezdok views were a bit messed up. So I ran the EZCA confiscator, relaunched and error ever since. Have tried so many things. Most pain full CTD issue ever!!

 

Faulting application name: Prepar3D.exe, version: 4.1.7.22841, time stamp: 0x59d67e95
Faulting module name: clr.dll, version: 4.7.2600.0, time stamp: 0x59d78bb6
Exception code: 0xc0000005
Fault offset: 0x00000000004104fb
Faulting process id: 0x2e4c
Faulting application start time: 0x01d36bf71267cd89
Faulting application path: C:\Prepar3D v4\Prepar3D v4\Prepar3D.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll

Dont  know  why  your  posting  a ezdok  issue  in the  chase plane  thread