MatthiasKNU

Yes, a visual only update would be really great! I would pay for that, too. I think there is no need of programming anything new, the 737 is great.

Good evening, yes, that was me. I have exactly this problem, normally I have the upper visibility limited to 60 nm but now after updating to P3Dv3.2 and updating ASN I have this problem. And I am not the only one, I know a few others with this problem. I think this problem is related to ASN and so I hope that this will be fixed soon!

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

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...

Yes, I have Road traffic allways off, so this was not the reason, Anyway, P3D is running again! Thank you all very much!

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

A flight without FSUIPC didn't change anything...

Good morning, no, I am not using the MSI Gaming App. I have a clean windows 10 installation with no "tuning" program installed. I don't think that this missing .agn file is causing my CTDs. But what about this strange APL-entry and the hardware id which is not found?

Hm, the Process Monitor is working perfect and P3D is working perfect with process monitor run (except of my CTDs...). Only EZCA won't run with procmon active...

Yes, i tried a flight without ASN. But I will try that tomorrow again. I will try a flight without FSUIPC tomorrow, too. I let Memtest running a half day without any errors. I will try a flight with other RAM modules.

No, i am not using dynamic reflections, this slider is set to off

Hello Jim, Thank you very much for your answer. I thought that EZCA makes problems, too. But I have these CTD when EZCA is completly removed from my computer, too. The EZCA crashes are another problem, I think. They have nothing to do with my P3D-CTDs. Yes, you are right, of course I can't "reinstall" DirectX. I ran the DirectX complete setup, checked for errors and so on. Like i have written above, I tried reinstalling complete Windows and Prepar3D, which didn't solve my CTD-problem... And yes, I thought that the drivers may be a problem, too, but I have for every device the latest win10-driver installed... Thank you anyway!

Hello all, First of all, I am quite new to these forums and sorry for the very, very long post... I have sine 2-3 weeks a huge CTD-problem, which a can't solve... The most time of the flight everything works fine but sometimes P3D suddenly freezes. The only possibility to close P3D is via the Task Manager. When P3D crashes, dxdiag.exe shows up in the ProcessHacker for some seconds. Starting dxdiag manually shows no errors. There is no entry in the event viewer. When P3D crashes the dxdiag process shows up for some seconds. The video card memory is not full. The GPU temp is around 60 - 65 °C and I have a 750 W power supply. Even a complete clean install of Windows10 and P3D doesn't solve my problem... I tried to locate the problem and here is the result... 1. The problem only appears after more than 3 - 3 1/2 hours inflight 2. The problem does not appear when I leave an aircraft more hours "ready for takeoff" standing on an airport 3. The problem does appear at all aircraft 4. In the AppCrashView I only get an entry "AppHangB1" 5. Starting dxdiag manually shows no errors. 6. In the dxdiag.txt I have 9 errors of EZCA. P3D is started with Admin rights, EZCA not. Yesterday I tried again a flight, only with EZCA, ASN, the PMDG 737 and P3Dv3.1. No other Addon etc. was running. Again a CTD when switching on the Dome Light. But I don't have to do something to let P3D crash, P3D crashs even if I am doing absolutly nothing on my computer. I even tried a flight without EZCA, that does not change anything. Today I tried a flight with ProcessMonitor running. P3D crashed as usual, but i have a big, very big log file. screenshot number 1: The APL-Entry in the registry does not exist. The .agn-File P3D is looking for does not exist, too. The Device-Class-key does not exist. This sequence was repeated the whole time P3D is running. I found out that P3D is looking for the following registry entry: HKLM\Software\WOW6432node\Microsoft\APL and the entry "Safe Mode". screenshot number 2: Another little notice: When I am using an external view, P3D is looking for the APL-entry mentioned above. When I am using a cockpit view,P3D is looking for this hardware-ID in the second screenshot. I tried to find out this ID, this ID is existing on my computer, but has only one entry properties = 1 I tried to dissolve this hardware-ID, but I came to no result... AppCrashView screenshot: and my dxdiag.txt: http://www.file-upload.net/download-11308684/dxdiag.txt.html and the full AppCrashView protocoll of the last P3D-CTD: http://www.file-upload.net/download-11310600/AppCrashView.txt.html All benachmarks anb stresstest are working as they should, there are no problems. Memtest, Prime95 and 3D Mark are running without any errors. I tried reinstalling the video driver, reinstalling directX, reinstalling Windows 10 (format C), reinstalling P3D, nothing worked for me. And my system: I am using P3Dv3.1 and EZCA 1.18.7 with the latest variables.ini on Windows 10 pro x64. I7-5820K, MSI Z99X, Zotac GTX980 AMP Edition, 16GB DDR4 RAM I am using water settings "Medium" and I am not using any migration tool. The VAS at the time of the crash was around 2,4-2,6 GB. There is no difference between using windowed mode or fullscreen mode P3D is installed under C:\Lockheed Martin Prepar3D v3\ My GPU is not overclocked, my CPU is overclocked. Removing this OC'ed doesn't change anything, I have the latest drivers for my system. UAC and Windows Defender is disabled, i am not using any anti virus program. In the windows event viewer is no entry. Thank you very, very much in advance! Kind regards Matthias