3 minutes ago, Bigmack said:

That's your problem AI suite, It pretty much hosed my FS installs. I ended up dumping everything and reinstalling win10, then my simulators again. Have not had any issue since. I use AI overclock in the BIOS to over clock my system.

You’re the first person to point the finger at AI Suite. Any evidence to substantiate this claim?

Can you describe “hosed”?

27 minutes ago, Bigmack said:

That's your problem AI suite, It pretty much hosed my FS installs. I ended up dumping everything and reinstalling win10, then my simulators again. Have not had any issue since. I use AI overclock in the BIOS to over clock my system. Also been using 471.96 since release. No issues. I see there's a new release 472.12 but I think I'll stick with what's working.

ive also once before had ai suite on and ran the config tool that does the CPU, RAM, GFX Card, and fans.  It was giving me dxgi errors.  So did exactly the same.  did the overclock in BIOS.  No more dxgi errors for me.  and ive had a ton of them before in the past.

i mentioned it before eariler up the thread.

ai suite

afterburner

asus gpu tweak

all the above caused me dxgi errors when overclocking the GFX CARD on my 1080ti but im not an IT guru, so what would I know.  

but with nearly 17000 hours on the sim over the years, all those 3 software items have caused me DXGI errors.  Ive had more DXGI errors than hot dinners,  all gone once i removed those 3 things.

Sorry Ray,  this guy mr Bigmack is onto something here im afriad. 

Edited September 25, 20214 yr by fluffyflops

I’ll give this some thought. I’ll check DXGI errors compared to when I installed AI SUITE.

Back in July Bob was able to overclock his 8086K even more than mine. He hasn’t reported any DXGI issues so I’m beginning to think it’s not an overclocking issue.

Why would it cope fine at EGLL with 100+ Ai but not at FL350 over open terrain with far less demand on the system?

6 hours ago, Bigmack said:

That's your problem AI suite, It pretty much hosed my FS installs. I ended up dumping everything and reinstalling win10, then my simulators again. Have not had any issue since. I use AI overclock in the BIOS to over clock my system

That's really all AI Suite does if you use its automatic mode to find the best stable settings. I let it do that then went one of its steps back to ensure some headroom. But yes, you can mess things up real good if you mess with its sliders yourself, as of course you can directly in the BIOS.

Annoyingly (for me) AI Suite does not touch the memory clocking or voltage, nor the GPU -- it only deals with CPU clocks and voltages. I had to venture into the BIOS to turn my memory clock down from its nominal 4500 MHz rating to 3900 MHz in order to achieve my stable setting of 5.5 GHz on all cores.

My RTX Titan GPU was overclocked at source so I've not touched that.

BTW, I've never had any DXGI failures -- one of the lucky ones i assume! 😉

Pete

 

Edited September 25, 20214 yr by Pete Dowson

I'm not in the mood to continue investigating possible solutions to this problem given how widespread it is. If the fix suggested in this link is good enough for a co-developer in FS Labs it's good enough for me.

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

1 hour ago, Ray Proudfoot said:

If the fix suggested in this link is good enough for a co-developer in FS Labs it's good enough for me.

Hi Ray,

This link references TdrLevel=0 and  yet much of this thread has been concentrating on TdrDelay=0 (although TdrLevel has been mentioned). Is this apparent inconsistency simply reflecting our confusion as to what we should be doing or, as you have discovered, while potentially helpful, neither can be regarded as being the final solution?

Regards,

Mike

5 minutes ago, Cruachan said:

Hi Ray,

This link references TdrLevel=0 and  yet much of this thread has been concentrating on TdrDelay=0 (although TdrLevel has been mentioned). Is this apparent inconsistency simply reflecting our confusion as to what we should be doing or, as you have discovered, while potentially helpful, neither can be regarded as being the final solution?

Regards,

Mike

Mike, good spot. I've researched this so much I've done my head in.

I will try TdrLevel=0 on my next flight as searching for the two commands shows that TdrLevel seems to fix it for more people.

Hi Ray,

Oh, I do understand and without wishing to compromise further your remaining normal neuronal synaptic functionality, I came across this on the Adobe website:

“Note that these Keys can be reset to their default value by Windows updates or GPU Drivers updates.”

Something to keep in mind perhaps?

This is an interesting and informative short thread:

https://www.reddit.com/r/nvidia/comments/4y4202/for_those_of_you_having_frame_freezing_or_driver/

It is 5 years old, but much of it remains relevant.

Unfortunately (?) it introduces another registry entry: TdrDdiDelay which may not be relevant for our purposes as it specifies the number of seconds that the OS allows threads to leave the driver. After a specified time, the OS bug-checks the computer with the code VIDEO_TDR_FAILURE (0x116).

Regards,

Mike

 

Mike,

Thanks for the link. Spoilt for choice! For now I’m going to use TdrLevel as that is what worked for FSL Airbus users.

I completed my flight from Palermo to Salonika without issue.

Just had a strange situation 17 mins outbound from LGTS heading north. There was a buzzing noise from the system and P3D froze for a couple of seconds. I was expecting a CTD but it unfroze and continued. No errors or warnings in Event Viewer.

With TdrLevel=0 now set I'm wondering if that prevented a DXGI problem.

Hello Ray,

had this behavior a while ago, updating the sound driver of my ASUS-Board solved this issue for me.

Regards

18 minutes ago, Whenmaker said:

Hello Ray,

had this behavior a while ago, updating the sound driver of my ASUS-Board solved this issue for me.

Regards

First time in the 3 years I've had this PC. If it happens again I'll do as you suggest.

Interesting comments on the AI Suite. I don't have it installed and have not overclocked my video card but was still getting these errors.  I don't have enough flights completed to confirm if the problem is fully resolved after a complete P3D reinstall.

24 minutes ago, Ray Proudfoot said:

First time in the 3 years I've had this PC. If it happens again I'll do as you suggest.

I have had the dreaded buzz before a couple of times and each time is was the harbinger of bad fortune. (CTD)

So I think you were very lucky. Maybe your TdrLevel was the antidote.