I see the pinned post on the XGI_ERROR_DEVICE_HUNG crash.  I am getting this crash every time since upgrading to P3DV5.3 - rarely had it in 5.2.  I have an NdvidiaTitan X with 12 GB on it and I see I am only using 4-5 GB.  The crash usually happens after I complete a flight and am the gate just sitting there, or on a 2nd flight shortly after takeoff but during level flights.  All my flights are 1/2 to 1 hour long.  I uploaded the latest drivers from Nvidia experience. 

My question is:
 

1.  Did the fix reported here solve the problem - as it said temp fix.  no one reported on this really since.  Please tell me your feedback on its success.  I do not have the know how to use those steps, butI canhire someone to do it for me.  

2.  I wonder what causes the crashes?  any insight?   I have plenty of VRAM free - but something will cause it to rash 100% if the time after say 1 hour f flying.

3 hours ago, paulyg123 said:

I uploaded the latest drivers from Nvidia experience. 

My pinned topic mentioned the driver version. 471.96 are recommended and still used by me.

Not had the error in ages. Editing the Registry is not difficult. Just save it before you start. Here’s a simple guide...

https://www.youtube.com/watch?v=RcCuN2x8gM4

 

Ray, I appreciate your help.  Per my Nvidia Control Panel, I see the game ready driver for my Titan X Pascal card is 512.59 which is the latest one available.  Do I keep this driver?

Do you have terrain and/or Cloud shadows enabled? If yes try test without both. They do give the error here when enabled mostly.

Michael Moe

yes terrain and cloud shadows are off. I actually cranked up by settings to force a crash and still stable. I have CDU and EFB opened up on 2nd monitor and flying a PMDG 747 from KORD to KMEM with both airport as payware addons.  Getting 30 fps.  I turned down FPS unlimited to 40 fps limited- I wonder if that helps?     I have  GPU monitoring program that says my GPU is 83 dg C and does up to 97 deg C at times.  I often wonder if it is a temperature issue as I never approach the 11 Gb limit.  I mean, how does one know what is the condition that caused the error?

Edited May 4, 20224 yr by paulyg123

Another thing to consider. PMDG planes do not like to be moved to another airport in the same session. It is always better to reboot the PC between flights.

17 hours ago, Ray Proudfoot said:

My pinned topic mentioned the driver version. 471.96 are recommended and still used by me.

Not had the error in ages. Editing the Registry is not difficult. Just save it before you start. Here’s a simple guide...

https://www.youtube.com/watch?v=RcCuN2x8gM4

 

the only thing me and ray have ever agreed on.  

use 471.96 .   Not had once since

on a side not can driver  417.96 being used with ms2020,  if i decide to have that aswell as p3d until the qw 787 drops. ? 

I had a Titan X (Maxwell) and experienced this issue as well. Especially with the FSLabs A320. Following the guidance outlined here worked for me: 

 

I have since built a new flight sim PC and no longer experience the issue anymore.

Edited May 16, 20224 yr by Bnash00

I got one yesterday out of nowhere.

Reinstalled my graphic driver andu pdate to the latest one, same flight done again, no error. Weird things happen :D