40 minutes ago, Ray Proudfoot said:

For those still having the problem even with the Registry fix try the suggestions here...

https://www.prepar3d.com/forum/viewtopic.php?f=6312&t=140508

The best part of that thread is where someone asked "Have you contacted Microsoft" (about the DX12 Win 10 issue). As if they are going to install P3D with all of the add-ons on their computers and run elimination tests 😆

Edited September 19, 20214 yr by Afterburner

General thought. Go into bios and change auto for pci express to gen 2. Save out (F10) and restart sim. 

Its only as a last resort and surely it wont work.

Older version of P3D had an issue with this error or CTD when 1st gen gen 3 cards came out and had to be set back to gen 2 to regain compatibility from very old google sites back in the day.  

No hung error messages on my 11900k but there's obviously some other weird problems going on in which very modern hardware users might have to keep an eye on. 

Good luck on the bios adjustment.

Edited September 19, 20214 yr by 40track

I'll hold my hand up and admit I don't clean out temporary files as often as I should.

400Mb cleaned including 9.4Mb of temporary DirectX shader files. Significant? Who knows. It fixed things for one user on my earlier linked P3D LM discussion. Anyone who hasn't - it's worth doing.

 

 

tut tut Raymond lol !

This morning's test flight from KLAX to KSEA might be significant. For the first time since these DXGI errors started this has been a troublesome route but I was able to fly it without incident. Other flights up to CYVR use the same routing I've not been able to complete in the PMDG without the DXGI_DEVICE_HUNG error.

What changes? Well the 'Prefer Max Performance' is still set in NCP and I still have TdrDelay=0 in the Registry. The only change was clearing out DirectX Shader Cache yesterday.

I'm going to clear it out after each flight as part of this testing routine. Whether retaining them is significant will only become apparent after several successful flights - should that happen.

If others wish to try these three actions please report back on whether it was successful or not.

Ray, have you had a DXGI error yet with Max Performance setting and TdrDelay=0?  I am asking because it sounds like you had one, and now you want to clear the DX shader cache, but I don't recall...

14 minutes ago, Afterburner said:

Ray, have you had a DXGI error yet with Max Performance setting and TdrDelay=0?  I am asking because it sounds like you had one, and now you want to clear the DX shader cache, but I don't recall...

No. Another flight yesterday was okay and so was this morning's 3hr up to Seattle. That makes 5 good flights with that combo.

I'm now flying my other troublesome route - YBBN to YSSY. DirectX Shader Cache cleaned and PC rebooted.

 

YBBN-YSSY completed without any problems. That's 6 flights without an issue.

I think that's it. DirectX Shader files. Maybe I had a corrupt one or more causing this problem.

For now I'll keep my Registry setting and TdrDelay setting and Prefer Max Performance. If the problem has really gone away I'll make one change to those and do another set of flights. But for now that appears to have resolved my DXGI issues.

1 hour ago, Ray Proudfoot said:

No. Another flight yesterday was okay and so was this morning's 3hr up to Seattle. That makes 5 good flights with that combo.

I'm now flying my other troublesome route - YBBN to YSSY. DirectX Shader Cache cleaned and PC rebooted.

 

Have you reported to LM Ray, I would have thought it could be included in their installer so users don't need to make a registry mod.

 

3 minutes ago, kevinfirth said:

Have you reported to LM Ray, I would have thought it could be included in their installer so users don't need to make a registry mod.

I've posted on my DXGI thread there Kevin. You would hope they would monitor things and respond when appropriate. The DirectX Shaders don't appear accessible except via Windows 10 Settings. If they were in a folder then a simple batch file could be run either after a session ends or before the next one.

Regarding the TdrDelay all I've done is switch off the warning. Whether there's still a problem which is now being ignored or no problem at all because of deleting the DX shaders I haven't a clue. I'm just hugely relieved the problem 'appears' to have been resolved. I hope I don't live to regret those words. 😏

2 minutes ago, Ray Proudfoot said:

I've posted on my DXGI thread there Kevin. You would hope they would monitor things and respond when appropriate. The DirectX Shaders don't appear accessible except via Windows 10 Settings. If they were in a folder then a simple batch file could be run either after a session ends or before the next one.

Regarding the TdrDelay all I've done is switch off the warning. Whether there's still a problem which is now being ignored or no problem at all because of deleting the DX shaders I haven't a clue. I'm just hugely relieved the problem 'appears' to have been resolved. I hope I don't live to regret those words. 😏

It's interesting because I've not had a DXGI error for ages, and I also did that same mod but as it was recommended by Milviz.

Also have power set to max in NVP, but I never cleared the DX12 shaders...

3 minutes ago, kevinfirth said:

but I never cleared the DX12 shaders...

...and you have the 3090.

Just now, G-YMML1 said:

...and you have the 3090.

True, but I didn't have any significant DXGI probs with my 2080ti prior to that either?

18 minutes ago, kevinfirth said:

True, but I didn't have any significant DXGI probs with my 2080ti prior to that either?

me either with 2080Ti. I've had a lot of flights flights since July5th - none of them ended in CTD. Maybe it's a some sort of mystery specifically with 1080Ti.

37 minutes ago, kevinfirth said:

It's interesting because I've not had a DXGI error for ages, and I also did that same mod but as it was recommended by Milviz.

Also have power set to max in NVP, but I never cleared the DX12 shaders...

I wonder if it might be related to having v3, v4 and v5 installed. v4 was uninstalled a month ago but who knows how long those DirectX Shaders were sitting around.

It’s possible I’ve just been unlucky but fortunately the “fix” is a simple one.

@G-YMML1, no mystery with the 1080Ti. Just a bad file or files I suspect. 👍