March 7, 20215 yr 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. Â
March 7, 20215 yr Interesting - thanks! I am investigating this. I am hoping it might help the 0x05 error, which is difficult to trace. It might also explain why people with very powerful GPU's (3080 / 3090 etc.) don't get the error as much. I just need to look up the default values in case I want to put it back. Rob (but call me Bob or Rob, I don't mind). I like to trick airline passengers into thinking I have my own swimming pool in my back yard by painting a large blue rectangle on my patio. Intel 14900K in a Z790 motherboard with water cooling, RTX 4080, 32 GB 6000 CL30 DDR5 RAM, W11 and MSFS on Samsung 980 Pro NVME SSD's. Core Isolation Off, Game Mode Off.
March 7, 20215 yr 9 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've had this mod running since last Thursday and have now completed four, two hour+ flights in the A320Neo with the FBW mod without a CTD. I can't say 100% that this has fixed the CTDs as I also reduced the AI% down to 40% and deleted the rolling cache at the same time. And four flights is not conclusive evidence. I could of course, reverse the above and restest and see if the CTDs return, but that's not going to happen ! However, so far, so good...
March 7, 20215 yr Before I had plenty of CDT on almost every flight and this tdrDelay and TdrDdidelay tweak solved everything! I put the 2 to 60 ...
March 7, 20215 yr 8 minutes ago, Axis3600 said: Before I had plenty of CDT on almost every flight and this tdrDelay and TdrDdidelay tweak solved everything! I put the 2 to 60 ... It was your posting in another thread I that put me onto it - many thanks!Â
March 7, 20215 yr Using this fix since months - initially to avoid crashes in P3DV5.1 (Nvidia RTX 2080). And I never had a CTD in MSFS either. Highly recommend! Edited March 7, 20215 yr by LarsA
March 7, 20215 yr 10 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.  So by just clicking on this file after you create it, this entry is then added to the registry in the proper place, without having to edit the registry?   Â
March 7, 20215 yr Thanks for this - I'm hoping this will mean I can start using a AMD driver newer than last Octobers.
March 7, 20215 yr 33 minutes ago, Bobsk8 said: So by just clicking on this file after you create it, this entry is then added to the registry in the proper place, without having to edit the registry? yes, as long as you name the file with .reg on the end, it will automatically enter it into the Windows Registry when you double click on it - there will be a confirmation warning of what it is about to do. Then, for it to take effect, restart the computer (not shut down and start up - as on some PC's it will fast load a previous state and not change anything). I have now done this and I look forward to testing it. I have a few hours planned in MSFS this evening. Edited March 7, 20215 yr by bobcat999 Rob (but call me Bob or Rob, I don't mind). I like to trick airline passengers into thinking I have my own swimming pool in my back yard by painting a large blue rectangle on my patio. Intel 14900K in a Z790 motherboard with water cooling, RTX 4080, 32 GB 6000 CL30 DDR5 RAM, W11 and MSFS on Samsung 980 Pro NVME SSD's. Core Isolation Off, Game Mode Off.
March 7, 20215 yr 11 hours ago, Emerson67 said: 7. Give feedback. 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? Frank Patton Corsair 5000D Airflow Case; MSI B650 Tomahawk MOB; Ryzen 7 7800 X3D CPU; ASUS RTX 4080 Super; NZXT 360mm liquid cooler; Corsair Vengeance 64GB DDR5 4800 MHz RAM; RMX850X Gold PSU;; ASUS VG289 4K 27" Display; Honeycomb Alpha & Bravo, Crosswind 3's w/dampener.  Former USAF meteorologist & ground weather school instructor. AOPA Member #07379126             "I will never put my name on a product that does not have in it the best that is in me." - John Deere
March 7, 20215 yr 4 minutes 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? Just checking my registry the entries don't already exists so if I remember my registry hacking correctly in that case you'd want a file like  Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers] "TdrDelay"=- TdrDdiDelay"=- Â
March 7, 20215 yr @fppilot Would like to know how to reverse it? Martin Parr Retired professional yacht skipper for vessels up to 46m  System: Omen 40L GT13-0054na Gaming PC; Windows 11 Home 64-bit OS; Intel Core i9-10900K CPU @ 3.7GHz; RAM 32GB; Samsung S34J55x Monitor 3440x1440 @75 Hz Resolution; NVIDIA GeForce RTX 4080 Ti. MSFS P/D; TM Pendular Rudder Pedals, TM Warthog Hortas Throttle/Joystick Combo.
March 7, 20215 yr 15 minutes ago, Matchstick said: Just checking my registry the entries don't already exists so if I remember my registry hacking correctly in that case you'd want a file like  Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers] "TdrDelay"=- TdrDdiDelay"=-  Doing a search of the Win10 registry tells me neither of these keys exist at this location (nor anywhere else.) In other words you're ADDING these keys, not changing them. YMMV -J 13700KF | RTX 4090 @ 1440 | 64GB DDR5 | 2 x 1TB SSDs | 1TB M.2 NVMe
March 7, 20215 yr Just now, Twenty6 said: Doing a search of the Win10 registry tells me neither of these keys exist at this location (nor anywhere else.) In other words you're ADDING these keys, not changing them. YMMV That's my script for deleting them if you've added them with the original script.
March 7, 20215 yr 5 minutes ago, Twenty6 said: Doing a search of the Win10 registry tells me neither of these keys exist at this location (nor anywhere else.) In other words you're ADDING these keys, not changing them. YMMV 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? Edited March 7, 20215 yr by Bobsk8 Â Â Â
Archived
This topic is now archived and is closed to further replies.