KAB

DXGI_ERROR_DEVICE_HUNG

Recommended Posts

Hi

For the last few months I haven't been able to complete any flight using the PMDG 737NGX or the 747V2 in Prepar3D.

It always ends with this:

S4yEPGo.jpg

I have tried several GeForce driver versions. Now using the latest version, 382.05.

P3D runs smooth, not using too heavy settings

Any help would be highly appreciated.

System information:
Prepar3D v3.4.22
Window 10 Home 64 bit v1703
Nvidia GeForce GTX 670
Intel i5-4670 @ 3,4 GHz
8 GB RAM

Kjell A.

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Funny,  i also  started to get these sometimes. I never had this before.

I might think it came moving from 373.06 to 381.65. Now i am at 381.89 and so far havent seen it but still to early to state.  

Or after updating 3.4.9. to 3.4.22. Cant tell. 

 

Sometimes the nvdia controlpanel is not properly loaded during Windows start, but again have not seen it yet with 381.89.

Thanks Michael Moe 

Share this post


Link to post
Share on other sites
1 hour ago, Michael Moe said:

Sometimes the nvdia controlpanel is not properly loaded during Windows start, but again have not seen it yet with 381.89.

I've noticed that too multiple times.  In fact, I just now checked and it was only showing the 3D vision options and since I don't use 3D vision options I used windows control panel to remove all but the graphics driver and the expected complete control panel returned.

As for OP, may I suggest you take a look at your video card to make sure it's not clogged with dust. It is a five year old product now, but should work well if not overheating.

Share this post


Link to post
Share on other sites

I believe it has to do with the SLI and how P3D handles it, at least it was for me.

Share this post


Link to post
Share on other sites

I have had some of those pesky errors pop up, and I am thinking the nVidia settings panel and other software being used (nVidia inspector?), may be giving the GPU fits.

I changed the settings in the nVidia Control panel to application controlled for anisotropic filtering, anti aliasing mode, transparency supersampling 8x and so far it seems to be working.

4790K stock, GTX 970, 8GB RAM, Win 7 Pro

Running AS16 +ASCA, ORBX, PMDG, LD 767, AS airbus, MJC Q400, lots of add on airports

But what do I know?  I am not a computer guy.

Share this post


Link to post
Share on other sites
8 hours ago, KAB said:

Hi

For the last few months I haven't been able to complete any flight using the PMDG 737NGX or the 747V2 in Prepar3D.

It always ends with this:

S4yEPGo.jpg

I have tried several GeForce driver versions. Now using the latest version, 382.05.

P3D runs smooth, not using too heavy settings

Any help would be highly appreciated.

System information:
Prepar3D v3.4.22
Window 10 Home 64 bit v1703
Nvidia GeForce GTX 670
Intel i5-4670 @ 3,4 GHz
8 GB RAM

Kjell A.

I was getting this problem using P3D v3.4.22 so I went back to v3.3.5 and it stopped.

 

Share this post


Link to post
Share on other sites
15 hours ago, StewCal said:

Started for me after installing FSLabs A320.

+1

Share this post


Link to post
Share on other sites

I only get this error now after a certain, but variable number of switches between full and windowed screen viewing. I just save now before switching and this problem is now just an annoyance. Doesn't seem to matter what aircraft.

Bill Barrette 

Share this post


Link to post
Share on other sites

For now, downgrading Prepar3D from version 3.4.22 to version 3.3.5 have solved the DXGI-error. So far I have completed several flights!

Share this post


Link to post
Share on other sites

I think it related to SLI? I dont get it with single card. 

Thanks Michael Moe 

 

 

Share this post


Link to post
Share on other sites

Hi everybody,

I am using P3D v. 4.3 with Intel i7 3,33 GHz, 24 GB RAM, Win 7 Ultimate 64Bit and single NVIDIA GeForce GTX 960. When I am flying FSLabs A320 or any of the standard airplanes of P3D and sooner or later I am getting this error message (DXGL_ERROR_DEVICE_HUNG...) when I switch to one of the outside views. With any of the (virtual) cockpit views I can fly the airbus and other planes for hours without any problem. I have obeyed numerous instructions to solve the problem (including installing another Graphics Card, clean installations of several graphics drivers, modifying options in P3D, deinstallation of "Spotlights", changing pagefile and so on), but everything without any success.

I should be very grateful for any help.

Best regards

Paul

Share this post


Link to post
Share on other sites
Posted (edited)

A google search helped me to solve it, the solution was somewhere in the microsoft forums. But I absolutely cant remember where or what it was, I‘m afraid. But this here is the PMDG forum and as lobg as nobody can provide a master solution this is probably not the right room for that, all above when you get it with FSLabs addons..

Edited by Ephedrin

Share this post


Link to post
Share on other sites

Sounds a lot like a graphics driver issue. Definitely not one of ours if you're getting it with other aircraft.

You're likely better off posting in a P3D-specifiic forum.

Share this post


Link to post
Share on other sites

I fixed this by using an nvidia driver from May.

michael chandler

  • Upvote 1

Share this post


Link to post
Share on other sites
3 hours ago, scandinavian13 said:

Sounds a lot like a graphics driver issue. Definitely not one of ours if you're getting it with other aircraft.

You're likely better off posting in a P3D-specifiic forum.

Yep, a driver issue. NVIDIA, Windows and P3D are not playing well together. Easiest fix is a rollback, but that may affect other games and applications that depend on it.

Share this post


Link to post
Share on other sites

Long story short, its a APP and driver issue. Or rather how they talk to each other. Some older Drivers work and resolve that issue or update to the latest. Just make sure you have the latest installers as well from the developers. I have the latest FSLabs/PMDG, etc etc and latest NVIDIA and no issues with P3Dv4.3

 

Share this post


Link to post
Share on other sites

rollback to 388.71 and it will fix the issue

Share this post


Link to post
Share on other sites

I rolled the driver version back to 397.31 and that ended it. Still on P3D v4.2.......

It also first appeared after first running the new A320-X. It was not happening with PMDG a/c, so yes, better let them know in the other vendor's forum. 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now