Recent content by Circinae

Spacekitkat is correct, the option isn't there and we knew about this. Sven highlighted that this option wasn't available for older cards when he told us about the registry work around, which was one of the main problems. Of course AMD's own representatives would be less informed than a bunch of...

It is absolutely the drivers and the clock speed control. Older drivers stop the problem. Clock blocker stops the problem. It is consistent, easy to reproduce and occurs across systems for a specific GFX card edition. You can even monitor the clock speeds to watch when it triggers. I very much...

I can say with confidence that using Clock Blocker and changing the "Default" setting to "Block", then having it enabled stops the crashes, regardless of the driver version (I'm running the latest). Make sure the program is set to start when Windows starts and as I mentioned before, it will...

Hey folks, So, I've been running Clock Blocker (name still makes me giggle) with the setting to stop downclocking by default and to auto-start on windows launch. It has eradicated the crash in question, but of course, keeps the card clocks running at their maximum, meaning more heat and energy...

Hey Sven, I hadn't updated my drivers in a long time and when I did, the crashes began to happen. I went back a few driver versions and they kept happening and as I'd forgotten the number of my previous ones, so I thought back to the first Crimson drivers that I'd remembered working fine (15.12)...

Well, as expected, crashed immediately this morning, so yeah 15.12 is still the only solution I know of. The latest drivers are still busted. Shame.

Quick update to my earlier message and this is still speculative, but I've actually updated to the latest AMD drivers as I noticed they had 16.40 rather than .30 for the first time in a long time. I've been watching streams, playing Battlefield 1 and both at the same time, alt tab etc. So far...

I had a look through your thread and signed up to chime in. I have an R9 290 and the exact same problem, it has plagued me for the majority of the year. You may stop butchering your PC now. It is categorically a result of AMD's drivers. I am not exactly sure at what point the issue arose, but...