2 minutes ago, Bobsk8 said:

I found the same thing. So to reverse it, I guess you would just have to remove the entry in the registry. ( Just a guess not sure) 

Exactly. Then restart the computer.

Is there some sort of problem with writing a script to remove them?

3 minutes ago, fppilot said:

Is there some sort of problem with writing a script to remove them?

No, Scroll back a bit, and Matchstick has already done it.

1 hour ago, fppilot said:

Thanks.  Will apply this.  However. With each registry patch like this should there also be an "antidote.reg" file to put Windows back to the previous state?

 

35 minutes ago, Bobsk8 said:

I found the same thing. So to reverse it, I guess you would just have to remove the entry in the registry. ( Just a guess not sure) Or would that cause a problem if you just deleted the entry?

I saw it.  Just surprised at some of the discussion that followed my post, so I have quoted it above.  I was not singling out Emerson67, or this particular registry mod/script.  My comment was general or global.  "with each registry patch like this..."   Too often it is not done.  And though I myself am quite comfortable with using regedit and drilling down to sometimes deep locations in the Windows Registry, not all members here are comfortable with that, or have the skills.

I have not used this yet, as i don't feel confident carrying it out, and not wrecking something else. On to the 3rd day now without a ctd, so hopefully i wont need to use it,

Edited March 7, 20215 yr by Car147

14 hours ago, Emerson67 said:

This post is for all desesperados,

This is a nice tweak (actually not new) that should prevent a pretty common MSFS crash to desktop cause, by adjusting some Windows 10 GPU scheduler timeouts.

It does not prevent some CTDs caused by MSFS internal bugs, because this tweak acts on Windows 10 itself.

Procedure:

1. Open a plain text editor, like Microsoft Notepad (Windows accessories->Notepad) or Notepad++.

2. Copy and paste the following text into the editor:

Windows Registry Editor Version 5.00

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

3. Save as "vaccine.reg" file, and close the editor.

4. Double click on "vaccine.reg" file, and then choose "Yes".

5. Restart the computer.

6. Run MSFS.

7. Give feedback.

 

What this tweak does? It increases (5 times) the values of two Windows 10 GPU scheduler timeout parameters.

You may tweak yourself those values as you wish. Here is the technical info.

 

I followed you instructions, restarted PC and do not see any entry added in the registry.  Where is that supposed to appear? 

3 hours ago, Bobsk8 said:

I found the same thing. So to reverse it, I guess you would just have to remove the entry in the registry. ( Just a guess not sure) Or would that cause a problem if you just deleted the entry?

These are Windows debug tools. Removing them will simple set default values for these. Check out Microsoft documentations at https://docs.microsoft.com/en-us/windows-hardware/drivers/display/tdr-registry-keys

KeyPath   : HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\GraphicsDrivers
KeyValue  : TdrDelay
ValueType : REG_DWORD
ValueData : Number of seconds to delay. The default value is 2 seconds.

3 minutes ago, Cai Zicheng said:

These are Windows debug tools. Removing them will simple set default values for these. Check out Microsoft documentations at https://docs.microsoft.com/en-us/windows-hardware/drivers/display/tdr-registry-keys

KeyPath   : HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\GraphicsDrivers
KeyValue  : TdrDelay
ValueType : REG_DWORD
ValueData : Number of seconds to delay. The default value is 2 seconds.

Well I installed the vaccine per instructions and i don't see any entry in the Registry for it. . I hope I didn't screw up my system..

2 minutes ago, Bobsk8 said:

Well I installed the vaccine per instructions and i don't see any entry in the Registry for it. . I hope I didn't screw up my system..

Can you try right click and run as administrator?

OK I see where they are now, The folder Graphics drivers/   I was   looking for it in  the sub folders. Now we will see if it works. To reverse this, I guess I could just delete the two entries.

 

Now I am going to try the same flight that just CTD on approach and see if this works. 

 

"TdrDelay"=dword:0000000a
"TdrDdiDelay"=dword:00000019

Edited March 7, 20215 yr by Bobsk8

Note that the tweak only prevents CTDs caused by Windows 10 GPU scheduler, which is a common source of CTDs on MSFS. It does not prevent crashes caused by other sources, like add-ons that have buggy program code (e.g. avionics).

So far this has worked. Five flights with zero problems. 😃

I had very rarely CTDs (aside one version which was admittedly broken) but I saved this for the future. You never know...

Thanks to @Emerson67 for posting this.

Kind regards, Michael

I have plenty of CTD's, nearly every long flight. This 'vaccine' did not help in my case, but I suspect my CTD's are USB related.
It is a shame though that a system can be rock stable for all kinds of heavy duty work and games, and become unstable when it comes to flightsims.

Strangely enough, I never had a CTD with MSFS. I run MSFS with ZERO tweaks (no ext FPS limiter, no CFG alteration, etc) and also run my rig with no enhancements whatsoever. My Community folder is also quite "empty".

I wonder those having CTDs what changes (if any) they have applied....