-
Please see the most recent updates in the "Where did the .com name go?" thread. Posts number 16 and 17.
DXGI_ERROR_DEVICE_HUNG Old friend back...
- Thread starter DaveQ
- Start date
Hi Dave
I've experienced the problem for the last several months with both 5.1 and now 5.2. For me it occurs consistently when I attempt to "disable" VR - Oculus Rift S. Have attempted many fixes - some appeared to work for a bit but the problem has always re-occurred. I have read about another couple of fixes over on the P3D forum under this same topic but have not tried them. I'm also given to understand that LM is planning a hot-fix intended to help. Wish I could report something more concrete.
Warren
I've experienced the problem for the last several months with both 5.1 and now 5.2. For me it occurs consistently when I attempt to "disable" VR - Oculus Rift S. Have attempted many fixes - some appeared to work for a bit but the problem has always re-occurred. I have read about another couple of fixes over on the P3D forum under this same topic but have not tried them. I'm also given to understand that LM is planning a hot-fix intended to help. Wish I could report something more concrete.
Warren
BendyFlyer
Charter Member
Dave sorry I have never seen this problem but I run an Intel CPU with an NVIDIA GPU.
Hi
Have a look here and pearhaps, you can try the fix:
Regards
Michel
https://www.prepar3d.com/forum/viewtopic.php?f=6312&t=142590
Have a look here and pearhaps, you can try the fix:
Regards
Michel
https://www.prepar3d.com/forum/viewtopic.php?f=6312&t=142590
dhazelgrove
Charter Member
wombat666
Administrator
I had this happen a few times so I rolled back the NVIDIA drivers and it went away.
That was earlier this year and I've since upgraded to a 3090 GPU, aside from a single OOM message (on a 24G GPU!) I've yet to rejoin the fold!
This looks like it might help but so did a number of suggestions.
The problem was all over the Interweb and it drove LM bat-chit crazy.
That was earlier this year and I've since upgraded to a 3090 GPU, aside from a single OOM message (on a 24G GPU!) I've yet to rejoin the fold!
This looks like it might help but so did a number of suggestions.
The problem was all over the Interweb and it drove LM bat-chit crazy.
CG_1976
Ret. US Coastie/RCAF
I had that issue with this new Dell Computer. However Dell's Lockheed person took care of via remote. According to Dell it was the Wacky ATI driver situation in case the Alienware center and ATI center having a Vegas Friday night Fight match lol and P3D was the Ref getting caught in the middle of an upper cut. They cured it.
DaveQ
Charter Member
Thanks for the help Guys. I've tried the Partition Wizard fix without success; an earlier P3D forum fix also was unsuccessful. I've been out most of the day but I'll try the latest P3D particledraw.fx fix in mpns's post when I next get a chance.
Thanks again - I'll keep you posted....
DaveQ
Thanks again - I'll keep you posted....
DaveQ
DaveQ
Charter Member
Preliminary testing after altering the the ShadersHLSL/ParticleDraw.fx file indicates the problem is solved
. Will update if there's a recurrence, meanwhile awaiting the hotfix. Thanks again mpni
DaveQ
centuryseries
SOH-CM-2023
I got that with 5.1 and also now with 5.2 with a RTX 3080 and i9 10900, I can't understand why this still hasn't been fixed - it talks about Nvidia when you start P3D, so if they have some kind of Nvidia assistance, why is it still happening!
I created a post on their forum for 5.1 DXGI Hung and it ended up being many, many pages long!!
I created a post on their forum for 5.1 DXGI Hung and it ended up being many, many pages long!!
DaveQ
Charter Member
I'm still tracking this one. Pushed some sliders to the right and it came back. Deleting the P3D.cfg file fixed it. My latest guess is bathymetry which I turned on and that caused a 'fail'. But there may be other triggers as well. Running default settings avoids the issue rather than solves it.
DaveQ
DaveQ