P3Dv3.1 strange CTDs

[MatthiasKNU 298]

I think I could solve my problem with reinstalling P3D again...

[Bob Scott 7,714]

Another possibility--from the L-M forums, it appears P3D v3.1 has a known memory leak issue with road traffic...slow but insidious impact over longer flights.  So it might be useful to try turning road traffic completely off.

 

Regards

[MatthiasKNU 298]

Yes, I have Road traffic allways off, so this was not the reason,

 

Anyway, P3D is running again!

Thank you all very much!

[HUSSAR 258]

What about hardware Matthias?  Yoke, throttle, pedals?

[MatthiasKNU 298]

Hm, yes, all...

Yoke, throttle, pedals, all from saitek.

 

Today I had again 2 CTDs. I really don't know what is causing these CTDs...

[Jim Young 2,356]

 

 

Today I had again 2 CTDs. I really don't know what is causing these CTDs...

 

You need to send us AppCrashView report or an Event Viewer Report (page 1, AVSIM CTD Guide).

 

Best regards,

[MatthiasKNU 298]

I am sorry, I don't have a report. AppCrashView and the event viewer don't show any errors...

[ETNWHVAC 4]

This is a long shot but I started experiencing CTD's after I decided to switch on BIOS the hyperthreading ON. Over clock the CPU and then CTD galore. I'm waiting to get the latest release of P3Dv3 to do a clean install see if that fixes it I have P3Dv3.3.5

[SteveW 1,792]

With HT enabled the CPU does more work in the same amount of time than it would with HT disabled. More work = more heat. An increased overclock = more work and will add more heat. If the system heat situation is far enough up the curve, you may need only a tiny increase in work to overheat it. If you've turned HT on and not considered that multi-threaded apps often start two processes per core instead of one this too will add to increase heat in the system which can lead to CTDs. You shouldn't get CTD's with a clean install and no addons.

[Jim Young 2,356]

I am sorry, I don't have a report. AppCrashView and the event viewer don't show any errors...

Respectfully, that's impossible.  An Event has to be recorded.  AppCrashView deciphers Windows Error Reporting that occur when something happens to your computer system or a software application crashes.  It provides more details.  If there is no AppCrashView or Event, then there is absolutely nothing anyone can do to help you.

 

Best regards,

[FS++ 707]

It might not be the root cause, but if you're having any doubts about P3D (or FSX), go back to basics and disable all add-ons, without un-installing them.

 

The proper way is to go to C:\Users\your_user_name\AppData\Roaming\Lockheed Martin\Prepar3D v3\ and rename "dll.xml" to "NO-dll.xml" as well as "exe.xm" to "NO-exe.xml".

 

Start P3D and load a default aircraft. See if you can get it to crash.

 

By the end of the day, you'll know whether it's related to P3D (possibly installed with an overclocked system and having a few corrupted files here and there, in which case a re-install is in order), or as is usually the case, with one of the add-ons.