DXGI_ERROR_DEVICE_HUNG Guide

[reecemj 149]

Any one tried this guide? AVIATIONLY - NO MORE CRASHES GUIDE P3D5. Its at simMarket.  I didn't post a link I think the rules here say I cant.

After using the pinned solution posted at the top I still get errors every other flight. 

[Ray Proudfoot 8,980]

Have you tried the Registry settings in the pinned DXGI ERROR DEVICE HUNG topic above? No more errors for me.

[reecemj 149]

22 minutes ago, Ray Proudfoot said:

Have you tried the Registry settings in the pinned DXGI ERROR DEVICE HUNG topic above? No more errors for me.

Yes. Put setting in last week but errors are still there.

[Ray Proudfoot 8,980]

29 minutes ago, reecemj said:

Yes. Put setting in last week but errors are still there.

Errors? Just DXGI_ERROR_DEVICE_HUNG or others?

Have you bought that guide? I’d be curious to know how he solves that particular one.

[reecemj 149]

1 hour ago, Ray Proudfoot said:

Just DXGI_ERROR_DEVICE_HUNG or others?

Both so am also looking at some recent installs also. I have not bought the guide yet. Just wanted to see if anyone else used it. LOL! It may be in the guide what we are using already.

Edited November 21, 2021 by reecemj

[Ray Proudfoot 8,980]

2 hours ago, reecemj said:

Both so am also looking at some recent installs also. I have not bought the guide yet. Just wanted to see if anyone else used it. LOL! It may be in the guide what we are using already.

Both? What’s the other? My pinned post is the guidance from Microsoft so it probably is. I doubt paying for it will reveal anything new.

[Mikenor 13]

Hi Ray - I've tried the pinned solution with no luck. I've never had any issues with P3D up until about a month ago and now cannot even get a flight started, get the error within seconds of opening the flight. This while using the exact same settings I've always used with no probs. I'm on a GTX 1080. I've even gone as far as resetting my Windows 10 3 times to no avail. I'm in flightsimming withdrawal right now and would appreciate any help anyone can give.

Thanks,

Mike

[pgde 571]

I found, other than doing the registry mods noted above, is to set the Nvidia Control Panel (NCP) to "Prefer Maximum Performance" in the Power Management Mode entry.

Edited December 9, 2021 by pgde

[Ray Proudfoot 8,980]

5 hours ago, Mikenor said:

Hi Ray - I've tried the pinned solution with no luck. I've never had any issues with P3D up until about a month ago and now cannot even get a flight started, get the error within seconds of opening the flight. This while using the exact same settings I've always used with no probs. I'm on a GTX 1080

You didn’t say what drivers you’re using. They have to be 471.96. Try those. I haven’t had a DXGI error since using those with the Registry settings.

And do as @pgdesuggests.

[joby33y 152]

OK I just set up P3D 53 this week, on a brand new i9 11900 with a 3080.   My former machine was a 8700k with a 2080Ti, and I've experienced the error on that machine as well.  Today,  I got the DEVICE_HUNG error after landing at CYVR (Dreamteam add-on scenery).  This is after doing the reg mods pinned above.  But I was on the newer 496 driver, and I use a lot of TrueEarth, and Oculus VR so I'm banging the graphics fairly hard.   I am reverting to the 471 driver and will experiment further. 

[Mikenor 13]

Thanks PDGE and Ray - will try rolling back the driver as well and report back.  

Mike

[Fiorentoni 4,253]

For me only 457.30 works without any hung error (1080ti). Seems the perfect driver for P3D.

[Ray Proudfoot 8,980]

38 minutes ago, Fiorentoni said:

For me only 457.30 works without any hung error (1080ti). Seems the perfect driver for P3D.

With or without the Registry 'hack'?

[Fiorentoni 4,253]

1 minute ago, Ray Proudfoot said:

With or without the Registry 'hack'?

Without it. Also in MSFS this is the only driver that doesn't CTD me. No idea why, might be my GPU that's a bit peculiar.

[Ray Proudfoot 8,980]

1 minute ago, Fiorentoni said:

Without it. Also in MSFS this is the only driver that doesn't CTD me. No idea why, might be my GPU that's a bit peculiar.

Okay. You have a conflict here with MSFS to be taken into account. All I can say is 471.96 with the Registry changes and 'Prefer Maximum Performance' gives me a problem-free solution.