Hello I was flying from LPPT to LEPA using P3Dv5 and using Prosim737.  About 20 minutes into the flight I noticed that the sound of the engines was still going on,but the image was frozen. It did not continue. Afyter a while I stop the simulation. Now if I restart P3D I get the first screen with the F22 and the default airport, I just kit Ok. it starts loading and about 75% later it crashed to the desktop.

 I looked at Windows event viewer, and it shows a crash of P3dV5 due to fault with the file Kernel.dll.

I don't think is an issue with the system, as I have a pretty decent machine

I9-10850K not overclocked, ASUS Maximus X!!, 32 GB of DDR4-4000 RAM, GTX 1080TI.

Thanks and regards

Juan

 

I've had this happen a couple of times usually after I have restarted P3DV5 numerous times when I'm testing a mod that I have done.  In both cases I have shutdown my computer and started it up again. In both cases, the first time I try to start P3DV5 after restart it will CTD and after the first try it will work ok.  Go figure.

Hi there,

"Delete P3D generated files" feature, solved a similar issue I encountered in the past with V4.

https://youtu.be/Wj9QdURzbIY

Cheers,

Edited October 23, 20205 yr by ffantasy67

I had that specific problem of screen frozen but sound continues only once in P3Dv5 and I suspect it was caused by a conflict I had with Simmconnect as I inadvertently had two live map/tracking utilities running at the same time. However I was able to restart P3D without any issues.

Did you make any modifications or add anything prior to starting your most recent flight. This may give you a clue.

Also P3D may fail to start if it detects a bad scenery. I usually use Lorby Add on Manager to pick up those sorts of issues.

13 hours ago, johncott said:

I've had this happen a couple of times usually after I have restarted P3DV5 numerous times when I'm testing a mod that I have done.  In both cases I have shutdown my computer and started it up again. In both cases, the first time I try to start P3DV5 after restart it will CTD and after the first try it will work ok.  Go figure.

same here.

delete the "previous.flt" file.  a do a PROPER reboot of  the pc 

using alt f4 at the desktop until you see a box coming up tellling you to reboot or restart,  ie dont use click windows icon / start , power  etc etc , using the alt f4  until you see the box, then reload p3d she if that fixes it.

I have witness issues like this after WIN10 updates, aswell.

For months since V5 HF2 is out i made hours of flying without a single CTD. Then i rember last 2 months there where some Windows updates also for VCruntine and Netframework installed allong with the automatic updates from MS. After that i got regular CTD with several modules like Kernellbase.dll, VCruntime.dll, and terrain.dll etc. 

After several repair installations of Simconnect, Nvidia Drivers (because Netframeworks relation) and the different VSRuntimes on the System. The CTD´where all gone and i could fly for the last 4 weeks without any issue. 

Beginning of this week there came several other Windows updates along, and now guess what...again CTD´s. For me it seems, that´s maybe a good idea to reinstall those parts of additional softwaremodules which could be effected by an Update of the OS, like SimConnect, Netframework, VC etc.

I had some kernelbase errors as well. Nvidia drivers seem to cause this 

 

A CTD or a shutdown anomaly can sometimes leave your sim config in an unstartable state, not to mention unruly add-on installers or the occasional fat-finger mistake.

I use Lorby-SI's freeware P3D Addon Manager to take a snapshot of my config environment after pretty much any config change.  The Backup feature is a one-click affair that makes a copy of the important config files in P3D, and restoring it back to that state is just as easy.  It's saved me from hours of butt pain more than a few times.

It only takes one go at trying to troubleshoot o a problem like this to see the HUGE value of that sort of backup tool.