Hiya guys,

I have recently had new build PC and gone over to P3Dv4. Lots of addons including usuals such as ORBX. At least one a day I am getting app hangs. It will never CTD but likewise after 5/10 mins still have not recovered. Any ideas from the below log?

Many thanks in advance for your help.

Chris

 

Fault bucket 129584528079, type 5
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: Prepar3D.exe
P2: 4.1.7.22841
P3: 59d67e95
P4: 0000
P5: 134217984
P6: 
P7: 
P8: 
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER479C.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER47AB.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER47AC.tmp.txt
\\?\C:\Users\chris\AppData\Local\Temp\WER522C.tmp.appcompat.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppHang_Prepar3D.exe_7dbfdbe783a886a39b4204a944aeaa4ab578d_911d388a_1ee25a59

Analysis symbol: 
Rechecking for solution: 0
Report ID: b0ec380d-0983-4a80-b345-9bec7980201c
Report Status: 268435456
Hashed bucket: 67d6e0476771645646fd44e30e8461e6

 

The program Prepar3D.exe version 4.1.7.22841 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
 Process ID: 23a4
 Start Time: 01d39ce1fd51e647
 Termination Time: 33
 Application Path: C:\P3D\Prepar3D.exe
 Report Id: b0ec380d-0983-4a80-b345-9bec7980201c
 Faulting package full name: 
 Faulting package-relative application ID: 
 

The Problem Signature, P7, is blank and that usually tells us why it crashed.  App Hangs are impossible to diagnose on forums.  As stated in the AVSIM CTD Guide (link in my signature), page 10, you should first rename your p3d.cfg to p3d.cfg.off, restart P3D and let it rebuild.  That fixes 90% of the crashes as a tweak in the config or high settings usually are the culprit.  If that does not fix it, then renaming the dll.xml (two of them) would be next.  One of the modules could be corrupted, missing, or out of date.  For instance, I have many Carenado aircraft (they come with the default P3D too) and they keep entering the 32 bit version of the CMeteoXml.dll (think their weather radar module).  If you have the P3Dv4.1, the correct version should be CmeteoXmlx64.  Same with the Carenavigraph.dll.  The FSUIPC will freeze up P3D too if not the proper version or you have it saving flights during a flight session.  As you can see, there are so many possibilities for the total destruction of your enjoyment of flight simulating with the more add-ons installed, it is mind-boggling.

Christinney, 

I too went through the anguish and pain you are now experiencing. Jim mentions the AVSIM CTD Guide which is very helpful. In addition, I downloaded a free program called 'Driver Booster' (I think that's it) that analyses the currency of drivers. This is what ultimately solved the issue for me. 

2 hours ago, Les Parson said:

I downloaded a free program called 'Driver Booster'

The info about this freeware is in the guide too on page 15.