10 minutes, so far so good...
Anyone else testing?
Please, AMD, dont mess it up...
nvm... it's still crashing... I give up...
The feels, bruh.
Still display driver crashes with latest "Non-WHQL-Win10-64Bit-Radeon-Software-Crimson-ReLive-17.4.2-Apr11" radeon driver. Tried to install it disabling driver signature enforcement but no luck. Hope you devs release a hotfix ASAP.
The be honest that GPU is old. I'm surprised AMD are still releasing updates for this GPU.
I wouldn't expect miracles with a 2013 GPU.
What crashes are you seeing? Can you check windows event viewer, system events, and see what is the specific error?
Report it here please: http://www.amdsurveys.com/se.ashx?s=5A1E27D23A3DE979
Are you kidding? Haven't you readed this forums lately?
Everyone reported; everyone complains here; nobody simply cares.
And you haven't supplied any information at all. Don't even know what graphics card you have.
INFORMATION REQUIRED WHEN POSTING A QUESTION
One of the 10 posts I've made about it:
"Default Radeon WattMan settings have been restored due to unexpected system failure" and "Radeon Settings: Host Application stopped working"
One of the million threads about it:
I receive the following message since the new OS update was installed
I know you just asked my system specs, but you're not answering anymore. I'll just leave my specs here as well anyways...
AMD Graphics Card
So with all the posts you made....you still have to post more? Are the readers supposed to know about all your other posts? If you don't get a answer on a user-to-user forum it means nobody has a answer for you. Take your computer to a professional or contact AMD or Microsoft support.
Microsoft and computer professional says it's a driver issue.
AMD ignores it. It's not even in the Known bugs list, even tho many people are reporting it.
I'm a consumer and I have the right to be answered and the right to let other people know AMD products are NOT WORKING PROPERLY.
Based on your more recent post, it appears you have identified the cause of this crash as overclocking of our Intel CPU.
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.
Retrieving data ...