I forgot to mention. The way it crashes is when I put on my CV1 I can see and hear around 1 second then the both oculus and my screen freezes and turns all black and stays like that. Next thing I have to reset my computer.
2 of 2 people found this helpful
Your problem is Asus tweak. Delete it or disable it through 'Services'. This program conflicts with Wattman/AMD controls.
by trilliante on May 18, 2017 9:00 PM
I have an Asus GPU, so I had the Asus GPU Tweak software installed. After installing the update and watching what happens on reboot, I discovered that the crash happened as soon as GPU tweak started, and that it was accompanied by a message about wattman being reset. I knew I had a slight "over"clock on my GPU, but I didn't even think about that being the cause of it. I booted into safe mode, opened up services and disabled the ASGT service (Asus GPU Tweak). When I restarted.... everything worked properly! I then uninstalled the software. Looks like I'll be doing all my adjustments through the built in AMD software from now on.......
See the answer in context
This did the trick! Man, I've been looking for a real solution for ages, thank you very much!
This is what happened:
I uninstalled GPU Tweak II and the old driver with DDU. Then I installed the latest Crimson drivers along with AMD Settings and gave it a try.
Same thing as always, but watching other post you made gave me the idea. Using Wattman I've risen the voltage for the first two stages to 1000, that way when the Oculus Rift suddenly demands power the video card would respond in time. I gave it a try and it's running great, I think even better than before!
These are the only changes I had to make:
Oh I think my faith in AMD is restored, I'll still try it for a few days to be sure, but this seems to work.
Thanks again kingfish!
glad to see that you have found the correct answer to your question. In order to help others with a similar problem to find this answer quickly, we have locked the discussion to keep it focused on the issue you reported.
Thanks for the quick response!
Well that may have been the one and only thing I didn't try. I'll give it a go, disable Tweak and update the drivers and software and see what happens once I get back from work in a few hours and post the results.