January 9, 201511 yr The best thing to do is to reinstall MyTrafficX 5.4b or c and do NOT go on the developers website and install the 2012 or 2013 AI schedule. Use the default that comes with MyTrafficX which is absolutely awesome and provides even more AI traffic. Once installed in FSX, copy the MyTrafficX folder to P3DV2, make the change in the P3D.cfg, and add the scenery to your Scenery Library and put it just above Propeller Objects. Go Fly. I reinstalled mine to 5.4b and have not had any problems whatsoever with CTD's since then (about 8 months ago). Best regards, Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS) I7 8086K 5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10
January 9, 201511 yr The schedule change only addresses the ntdll.dll error in P3d. You might want to check your Windows error event log to see what specific error that you are getting. Good idea JaBoomBoom I will check my error log and see what the culprit was Once installed in FSX, copy the MyTrafficX folder to P3DV2, make the change in the P3D.cfg, and add the scenery to your Scenery Library and put it just above Propeller Objects. Go Fly. Unfortunately I have MyTraffic3D so I'm not sure if that solution will work but I do have FSX still installed so I'll give it a go, thanks for the tip! Here's what I'm getting out of the event log, it's all greek to me Faulting application name: Prepar3D.exe, version: 2.4.11570.0, time stamp: 0x542314d3 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0xd46cef65 Faulting process id: 0x176c Faulting application start time: 0x01d02ba275b50ecd Faulting application path: F:\Lockheed Martin\Prepar3D v2\Prepar3D.exe Faulting module path: unknown Report Id: d5047c77-979e-11e4-8e71-e0cb4ef9260d Fault bucket 144596503, type 19 Event Name: BEX Response: Not available Cab Id: 0 Problem signature: P1: Prepar3D.exe P2: 2.4.11570.0 P3: 542314d3 P4: unknown P5: 0.0.0.0 P6: 00000000 P7: d46cef65 P8: c0000005 P9: 00000008 P10: Attached files: C:\Users\Paul Cordogan\AppData\Roaming\Lockheed Martin\Prepar3D v2\Prepar3D.cfg.txt C:\Users\Paul Cordogan\AppData\Roaming\Lockheed Martin\Prepar3D v2\dxdiag.txt C:\Users\Paul Cordogan\AppData\Roaming\Lockheed Martin\Prepar3D v2\scenery.cfg C:\Users\Paul Cordogan\AppData\Roaming\Lockheed Martin\Prepar3D v2\fdr.dat C:\Users\Paul Cordogan\AppData\Roaming\Lockheed Martin\Prepar3D v2\DLL.XML C:\Users\Paul Cordogan\AppData\Local\Temp\WER55CE.tmp.WERInternalMetadata.xml These files may be available here: C:\Users\Paul Cordogan\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_126e3d69f0b07a16ff11188b5259669c73a2_08827649 Analysis symbol: Rechecking for solution: 0 Report Id: d5047c77-979e-11e4-8e71-e0cb4ef9260d Report Status: 0 Paul Cordogan
Create an account or sign in to comment