June 12, 20205 yr I've CTD'd twice now in the Mad Dog X around Portland. I am thinking it's a location-based crash because one of the errors in Event Viewer points to terrain.dll. I've got Orbx Global/Vector and FlightBeam's PDX installed. Faulting application name: Prepar3D.exe, version: 5.0.24.34874, time stamp: 0x5eab3677 Faulting module name: terrain.dll, version: 5.0.24.34874, time stamp: 0x5eab35fd Exception code: 0xc0000005 Fault offset: 0x00000000000da4e4 Faulting process id: 0x39ac Faulting application start time: 0x01d6410034c68705 Faulting application path: D:\Prepar3D V5\Prepar3D.exe Faulting module path: D:\Prepar3D V5\terrain.dll Report Id: 7b867e52-7d9e-4b2e-93ab-a246adeeec43 Faulting package full name: Faulting package-relative application ID:
June 13, 20205 yr PDX works fine for me with Megascenery (no ORBX). Great work by Bill Womack. Gigabyte x670 Aorus Elite AX MB; AMD 7800X3D CPU; Deepcool LT520 AIO Cooler; 64 Gb G.Skill Trident Z5 NEO DDR5 6000; Win11 Pro; P3D V5.4; 1 Samsung 990 2Tb NVMe SSD: 1 Crucial 4Tb MX500 SATA SSD; 1 Samsung 860 1Tb SSD; Gigabyte Aorus Extreme 1080ti 11Gb VRAM; Toshiba 43" LED TV @ 4k; Honeycomb Bravo.
June 13, 20205 yr Author I looked at the event log again last night and a .NET Runtime crash actually preceded the terrain.DLL one so maybe that's the real culprit. Application: Prepar3D.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: exception code c0000005, exception address 00007FFAE661A4E4 Stack:
Archived
This topic is now archived and is closed to further replies.