I asked him here: http://www.anandtech.com/comments/10540/the-geforc... and he said it'd come after the 470 and 460. Not sure if he meant release or review; I think he meant release, and it's possible he'll do a 480+470+460+Polaris deep dive in one article.
That Firefox issue... Very strange, but, I never had an application crash--it was the driver that crashed (but with no message about it; it just kept resetting) and it would happen with or without hardware acceleration enabled. It also wasn't exclusive to Firefox, the crash happened with IE and Edge as well.
I had this problem with every driver released after v15.12. It is now fixed.
This is an issue with certain rendering paths on WDDM driver stacks. Modern GPU's will often not need to directly update Windows on the status of a rendering task, but unfortunately Windows has a default timeout of only 2 seconds before it assumes the gpu has hung and resets the display driver - you'll see lots of scary "Windows - Hardware error" messages in Reliability Monitor when this happens.
The fix is to change the default timeout to something more reasonable - nVidia recommends 10 seconds, I'm not sure what AMD recommends but 10 seconds seems to be a good ballpark for it.
Yes, the default is 2 seconds by default or if the key doesn't exist. It's created if you install certain GPGPU debugging utilities. Create the key and set it to the (decimal) value in seconds you wish the timeout to be. I'd recommend not going much past 10 seconds, since if the gpu has actually hung it'll increase the time to recover.
We’ve updated our terms. By continuing to use the site and/or by logging into your account, you agree to the Site’s updated Terms of Use and Privacy Policy.
11 Comments
Back to Article
powerarmour - Tuesday, August 9, 2016 - link
Yes yes, now about that full Polaris review...silverblue - Tuesday, August 9, 2016 - link
Ryan said last Friday that the deep-dive will follow the reviews for the 470 and 460.Dr. Swag - Tuesday, August 9, 2016 - link
I asked him here: http://www.anandtech.com/comments/10540/the-geforc... and he said it'd come after the 470 and 460. Not sure if he meant release or review; I think he meant release, and it's possible he'll do a 480+470+460+Polaris deep dive in one article.Dr. Swag - Tuesday, August 9, 2016 - link
P.S. If you want a direct answer from him ask him on Twitter. He should respond if you ask him there.prime2515103 - Tuesday, August 9, 2016 - link
That Firefox issue... Very strange, but, I never had an application crash--it was the driver that crashed (but with no message about it; it just kept resetting) and it would happen with or without hardware acceleration enabled. It also wasn't exclusive to Firefox, the crash happened with IE and Edge as well.I had this problem with every driver released after v15.12. It is now fixed.
This is on a 7970 3GB card.
prime2515103 - Tuesday, August 9, 2016 - link
P.S. That problem applied to both Win7 and Win10 (both 64-bit).Omoronovo - Tuesday, August 9, 2016 - link
This is an issue with certain rendering paths on WDDM driver stacks. Modern GPU's will often not need to directly update Windows on the status of a rendering task, but unfortunately Windows has a default timeout of only 2 seconds before it assumes the gpu has hung and resets the display driver - you'll see lots of scary "Windows - Hardware error" messages in Reliability Monitor when this happens.The fix is to change the default timeout to something more reasonable - nVidia recommends 10 seconds, I'm not sure what AMD recommends but 10 seconds seems to be a good ballpark for it.
nVidia: http://http.developer.nvidia.com/NsightVisualStudi... (nVidia debugging guide)
Microsoft: https://msdn.microsoft.com/en-us/library/windows/h... (discussion of tdr and the registry entries that need modified to alleviate this).
prime2515103 - Tuesday, August 9, 2016 - link
Good info there! I'll keep this in mind if the problem returns with future drivers.iamkyle - Wednesday, August 10, 2016 - link
Nothing in this article regarding Windows 10. Those reg keys don't exist...unless I'm supposed to create them?Omoronovo - Friday, August 12, 2016 - link
Yes, the default is 2 seconds by default or if the key doesn't exist. It's created if you install certain GPGPU debugging utilities. Create the key and set it to the (decimal) value in seconds you wish the timeout to be. I'd recommend not going much past 10 seconds, since if the gpu has actually hung it'll increase the time to recover.Shadowmaster625 - Wednesday, August 10, 2016 - link
Why would you play Overwatch and DOTA2 in crossfire?