NVIDIA GeForce GTX 1080 stopped working DXGI_ERROR_DEVICE_HUNG

[PurdueKev]

I am not getting crashes as consistently with HF1 (before it was anytime the ATC window was open, like clockwork I would get the DXGI error), but have had a DXGI error and then last night was the sim just a vanilla CTD. I am on a Titan Xp, latest drivers, 8700k.

Don't really appreciate paying to be a beta tester here...

[Martyson]

I am not getting crashes as consistently with HF1 (before it was anytime the ATC window was open, like clockwork I would get the DXGI error), but have had a DXGI error and then last night was the sim just a vanilla CTD. I am on a Titan Xp, latest drivers, 8700k.

Don't really appreciate paying to be a beta tester here...

Does vanilla CTD mean no Add-on installed?

What were you flying / doing ?

Is it repeatable?

[Sabre57]

I'm beginning to wonder if there isn't a relationship between AA and something, what I don't know, causing this error. I'm wondering because I can run the sim on 4xmsaa or 2xssaa. When I change to either 8xmsaa or 4xssaa I immediately get device hung. Texture size doesn't matter as long as I have the vram as I've run at 512, 1024, 2048 with no issues. I'm running an older card, 970 with 4gb and the latest driver.

[joefackel]

I'm beginning to wonder if there isn't a relationship between AA and something, what I don't know, causing this error. I'm wondering because I can run the sim on 4xmsaa or 2xssaa. When I change to either 8xmsaa or 4xssaa I immediately get device hung. Texture size doesn't matter as long as I have the vram as I've run at 512, 1024, 2048 with no issues. I'm running an older card, 970 with 4gb and the latest driver.

Turning up AA is much more work for your GPU, when you then get an DEVICE_HUNG its just too much for your hardware. You say you have an older card, the 970 came out end of 2014, likely your GPU has degraded over the years and thats causing hardware errors triggering the drivercrash.

[PurdueKev]

I am not getting crashes as consistently with HF1 (before it was anytime the ATC window was open, like clockwork I would get the DXGI error), but have had a DXGI error and then last night was the sim just a vanilla CTD. I am on a Titan Xp, latest drivers, 8700k.

Don't really appreciate paying to be a beta tester here...

Does vanilla CTD mean no Add-on installed?

What were you flying / doing ?

Is it repeatable?

It is with Orbx Global and openLC, and using the latest update of the F1 GTN after the hotfix. Sorry, I should have been more precise for debugging purposes, as "vanilla" is not default (although it is pretty much a common group of addons, and arguably P3D needs Orbx Base and OpenLC as a bare minimum to look at all like a modern flight sim).

The common thread seems to be when windows or gauge popups are open. Before the hotfix was with the ATC window alone open, though that has gone away after the hotfix. But each of the last two was with popups open (once for F1 GTN, once for default instrument) and trying to access menus at he same time.

[PurdueKev]

I'm beginning to wonder if there isn't a relationship between AA and something, what I don't know, causing this error. I'm wondering because I can run the sim on 4xmsaa or 2xssaa. When I change to either 8xmsaa or 4xssaa I immediately get device hung. Texture size doesn't matter as long as I have the vram as I've run at 512, 1024, 2048 with no issues. I'm running an older card, 970 with 4gb and the latest driver.

Turning up AA is much more work for your GPU, when you then get an DEVICE_HUNG its just too much for your hardware. You say you have an older card, the 970 came out end of 2014, likely your GPU has degraded over the years and thats causing hardware errors triggering the drivercrash.

And what about the users with the latest hardware who are still getting the same errors?

[DrumsArt]

Same problem here, a problem I've never encountered before.
-I'm not using the ATC window.
-GPU not over clocked.

For the moment (fingers crossed) the only thing that seems to have temporarily "solved" the problem for me (waiting for a fix) is to get back down from a version of the video driver.

I went back to the Nvidia Studio driver 442.19. Since then, I don't get this error message anymore (subject, of course).

If it helps, I noticed that with the most recent version of the driver (442.92), when I encountered the problem, Open Harware Monitor showed a 100% spike/peak in the Core GPU for a short while, I mean the Core GPU and not the Memory GPU.

Thank you and Regards,

Richard.

[Wilvanluyn]

