My first flight with these Studio drivers in P3D v5.2HF1 from LOWI to EDDK. Absolutely no issues and after parking I paused the sim for over 15 mins and all was well. Maybe it needs the aircraft to be airborne for this error to be generated.

Anyway, just wanted to report with newer drivers. TdrDelay=0 was retained in the Registry of course. DirectX Shader files were retained from previous flights but cleared out after shutting down P3D.

I’m using this topic as a log so I can report back after each flight.

Thanks  - i havent had any of these with 471.41 so far using 100-150 MHZ lowering on the GPU .

I did have a power surge issue reporting from ASUS motherboard also on my PC and it was related to a bad USB hub with its own power supply . Replaced that as well and now i have cranked everything up that would lead to a disaster with good results.

My ultimate test is right now in the MaddogX as AAL1173 towards FSDT KORD with DD Chicago installed as well.

Michael Moe

GTX1080TI FTW3

I7-4770K@4,5

32GB DDR3-2400

 

Edited September 25, 20214 yr by Michael Moe

16 minutes ago, Michael Moe said:

i havent had any of these with 471.41 so far

Michael, messages from those using different drivers could become confusing. Are you planning on installing 472.12?

1 minute ago, Ray Proudfoot said:

Michael, messages from those using different drivers could become confusing. Are you planning on installing 472.12?

Sorry i just missed the exact driver version information somehow. Thanks Ray

 

Michael Moe

Ray, I have a new Windows 10 and P3D5.2 installation. NV driver is 472.12. I have some other issues, but so far no DXGI_ERROR_DEVICE_HUNG. I have not yet made longer flights though.

@Nemo, is that flying the PMDG737NGXu?

Try pausing the sim below 10,000ft shortly after takeoff. Maybe for 5 mins or so. And do you have the TdrDelay fix in the Registry?

I’ve just posted this on the LM forum...

Suggestion to LM. Turn off the DXGI_ERROR_DEVICE_HUNG message in the next point release and let us see if there really is a DirectX issue with the graphics engine.

Maybe, just maybe it’s a false positive that is causing this trigger because there’s absolutely no evidence of a graphics problem before that message is displayed.

In any case the option to ignore it and continue doesn’t work anyway. I’m curious about how Windows will handle this error.

1 hour ago, Ray Proudfoot said:

@Nemo, is that flying the PMDG737NGXu?

Try pausing the sim below 10,000ft shortly after takeoff. Maybe for 5 mins or so. And do you have the TdrDelay fix in the Registry?

Yes it is the PMDG737NGXU. I remember I've once set the TdrDelay fix but don't know exactly where it was. Currently it is probably not set because it is a new Win10 install.

1 minute ago, Nemo said:

Yes it is the PMDG737NGXU. I remember I've once set the TdrDelay fix but don't know exactly where it was. Currently it is probably not set because it is a new Win10 install.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers" and create a key of type "QWORD (64-bit)" and name "TdrDelay" with a value of 0 as Decimal value.

0 effectively turns off the warning.

EDDK-EGBB, PMDG737-800, FL380 3nm east of waypoint LUMEN.

P3D v5.2 HF1 stopped working with DXGI_ERROR_DEVICE_HUNG message. This is with drivers 472.12.

This never happened with 471.96. I'm going to revert to those.

KSAN-KSFO, PMDG737-800, 8000 ft, 7nm before of waypoint ECHO. Paused for at least 10 min, resumed w/o any problem.

1 hour ago, Ray Proudfoot said:

P3D v5.2 HF1 stopped working with DXGI_ERROR_DEVICE_HUNG message. This is with drivers 472.12.

Ray,

Did you remember to clear the DX12 Cache after the previous crash?

Jesse

12 minutes ago, JesC said:

Ray,

Did you remember to clear the DX12 Cache after the previous crash?

Jesse

Indeed I did. The reloaded flight with the older drivers was fine.

Ray,
Curious about something here.  Try searching in your primary Windows folder for a file named "NvCamera32.dll".  It may be hidden even if you select to show hidden files.  So perform a file search to look for it.  If you find it, rename it with a leading underscore in the file extension.  ex ._dll so that Windows will not use it.  Then test for the issue with P3D and see what occurs.  I believe that file is related to the latest nVidia drivers and it has caused issues elsewhere.

1 hour ago, fppilot said:

Ray,
Curious about something here.  Try searching in your primary Windows folder for a file named "NvCamera32.dll".  It may be hidden even if you select to show hidden files.  So perform a file search to look for it.  If you find it, rename it with a leading underscore in the file extension.  ex ._dll so that Windows will not use it.  Then test for the issue with P3D and see what occurs.  I believe that file is related to the latest nVidia drivers and it has caused issues elsewhere.

Thanks Frank. Unusual suggestion but one worth trying. It will be with the earlier drivers, not these.

Anyone else done this?