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: