Quote Originally Posted by Redolentchewtoy View Post
If I might put my 2 cents in on this, it's SE's issue, I have an I7 3770k with a MSI GTX670 and get the crashes as well, but when i get it, it also locks up my intel chip monitoring system, I have noticed that both my gpu and cpu ramp up overload then no dx detected only in the bazaar areas, Both intercooled as well, niether ever above 35 C. Both also have self overclocking, which they both go to far at certain points, so it's not a gpu or driver issue, cause my CPU wouldn't be getting nuts, no biggy I just have to restart my monitoring back up. It's something with this engine and self clocking technology that's not meshing right. That's just my opinion I'm no tech.
Read here. You see the "No DX Detected" message because your display driver has encountered a fault and thus locks up forcing WDDM to perform a reset of the driver by forcing a restart of the driver.

If you are using software that constantly increases the clock speed of the GPU or your VRAM past the officially posted clock speed, it will continue to increase the clock speed until it forces the driver to hang. You then experience a display driver reset and the loss of DirectX. If what ever you are using only "increases the clock when under heavy load" you need to make sure to remove or disable it. When it's under heavy load that is the time it's most likely to be negatively effected by overclocking.

And everyone, please stop saying that because your GPU runs at a few centigrade above room temperature that it's not the problem. Your GPU runs exactly the same at 35C as it does at 95C.