3 minutes ago, Ray Proudfoot said:

Gents, the discussion has drifted away from the topic title. Keep on topic please.

@mikeymike, you have already started your own topic about your problem so please don’t hijack this one.

Ok, sorry.

i will post in my own topic.

thanks 

mike

i was reading this trhread. I also had this error after limiting my frames in nvidia console and not in p3d itself. Once i limit my frames in p3d i no longer got this problem. The downside is that my frames are 4-5 frames worse but no craches. 

So maybe try no frame limit or frame limit in p3d

Edited January 28, 20215 yr by funkyj4ever

8 hours ago, funkyj4ever said:

So maybe try no frame limit or frame limit in p3d

I'll try this, but just to let everyone know, I've just purchased and did a clean vanilla install the only thing I changed except the keybinds was Pause on task switch and went from the default medium 1024 to high 2048 that's it. Was flying the AC11 and got the error.

5 hours ago, FPStewy said:

I'll try this, but just to let everyone know, I've just purchased and did a clean vanilla install the only thing I changed except the keybinds was Pause on task switch and went from the default medium 1024 to high 2048 that's it. Was flying the AC11 and got the error.

2048 is generally a no go with a 8gb card. I stopped bothering changing that setting with my 2080. Set it to 1024 and forget it. 

Guys, just give up. There's no solution for this error. Like many people, I've tried every single tip or suggestion, nothing works. Most of the time I get this error when flying over huge cities just before landing, but then it crashes over the ocean, desert areas and so on. So it's just a random error.

7 hours ago, zecanelao said:

Guys, just give up. There's no solution for this error. Like many people, I've tried every single tip or suggestion, nothing works. Most of the time I get this error when flying over huge cities just before landing, but then it crashes over the ocean, desert areas and so on. So it's just a random error.

Pls try no frame limit 

Found this:

This is a Windows error, not a P3D error. A Google of the error message will show you this happens in programs such as Excel. It is caused by Windows momentarily disconnecting and reconnecting to your GPU. Some programs are written to recover from this, unfortunately, P3D is not. It seems by reverting to driver 432.00 you can stop this from happening.

and this:

Used to think it was vram settings related but it’s actually a windows issue. https://www.nvidia.com/en-us/geforce/forums/game-ready-drivers/13/193904/dxgi-error-device-hungremoved-fix-might-not-work-f/

https://www.google.com/amp/s/www.drivereasy.com/knowledge/solved-dxgi-error-device-hung-on-computer-easily/amp/

They state That it is an Windows error.

regards

Michael

 

 

35 minutes ago, MichaelLowl said:

Found this:

This is a Windows error, not a P3D error. A Google of the error message will show you this happens in programs such as Excel. It is caused by Windows momentarily disconnecting and reconnecting to your GPU. Some programs are written to recover from this, unfortunately, P3D is not. It seems by reverting to driver 432.00 you can stop this from happening.

and this:

Used to think it was vram settings related but it’s actually a windows issue. https://www.nvidia.com/en-us/geforce/forums/game-ready-drivers/13/193904/dxgi-error-device-hungremoved-fix-might-not-work-f/

https://www.google.com/amp/s/www.drivereasy.com/knowledge/solved-dxgi-error-device-hung-on-computer-easily/amp/

They state That it is an Windows error.

regards

Michael

 

 

Thanks for sharing Michael. What makes you so sure these issues (6year old thread at link 1 and 2 year old at link 2) are still the real cause of the present DXGI Hung error? 

I find it hard to believe. 

I am not saying this is not Windows related. But the proposed solutions must not work at present time. 

But it's good to share and try several solutions and suggestions. 

Marcus

Edited January 30, 20215 yr by mpo910

Doesn't matter if you fix the DXGI error. I thought I had mine under control. Then a week ago P3D started throwing me a totally new CTD I've never seen. Very close to throwing the towel in on this hobby, or whatever we call it. 

5 minutes ago, Chapstick said:

Doesn't matter if you fix the DXGI error. I thought I had mine under control. Then a week ago P3D started throwing me a totally new CTD I've never seen. Very close to throwing the towel in on this hobby, or whatever we call it. 

That's why we are posting here the solutions we found and also the solutions others found, to share and hope others could benefit. 

But as always, it is still necessary that those who are suffering are a bit more precisely what happend and how it happened. 

The problem in this DXGI Hung ctd is, that at the moment P3D can be the cause as well as windows, oc GPU or even Nvidia's drivers. 

I am sure P3D will solve their issues (like bathlemetry and vegetation shadows casting)....but what nvidia and windows will do......is unfortunately written in the stars.

