.NET Runtime and Application Error

[Kosta]

Hello,

I've encountered two application crashes today. What was weird about it, was that both Application errors were prefaulted by .NET Runtime exception.

Application: Prepar3D.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0020001, exception address 00007FFEEF803FB8
Stack:

And then:

Faulting application name: Prepar3D.exe, version: 4.1.7.22841, time stamp: 0x59d67e95
Faulting module name: KERNELBASE.dll, version: 10.0.16299.15, time stamp: 0x4736733c
Exception code: 0xc0020001
Fault offset: 0x0000000000013fb8
Faulting process id: 0x2574
Faulting application start time: 0x01d35ba4a3d8b6c5
Faulting application path: E:\P3D\Prepar3D.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 780a96af-ae5c-418d-b6da-213475727214
Faulting package full name:
Faulting package-relative application ID:

2nd crash:
Application: Prepar3D.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 00007FF8A65950C0
Stack:

And then:

Faulting application name: Prepar3D.exe, version: 4.1.7.22841, time stamp: 0x59d67e95
Faulting module name: api.dll, version: 4.1.7.22841, time stamp: 0x59d67f36
Exception code: 0xc0000005
Fault offset: 0x00000000000250c0
Faulting process id: 0x134c
Faulting application start time: 0x01d35bf2a30492a5
Faulting application path: E:\P3D\Prepar3D.exe
Faulting module path: E:\P3D\api.dll
Report Id: 11350735-d6b9-4f9d-b14f-0fa06d85c7cc
Faulting package full name:
Faulting package-relative application ID:

And

Faulting application name: Prepar3D.exe, version: 4.1.7.22841, time stamp: 0x59d67e95
Faulting module name: api.dll, version: 4.1.7.22841, time stamp: 0x59d67f36
Exception code: 0xc000041d
Fault offset: 0x00000000000250c0
Faulting process id: 0x134c
Faulting application start time: 0x01d35bf2a30492a5
Faulting application path: E:\P3D\Prepar3D.exe
Faulting module path: E:\P3D\api.dll
Report Id: d0024ede-45da-4214-bfce-029fa5aff063
Faulting package full name:
Faulting package-relative application ID:

Does this mean anything to devs, what would be correct way to troubleshoot this? I know I might try without addons, however not really a viable option, as it happens after +1hrs into the flight, completely randomized.

Thanks

[sunjunkiesi]

I've just had the exact same problem.

[valir]

I had the same today

Application: Prepar3D.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0020001, exception address 00007FFC825F9D98
Stack:


Faulting application name: Prepar3D.exe, version: 4.1.7.22841, time stamp: 0x59d67e95
Faulting module name: KERNELBASE.dll, version: 10.0.15063.726, time stamp: 0x1a9bbe0b
Exception code: 0xc0020001
Fault offset: 0x0000000000069d98
Faulting process id: 0x1e1c
Faulting application start time: 0x01d37124d91b9fe0
Faulting application path: F:\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 8c523449-d88c-4c4e-902e-c5651884e3e1
Faulting package full name:
Faulting package-relative application ID:


Faulting application name: Prepar3D.exe, version: 4.1.7.22841, time stamp: 0x59d67e95
Faulting module name: KERNELBASE.dll, version: 10.0.15063.726, time stamp: 0x1a9bbe0b
Exception code: 0xc000041d
Fault offset: 0x0000000000069d98
Faulting process id: 0x1e1c
Faulting application start time: 0x01d37124d91b9fe0
Faulting application path: F:\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: d9c595c0-fc16-4e9d-a20b-63803adf5258
Faulting package full name:
Faulting package-relative application ID:

[Brady Butler]

Hello,

To have us assist you further, could you please review this topic and let us know the results from following the troubleshooting steps? Also, can you provide the details of your system?

http://www.prepar3d.com/forum/viewtopic ... 2&t=123246

If the issue is determined to be caused by an add-on, you will likely want to reach out to the add-on developer for direct support. If they need any support with development, they should not hesitate to contact us.

Regards,
Brady