3 minutes ago, pgde said:

TBH, I don't know how a 1060 can run 4k at any normal level. My 1080ti has issues at certain times. Try backing your resolution down to 2560x1440 (QHD) and see if that helps stability. Yes, you won't have as sharp a picture but this is a test....

OP is running 1080 Ti.

Edited November 1, 20196 yr by Evros

1 minute ago, Evros said:

Sure you posted in the right topic? OP is running 1080 Ti at 1920x1080.

Wow, a senior moment :) My apologies and I deleted the text....

Regards,

P.

13 minutes ago, pgde said:

Wow, a senior moment 🙂 My apologies and I deleted the text....

Regards,

P.

Haha, same from me. For some odd reason I typed his resolution to be 1080p, while it is 4K. Happens with all of us.

1 hour ago, Evros said:

It could be, but I don't really want to go with this option until we have exhausted other ones. Lets start with you posting proper Event Viewer error. The one you posted previously doesn't seem to be properly formatted and is missing some crucial information.

Open Event Viewer and from the 'Summary of Administrative Events' open 'Error' drop down menu. From there, duble click on 'Application Error' (Event ID 1000). From there, look up your latest entry containing Prepar3D.exe and that is probably your latest crashed session. If you select it, then general information becomes available, and that is what you should paste here. I'll post an example below.

Faulting application name: Prepar3D.exe, version: 4.5.13.32097, time stamp: 0x5d8abf93
Faulting module name: util.dll, version: 4.5.13.32097, time stamp: 0x5d8ac1b9
Exception code: 0xc0000005
Fault offset: 0x0000000000026137
Faulting process id: 0x38c
Faulting application start time: 0x01d58dc63d2a83b5
Faulting application path: D:\Prepar3D\Prepar3D.exe
Faulting module path: D:\Prepar3D\util.dll
Report Id: b751fc6e-034b-433a-a398-78e29e3b8d10
Faulting package full name: 
Faulting package-relative application ID: 

You can also use third party log viewers; AppCrashView seems to be popular choice around here, but I don't find it necessary if same thing can be achieved with built-in facilities and full error stack is not needed.

Thanks i really appreciate this to find a solution but i gave you all information i got from it ,

I dont understand,

Never the less i whent from KORD to KEWR with only 1 CTD with Vpilot in the FSLa319 .(reducing to 2K)

Michael Moe

Edited November 1, 20196 yr by Michael Moe

I see. Could be that you have minimal error logging enabled or a Windows edition where it is limited by architecture. In that case, you may try AppCrashView as it might give some more information, possibly.

Another thing I like to do in this case is to delete prepr3d.cfg, let the program rebuild it and then test with the fresh ones. I'm not sure if you have tried it yet.

On 11/2/2019 at 1:21 AM, Evros said:

I see. Could be that you have minimal error logging enabled or a Windows edition where it is limited by architecture. In that case, you may try AppCrashView as it might give some more information, possibly.

Another thing I like to do in this case is to delete prepr3d.cfg, let the program rebuild it and then test with the fresh ones. I'm not sure if you have tried it yet.

Hi again

I got at Kernelbase.dll error and now this one

 

Thanks Michael Moe

Prepar3D.exe

4.5.13.32097

5d8abf93

USER32.dll

10.0.18362.449

9c993529

c0000005

00000000000130ee

30ac

01d59221d1e40d08

F:\P3DV4\Prepar3D.exe

C:\WINDOWS\System32\USER32.dll

fc0820ad-362e-4ca6-8361-1f6e928a62d0