Hi all,

I recently moved from P3D v4.5 to 5.2, and so far it's proved relatively reliable. However I was just flying KJFK-EGLL in the PMDG 744 and when descending through around 9-10k feet on arrival into Heathrow I experienced a fairly nasty Display Driver timeout which then CTD'd the Sim.

I should note that my current PC does have a few gremlins in the Graphics department (I often have to restart to avoid Display Driver Timeouts when opening video files, certain websites etc.), however these are always fixed by a restart and don't re-emerge until the next cold boot. I don't believe this is responsible for the error at hand here, especially since this never effected my v4 install beyond when attempting to record footage with external software. Also normally while unrecoverable, P3D would give the timeout notification, whereas in this case it just crashed out.

There are 2 entries in Eventviewer to draw on

A .net runtime error:

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 00007FFDD9964D16

And the P3D error itself:

Faulting application name: Prepar3D.exe, version: 5.2.22.27615, time stamp: 0x60db69bf
Faulting module name: amdxc64.dll, version: 27.20.22001.14011, time stamp: 0x60cbe0e6
Exception code: 0xc0000005
Fault offset: 0x0000000000344d16
Faulting process ID: 0xd58
Faulting application start time: 0x01d7cc9ba1b877e1
Faulting application path: E:\Lockheed Martin\Prepar3D v5\Prepar3D.exe
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\u0368925.inf_amd64_05ef22929fd9ebfc\B368707\amdxc64.dll
Report ID: c1b4857e-2ba8-465a-b025-f6e5c3f250f8
Faulting package full name: 
Faulting package-relative application ID: 

Just to confirm I'm running a Ryzen 5 5600x on the CPU end and my GPU is an RX-570 8GB

The exception suggests something tried to read a portion of memory it wasn't supposed to but it isn't particularly narrowed down. Since I have done longer flights in the sim without this happening it leads me to wonder whether scenery might be involved, I have ORBX Global installed but nothing else beyond the airport scenery (in this case Simwings EGLL). However given the gremlins I have had with this system I can't rule out a driver problem, I've updated them and will try to bring myself to replicate the problem in the next few days. Could also be an EA issue.

If anyone has any pointers as to what may be causing this/ what may help prevent this happening again I would be more than grateful.

 

Many thanks

Martin

Have done some troubleshooting and it seems this is a classic Win10 DX12 DXGI issue. I was having the timeout when loading the MaddogX MD88 into KATL & changing view. Upon restarting and clearing my DirectX Shader cache this has stopped happening.

Not an ideal fix but at least something to keep in mind for the future.

Edited October 30, 20214 yr by SimeonWilbury