3 minutes ago, Maxis said:

Ok well it has a purpose .. give it a try .. If you ctd .. well you now know why. Im not saying that it is the reason for your ctd but for me i never install anything that i am not using and try to stick to the bare essentials. 

Hmm would an ELGATO work to capture your video ? Im not a pro at media so im probably not the one to ask but i think thats one system that streamers like to use.

I agree, I try and do the same. I'll check out ELGATO!

On 11/30/2021 at 2:42 PM, mtr75 said:

Yeah, I'd be happy if I reinstall it and get no CTDs. But the main thing is no CTDs. What's weird is I wasn't having them, didn't change anything, and then they started happening. Just one after another. It's bizarre. And what causes crashes for some people is no problem for others and vice versa. I like to think it was this regedit that did the trick.

Didn't last, by the way. Back to CTDs.

I wanted to know if people were still using this "tweak" even today ?

41 minutes ago, Axis3600 said:

I wanted to know if people were still using this "tweak" even today ?

Yes--I started loosening the delay timings like this I think as far back as the FSX days. 

Increasing the DdiDelay values gives the system some extra time to recover from a graphics backlog before it calls it quits, resets the driver and crashes the sim.

Ok, what value do you use on TdrDelay and TdrDdidelay ? 60 is still good ?

I recall applying the tweak and don’t recall having a reason to uninstall it so it seems to be happily doing its thing in the background.

It's not going to hurt anything, as 60 is what most apps recommend, though to me that always seemed too high. I have mine at 30. I doubt it helps much in MSFS once you get over 5-10 or so, from what I have read anyhow. It will reduce the chance of a BSOD or just a general OS lockup if you keep going beyond 10, but not so much a CTD in a game like MSFS (maybe for some games).

If you've ever had your Start Menu disappear or stop functioning and the screen freezes too, and then Windows recovers that is sometimes what some TDR recoveries look like by the OS, if the screen doesn't freeze but the start menu was acting funny, it was probably just a process recovery (Windows auto-killed some stuck process, but it will usually only monitor its own MS related processes, not kill others).

I don't think I've ever seen MSFS recover from a potential GPU lockup, it always just CTD's or whatever. If you see a game recover in DirectX by using the TDR, then the screen will flash a few times or do something funny looking and then the game will resume or just maybe give you a pop-up error. Though technically, games can recover with not even a single frame loss with TDR, but that is in theory and rarely realized in code from my understanding.
 

Edited September 1, 20223 yr by Alpine Scenery

Thanks for the explanation

And I saw that some people put in QWORD 64 bits do we have to stay in DWORD 32 bits ?

I'm a bit wary of this, as I don't want my stability issues to get worse. And I don't see how this would affect the "memory could not be read" CTDs. It might however affect the freezes and lockups though? But like @Alpine Scenery says, "it's not going to hurt anything". If I were to try it, would this be okay? 

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers]
"TdrDelay"=dword:0000000a
"TdrDdiDelay"=dword:00000030

Even major apps like Substance Painter and Quixel tell you to add those in there, especially for an AMD. That is the only reason I even knew much about it. I don't think it is going to help this issue though to be honest. Anyone having severe CTD should also check memory timing and voltage in BIOS just in case, try clocking down at least 200, it may help, who knows.

Edited September 2, 20223 yr by Alpine Scenery

22 hours ago, Bob Scott said:

 

Increasing the DdiDelay values gives the system some extra time to recover from a graphics backlog before it calls it quits, resets the driver and crashes the sim.

I recently made a post stating that I felt like when there was a lapse in the data stream, the system crashed.  I suggested that when I get a pause, (lack of data), I immediately hit the ESC button and the sim goes to the Menu.  Then after a short period I hit Resume and everything is okay. (The data has had time to catch up)

It appears to me that this is what this registry fix is doing.  It's allowing more time for the data to catch up, so no crash.

To me, this would indicate that it is a glitch in the streaming, and the sims inability to handle it, not any third party addons or faults in your computer.

Comments please.

Roy

I applied this about a year ago.  Checked my Registry today and it was no longer there.  In the interim I upgraded my GPU and also updated drivers a couple or three times. So appropriate to check that you still have it in place.  I just put it back in.

But we agree friends, is it good in 32-bit DWORD and not 64-bit QWORD ?
So I just put back the TdrDelay and TdrDdiDelay.