February 10, 20197 yr Hi all has anyone got any idea what I can do to solve this CTD? Faulting application name: Prepar3D.exe, version: 4.4.16.27077, time stamp: 0x5bfdbb35 Faulting module name: D3D10Warp.dll, version: 10.0.16299.309, time stamp: 0xd6efb7cf Exception code: 0xc0000005 Fault offset: 0x00000000000941e7 Faulting process ID: 0xea8 Faulting application start time: 0x01d4c114d309a3d6 Faulting application path: D:\Prepar3D.exe Faulting module path: C:\Windows\SYSTEM32\D3D10Warp.dll Report ID: c3bbd775-83e9-424f-b50c-9332a41dc71a Faulting package full name: Faulting package-relative application ID: Regards, Tom
February 10, 20197 yr You will have to provide more details. The faulting module, d3d10warp.dll is a system file. A running process on Windows could have caused the crash and P3D just happened to be running when the conflict occurred. Back in the old days of flight simulation, we saw a lot of d3d11.dll errors and this was caused by an add-on called SweetFX. P3DV4 is a 64-bit system and does not support some 32-bit functions. If you have any add-ons, you might want to removed them by moving all the contents in the C:\Documents\Prepar3Dv4.4 Addon folder to a temporary location (do NOT delete). Then see if the crash(es) continue. See the AVSIM CTD Guide, especially page 10, for additional assistance. Did this occur at Startup? Did this occur while loading a flight? Did this occur while flying? What was loaded? 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
Archived
This topic is now archived and is closed to further replies.