My opinion is, that most DXGI Hung suffering simmers can solve it by them selves by following the suggestions and keeping their systems and drivers fully up to date. Combined with avoiding some settings in P3D things will work. 

I bet what will happen when MSFS will step into DX12 in about 6 to 8 months. And this combined with their other issues......my list is quite long (flight model, terrain lod, weather, lightning, system depth, ctd, etc...etc....and this are big ones).

Meanwhile flying in P3D is really enjoyable. 

So what happend at your end exactly?

Marcus

I noticed a couple things when I had several brief spates of DXGI issues.

I had Win 10 fast startup enabled, and I had a pernicious run of DXGI and black screen problems over the course of a day...further research on the problem suggested that if the driver code gets borked and fast startup is enabled, it saves out and reloads the corrupted code in the same manner as recovery from hibernation, rather than loading and initializing the driver anew.  Turning off fast startup cured those issues.  The difference between fast startup and normal startup when using an SSD for the boot drive is only a second or two, anyway. 

I had another brief run of DXGI errors in conjunction with observing some mild artifacting on the 55" 4K TV I use as a monitor.  The cursor and characters on the login window, for example, appeared mildly corrupted.  It happened through at least three restarts...ultimately power-cycling the TV instead of the computer put an end to it. 

These two issues lead me to suggest approaching this problem with the entire video system in mind--driver, video card, cable, and display.  My first action if I get one (and it's been a good while now) is to cold-boot the computer by shutting down and turning the AC feed off for ~30 sec (with the switch on the back of the PSU), as well as powering the TV off and on.  A cheap HDMI/DisplayPort cable that's on the ragged edge of carrying the significant bandwidth of a 4K connection might also be worth some healthy suspicion, especially if you went with a bargain-basement video cable or are trying to run high bandwidth video (e.g. 4K or 21:9 3440x1440 at 60Hz) with a cable that may have been designed for much slower HDMI v1.1/1.2 signals.  Long (> 6'/2m) HDMI cables need to be of very high quality for high bandwidth video.

 

47 minutes ago, w6kd said:

I noticed a couple things when I had several brief spates of DXGI issues.

 

You brought really good points in here:

• full clean OS boot
• Incapable/Capable hardware parts 

Yes, indeed. I am also thinking about replacing my 5 year old DisplayPort cable. But otherwise....my system is running and I don´t have any issues now. So I will wait a little bit more. But this must be taken into account if you are having issues.

Marcus

12 hours ago, Rob_Ainscough said:

I found a solution, so have others?  That's why we share our findings to see if they help others ... giving up is of course an option, but not terribly helpful to the intent of this thread.

Cheers, Rob.

What solution? I've read all topics about this subject and no one has ever found the solution, not even LM knows what causes this. That's why I said to just give up. This error is here for several years and even the sim developer doesn't know the solution, so it's reasonable to just give up at this point (unless I'm missing something big here).

37 minutes ago, zecanelao said:

What solution? I've read all topics about this subject and no one has ever found the solution, not even LM knows what causes this. That's why I said to just give up. This error is here for several years and even the sim developer doesn't know the solution, so it's reasonable to just give up at this point (unless I'm missing something big here).

I think here is some misunderstanding going on.

Of course this error is here for several years, it is a Nvidia/OS Error, not a P3D error. Every game or app can call this up.

There are several reasons possible for triggering this error. The bigger part is NOT P3D related. Rob found a solution for HIS DXGI error, at least for avoiding triggering his error. He provided that information to others which can eliminate this by using his solution if their cause is the same.

I think he spoke about:

I) Turning Bathemetry off

II) Disabling vegetation casting shadows

III) Updating TrueGlass and Reallight .dll to the recent version provided by TFDI directly or via ORBX.

If this issues are the cause of your DXGI Hung error, we can not tell. Because there a so many other (most of them not related to P3D) causes which can trigger a DXGI Hung CTD.

If you give up, that is a pity. You should update to a new Nvidia Driver if they come out again (latest is 461.40) because they can also be the reason!

If we would have some new findings, we would share here.

Stay tuned!

Marcus

 

Edited January 31, 20215 yr by mpo910

1 hour ago, zecanelao said:

This error is here for several years and even the sim developer doesn't know the solution, so it's reasonable to just give up at this point (unless I'm missing something big here).

You are making 2 mistakes..

1. As has already been pointed out, this problem has multiple root causes.  Complete elimination of the symptom requires each one to be successfully addressed.  Some already have been, some have workarounds and some are still under investigation or undiagnosed.  The fact that there is not one single simple solution means there is a need for further investigation, not that we should all give up and go home. 😃

2. Insufficient PMA. Just because something is hard, doesn't mean it's impossible!

Edited January 31, 20215 yr by kevinfirth