Update. HF1 looks like it fixed the ATC window DEVICE HUNG ERROR. Flew all day max settings no issues. But with a fix there is a broke... Few times saw cars and road traffic in the sky.... Start up at gates soon as scenario loads automatic crash. So I have to start up at a cargo parking area. Some airports road traffic is crossing the runways. KJFK is one of those airports. Fresh install. No add ons


Wil

[Martyson]

I am not getting crashes as consistently with HF1 (before it was anytime the ATC window was open, like clockwork I would get the DXGI error), but have had a DXGI error and then last night was the sim just a vanilla CTD. I am on a Titan Xp, latest drivers, 8700k.

Don't really appreciate paying to be a beta tester here...

Does vanilla CTD mean no Add-on installed?

What were you flying / doing ?

Is it repeatable?

It is with Orbx Global and openLC, and using the latest update of the F1 GTN after the hotfix. Sorry, I should have been more precise for debugging purposes, as "vanilla" is not default (although it is pretty much a common group of addons, and arguably P3D needs Orbx Base and OpenLC as a bare minimum to look at all like a modern flight sim).

The common thread seems to be when windows or gauge popups are open. Before the hotfix was with the ATC window alone open, though that has gone away after the hotfix. But each of the last two was with popups open (once for F1 GTN, once for default instrument) and trying to access menus at he same time.

I have not installed any (except FSUIPC6) Add-ons for P3Dv5HF1.

As for F1 GTN good to know they have an update out.
I was last still reading of problems with the F1 GTN and F1 G600 in P3Dv4.5HF2 and now there is P3Dv4.5HF3?

Maybe Uninstall the F1 GTN and scenery products to see if the basic P3Dv5 is running ok.
P3Dv5HF1 is ok on my setup.

Have you contacted your Add-on developers?

[Sabre57]

I'm beginning to wonder if there isn't a relationship between AA and something, what I don't know, causing this error. I'm wondering because I can run the sim on 4xmsaa or 2xssaa. When I change to either 8xmsaa or 4xssaa I immediately get device hung. Texture size doesn't matter as long as I have the vram as I've run at 512, 1024, 2048 with no issues. I'm running an older card, 970 with 4gb and the latest driver.

Turning up AA is much more work for your GPU, when you then get an DEVICE_HUNG its just too much for your hardware. You say you have an older card, the 970 came out end of 2014, likely your GPU has degraded over the years and thats causing hardware errors triggering the drivercrash.

And what about the users with the latest hardware who are still getting the same errors?

Well I certainly did not communicate effectively with my post. 8ms is between 4ms and 2ss. Not sure why the card would crash between them. And what I should have said was I was wondering if there's a driver issue.
Cheers.

[joefackel]

...
And what about the users with the latest hardware who are still getting the same errors?

DEVICE_HUNGS can be caused by many errors, old hardware ist just one. Google it, the range goes from overheating, unstable or to weak PSU's, overclocked hardware ..... you can suffer in MANY apps from it. From time to time you can "fix" it by editing the TDLR setting in the registry, but thats only a workaround IMO.

Heck, a few weeks ago i had it in "Citites: Skylines" and my hardware is around 1 year old.

[EmpireKicking]

...
And what about the users with the latest hardware who are still getting the same errors?

DEVICE_HUNGS can be caused by many errors, old hardware ist just one. Google it, the range goes from overheating, unstable or to weak PSU's, overclocked hardware ..... you can suffer in MANY apps from it. From time to time you can "fix" it by editing the TDLR setting in the registry, but thats only a workaround IMO.

Heck, a few weeks ago i had it in "Citites: Skylines" and my hardware is around 1 year old.

Only get the error when flying the drone LOL rest of the time works

[StephaneS]

....

[Martyson]

Hello, since the Nvidia v445.87, the Image Sharpening is not working anymore, and for you ?

Is it causing a device Hung (what this topic is about) on your P3D flight?

[YaBoi69420]

I just had the DXGI_ERROR_DEVICE_HUNG error 3 hours into a flight with the PMDG 747-400. Happened when changing between wing views. The sim had been fine for the entire flight with under 4GB of VRAM usage.

Specs:
i7-8700k
RTX 2070 Super
16GB DDR4

It's happened to me a few times now. I never had this crash in Prepar3D v4 so this is certainly a v5 issue. I didn't use the ATC panel or anything.