5 hours ago, Ray Proudfoot said:

Grgghh! DXGI_DEVICE_HUNG after hours of problem-free flights. There must still be some bugs in v5.2HF1.

One reason why this error is annoying is that it is tricky to pinpoint the exact cause. Ever since the first cases of the DXGI hung error came up, I have never seen LM acknowledging that this problem can happen on some systems, less alone providing a solution to it.

Some argue that P3D is not to blame, since this error happens with some other games as well (just Google it), so Nvidia and their drivers must be the culprit. However, this error doesn't happen with all games (including FSX and MSFS if I am not mistaken), so Nvidia may argue that it is the fault of the software after all. There must be some problem with the interaction between the OS and the GPU driver, but it's too bad that neither Nvidia nor LM want to dig deeper into it.

I have been wondering if this error occurs, why is it simply not possible to reset the GPU driver without crashing the sim from Windows 10 side?

@G-YMML1, I’ve had this PC since October 2018 and used P3Dv4 for 2.5 years at 4K resolution. Not one DXGI error in all that time.

In March 2021 I installed v5 and my first DXGI error occurred the following day. That was a different DXGI error to the current one and was related to switching vehicles in the sim.

But this DEVICE_HUNG is definitely related to DX12 and v5. You may well be right that 4K is a factor but the fact that my GPU rarely goes above 60% load suggests 4K is not imposing an excessive load.

Why would I get a DXGI 15 mins after takeoff, reload the flight and complete it 1.5hrs later with no further issues? It’s totally illogical.

2 minutes ago, Ray Proudfoot said:

@G-YMML1, I’ve had this PC since October 2018 and used P3Dv4 for 2.5 years at 4K resolution. Not one DXGI error in all that time.

In March 2021 I installed v5 and my first DXGI error occurred the following day. That was a different DXGI error to the current one and was related to switching vehicles in the sim.

But this DEVICE_HUNG is definitely related to DX12 and v5. You may well be right that 4K is a factor but the fact that my GPU rarely goes above 60% load suggests 4K is not imposing an excessive load.

Why would I get a DXGI 15 mins after takeoff, reload the flight and complete it 1.5hrs later with no further issues? It’s totally illogical.

Have you tried reseating the GPU and cleaning the contacts? I recall @SteveW recommending that after a technical explanation that I don't remember and probably went right over my head! 😜

4 minutes ago, Afterburner said:

I have been wondering if this error occurs, why is it simply not possible to reset the GPU driver without crashing the sim from Windows 10 side?

It’s possible the Registry fix does allow the card to recover before the error is trapped by P3D.

I agree it’s mystifying and with the complexity of modern games and hardware, increasingly common. MSFS is still DX11 and as far as I know doesn’t suffer this problem.

2 minutes ago, kevinfirth said:

Have you tried reseating the GPU and cleaning the contacts? I recall @SteveW recommending that after a technical explanation that I don't remember and probably went right over my head! 😜

Nope. Seems a long shot and not one I’ve seen with a DXGI_DEVICE_HUNG search on google. Why would it start the day after P3Dv5 was installed if it was a hardware issue? Huge coincidence.

I’ve never cleaned the contacts on any PC in 30 years.

This is the suggested fix I’m referring to. Seems to have solved the issue in P3Dv5 for Airbus users...

https://forums.flightsimlabs.com/index.php?/topic/29142-dxgi-error-device-hung/&do=findComment&comment=233626

6 minutes ago, Ray Proudfoot said:

This is the suggested fix I’m referring to. Seems to have solved the issue in P3Dv5 for Airbus users...

https://forums.flightsimlabs.com/index.php?/topic/29142-dxgi-error-device-hung/&do=findComment&comment=233626

Did you set it to 0, 60 or 120 ?  I set to 60 initially and got the error again, now trying 120, lets see what happens.

7 minutes ago, MarkW said:

Did you set it to 0, 60 or 120 ?  I set to 60 initially and got the error again, now trying 120, lets see what happens.

I’ve turned the PC off so will confirm tomorrow. Did you try 0 - the recommended setting?

Folks,

I can only assume that all of you are using 4k resolution with multiple monitors sometimes, right?

 

9 minutes ago, G-YMML1 said:

Folks,

I can only assume that all of you are using 4k resolution with multiple monitors sometimes, right?

One monitor only for me. I have another monitor on another PC connected via WideFS.

41 minutes ago, Ray Proudfoot said:

I’ve turned the PC off so will confirm tomorrow. Did you try 0 - the recommended setting?

No, I used 60 then 120, crashed both times

 

What are your max temps for a GPU? Mine are barely hit 67C with heavy OVC, multiple layers of clouds with AS. Normally they are about 55-61C 

1 hour ago, MarkW said:

Did you set it to 0, 60 or 120 ?  I set to 60 initially and got the error again, now trying 120, lets see what happens.

Mark,

Sounds like you may be referring to setting the TdrDelay rather than the TdrLevel that Ray is referring to.

Jesse

This link may help: https://docs.microsoft.com/en-us/windows-hardware/drivers/display/tdr-registry-keys

 

Edited September 16, 20214 yr by JesC

2 hours ago, MarkW said:

No, I used 60 then 120, crashed both times

But the value in the link I posted was 0. And Andrew Wilson confirmed it worked for him.

@JesC, a value of 0 effectively turns the detection off. Any value greater than 0 doesn’t. I can’t see any value other than 0 working.