Just a heads up Guys,i have never had a CTD for well over 6 months with P3Dv5,until this evening,dont know if its related (probably not) but the only thing i have changed on my PC is to update the Nvidia Driver to 516.94,nothing showed in the event viewer.

Gary Jones.

Edited August 10, 20223 yr by Benbo

Check in Event Viewer (Its a Windows app) it should tell you what caused the crash or point you to something.

Event Viewer > Windows Logs > Application. Look for "Errors".

Just now, Nocturnal said:

Check in Event Viewer (Its a Windows app) it should tell you what caused the crash or point you to something.

Event Viewer > Windows Logs > Application. Look for "Errors".

He posted that there were no entries in the Event Viewer.

1 hour ago, pgde said:

He posted that there were no entries in the Event Viewer.

Oops missed that part, my bad.

6 hours ago, Benbo said:

Just a heads up Guys,i have never had a CTD for well over 6 months with P3Dv5,until this evening,dont know if its related (probably not) but the only thing i have changed on my PC is to update the Nvidia Driver to 516.94,nothing showed in the event viewer.

Gary Jones.

Did you think about deleting the Shaders folder?

Richard.

I had some CTDs recently too, whithout any notice in the eventviewer. But since I change scenery and aircraft in the running sim, I thought this is my fault. There is a problem sometimes clicking one two times too much with the mouse on a menu causing a ctd. Since P3D5.3 HF2 is long time unchanged, I suspect rather the environment than the sim itself, e.g. Windows 11 with the updates. Something we can hardly change only hope for the better.

Always a good idea to clear the P3D compiled shaders folder when GFX related items are updated, lest you end up with things like CTD or strange happenings like this pic shows.

It's the A2A 172 prior to clearing compiled shader cache.

 

14 hours ago, Benbo said:

...but the only thing i have changed on my PC is to update the Nvidia Driver to 516.94

Gary, are you sure really? What was about Windows updates, because it was "Patchday". I suspect that many CTD´s rootcause base on WIndows itself. I can´t remember that i ever had a CTD in times of Windows 98 or XP. Sometimes there where bluescreens but very rare. Since MS introduced in Windows 7 a new architecture with user based settings, and the new roaming profiles etc. we started to get familar with those CTD´s. Most of them are caused by access violation on different MS components. This is driven by the security settings MS is setting for their system components. Especially the NET.Framework is involved in many CTD´s. The reason is just, that Windows is much too sensitive and paranoyic MS in case a program isn´t strictly following the security rules set in diffenrent tools and system data which are used by third party developers. If there is just something suspecious in the eyes of the WIndows system, a program just get terminated.

A good strategy in case of CTD´s is not to panic and re-install GPU-drivers, P3D, add-ons etc. immediatly and increase the mess. Better be patient and wait and try to use the SIM as usual. Only after a while, when CTD´s happen very frequently, the cause should be investigated very carefully. The last ever thing to do, is to re-install drivers, or P3D nor add-ons, as long you can´t say for sure their files are corrupted somehow.  

Hi Bernd,

Thanks for the advice the CTD occured when departing EDDM(which i do on a regular basis having Lufhansa as my VA)i have never in months flying out of EDDM had a CTD,yesterday changed that.I have installed the windows update which i didnt do yesterday,cleared my shaders and reinstalled the driver,i will try the flight again this evening

Gary.

4 hours ago, blaunarwal said:

I had some CTDs recently too, whithout any notice in the eventviewer. But since I change scenery and aircraft in the running sim, I thought this is my fault. There is a problem sometimes clicking one two times too much with the mouse on a menu causing a ctd. Since P3D5.3 HF2 is long time unchanged, I suspect rather the environment than the sim itself, e.g. Windows 11 with the updates. Something we can hardly change only hope for the better.

exactly! In fact most of the CTD´s are based just on very little access violations which are handled very strictly by Windows in Program termination.