TDR代表超時檢測和恢復。
這是Windows操作系統的一項功能，可以檢測顯卡的響應問題，並通過重置卡恢復到功能桌面。
如果操作系統在一定時間內（默認爲2秒）未收到圖形卡的響應，操作系統將重置顯卡。
在TDR存在之前，這種性質的問題會導致系統凍結並需要重新啓動操作系統。
如果啓用了TDR並且您看到TDR錯誤消息“顯示驅動程序停止響應並已恢復”，則表示Windows操作系統重置顯示驅動程序。
更詳細的資料==>
https://blog.csdn.net/MaxKwanVFX/article/details/79623257
在windows環境下，打開新版SP可能會彈出以下窗口，提示你的TDR(Timeout Detection
Recovery)過低，點擊Continue
anyway可進入軟件但是可能會帶來例如軟件崩潰和延遲過高的問題，本文針對該問題結合官方Documentation給出瞭解決辦法。
修改註冊表太麻煩了吧 打開 NVIDIA的自帶配置軟件==>
“C:\Program Files (x86)\NVIDIA Corporation\Nsight Visual Studio Edition XXX\Monitor\Common\Nsight.Monitor.exe”
修改下,改完後 需要重啓電腦生效的
SP 建議的是60秒
TDR stands for Timeout Detection and Recovery. This is a feature of the Windows operating system which detects response problems from a graphics card, and recovers to a functional desktop by resetting the card. If the operating system does not receive a response from a graphics card within a certain amount of time (default is 2 seconds), the operating system resets the graphics card.
Before TDR existed, problems of this nature would have resulted in a system freeze and required a reboot of the operating system. If TDR is enabled and you see the TDR error message, “Display driver stopped responding and has recovered,” this means that the Windows operating system reset the display driver.
There are three different possible debugging configurations:
Local debugging with a single GPU,
Local debugging with multiple GPUs, or
Remote debugging.
Choose the one that most closely reflects your NVIDIA Nsight setup:
Local Debugging with a Single GPU
Disabling TDR removes a valuable layer of protection, so it is generally recommended that you keep it enabled.
However, setting the TDR delay too low can cause the debugger to fail for one of two reasons:
Debugging on some GPUs will fails with a TDR delay of less than 10 seconds.
Debug builds of CUDA kernels run more slowly and may intrinsically require additional time to complete. With too low of a TDR delay, the kernels may not have enough time to complete.
Therefore, if you are using local debugging with a single GPU, it’s recommended that you leave TDR enabled, and set the delay to 10 seconds.
To enable TDR and change the delay, do the following:
Right-click the Nsight Monitor icon in the system tray.
Select Options.
In the Options window on the General tab, set WDDM TDR enabled to True.
Change the WDDM TDR Delay from the default setting to 10.
Local Debugging with Multiple GPUs or Remote Debugging
When using either a local debugging configuration with multiple GPUs, or a remote debugging configuration, it’s important to disable TDR. This is because with most CUDA applications, a TDR means that any debugging operation after the TDR will fail. You will not be able to step, set breakpoints, view variables, etc. The application will receive a grid launch failure, and the CUcontext will begin to report errors.
Having TDR enabled can interfere with GPU debugging because the graphics card is perceived by the operating system as unresponsive when the execution of a target application is paused or when the debugger is performing certain operations.
To disable TDR, do the following:
Right-click the Nsight Monitor icon in the system tray.
Select Options.
In the Options window on the General tab, set WDDM TDR enabled to False.
For more information about TDR, see: