T
ThomasSharpless
In many cases the blue screen "VIDEO_TDR_FAILURE" does not indicate a system configuration problem, but is just Windows shooting itself in the foot. The TDR monitor was intended to detect GPU hangs that would disable the UI, and automatically reboot the system so that the user would not have to know how to clear a hang (hold down the power button). TDR was never an essential function, but now that more apps use GPUs in compute mode, has become positively dangerous.
Reports of this failure are now rife on the web, and in most cases they are related to legitimate GPU compute processes, not bad game code. For example many users of Adobe Premier Pro and Lightroom now experience this crash regularly. It seems to be more prevalent on laptops with dual GPUs, which are also becoming more common.
This is a real defect in Windows, as it causes needless loss of time and loss of work for people who don't deserve it.
Sophisticated developers should be able to able to structure their GPU processes to avoid this crash. But this would just be another Windows-specific restriction, and we don't really need it. Better to disable TDR, or extend its timeout, by editing the Windows Registry. Here is the official info from Microsoft Timeout Detection and Recovery (TDR) Registry Keys - Windows drivers | Microsoft Docs Windows does not put these values in the registry, you have to create them by hand (note they are not new keys, just additional values of the key HKEY_LOCAL_MACHINE\System\
I suggest that Microsoft consider disabling TDR by default, and allowing those who want it to opt in via a system setting. Assuming that there are scenarios where it delivers some actual value. Otherwise how about just scrapping it?
Continue reading...
Reports of this failure are now rife on the web, and in most cases they are related to legitimate GPU compute processes, not bad game code. For example many users of Adobe Premier Pro and Lightroom now experience this crash regularly. It seems to be more prevalent on laptops with dual GPUs, which are also becoming more common.
This is a real defect in Windows, as it causes needless loss of time and loss of work for people who don't deserve it.
Sophisticated developers should be able to able to structure their GPU processes to avoid this crash. But this would just be another Windows-specific restriction, and we don't really need it. Better to disable TDR, or extend its timeout, by editing the Windows Registry. Here is the official info from Microsoft Timeout Detection and Recovery (TDR) Registry Keys - Windows drivers | Microsoft Docs Windows does not put these values in the registry, you have to create them by hand (note they are not new keys, just additional values of the key HKEY_LOCAL_MACHINE\System\
I suggest that Microsoft consider disabling TDR by default, and allowing those who want it to opt in via a system setting. Assuming that there are scenarios where it delivers some actual value. Otherwise how about just scrapping it?
Continue reading...