Not all bugs are fixed no, as above.

Same happens with Nvidias, some people are still saying, this is broken, been broken for months now, ive reported it, but they havn't fixed it, and some people who also had the same broken thing, have it fixed for them now, its like Espionage says, some things are hard to reproduce, as there is that many different combinations of setups, we are all not running the exact same things, so some people will have bugs that other people don't get, and some bugs will get fixed for some people, but still appear for others. When you report a bug, you have to remember, AMD and Nvidia do not have your rig, so if they reproduce and fix said bug, but its not fixed for you still, i guess thats because you are not using AMD or Nvidias rig that the bug was fixed on, something else will be causing said bug on your rig, getting them fixed for all combinations will take time, for both, be that many combinations, i wouldn't be surprised if some bugs just can't be fixed for everyone, only way they'll 100% fix bugs is, if when you send them a report, you also send them yer rig as well, or they have a repair service, like for Tvs, where someone can come to yer home and fix it 😀 Its not like the consoles, we are not all on the same ones, our CPUs are different, motherboards, Ram, GPUs, soundcards, even our clocks are also different, different BIOS, peripherals, drivers, software......................

I cleaned 14.4 whql with ddu than installed 14.8 but i can not acces ccc panel. Right click than amd catalyst control center, The mouse flickers like it is loading it and then nothing occurs. Any idea ?

What OS are you running? all of my encounters with CCC not opening have been .Net framework issues assuming that the drivers have installed correctly try repairing .Net you can download a useful tool for that here, http://www.wincert.net/forum/topic/10715-rebuilt-net-framework-452-full-x86x64-5-26-2014/

Same here! Running Windows 8.1 64-bit Also got the red screen(for the first time).

I got these also with the 14.7 RC3 after a game of BF3. Just red screened, but I have no OC. Just installed these and will see if it happens again. It only happened once so I'm really not sure what would have caused it.

The heat probleme is still here but my cf scaling is better on bf4 watchdogs metro crysis3 , so i can accept a bump in temps ( nothing to worry about 5-6c rise ) for a good bump in performance :P and no red screen so far 🙂

I downclocked to 4.5ghz and no more red screens after 2h of gameplay. I never though it was a unstable CPU, lol.

Funny drivers. Seems to work, the only issue I found with these, compared to 14.7RC3 was that EU4 loads with black screen and "not responding", so no welcome screens or what it is doing, just black screen with music, but once it loads stuff is there 🙂

Do any of you do fresh installs of Windows when moving to a new driver? I just did this and have received no problems so far.. I've only spent a few hours playing Space Engineers though : T

-Installing drivers is easy like usual except for my first rig. I always get a warning that there were some errors(?) during installation. I started receiving those messages since I used DDU for the "clean" installation during the mantle driver revolution :wanker:. CCC works fine on all systems.

Anyone else seeing this ?

Yea I get errors during install warning at the end of the install too, but never associated it with DDU until now The install has no errors though, you can check the log after the install and everything says SUCCESS

The warnings is not a problem in itself, from what I know, the Cat installer wrote a value that was already there, that's all. If someone who have the issue could send me an export HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer Before and After using DDU.

Hi there, just reporting my experience with this new driver, ive had no issues so far, alltho reading the comments here, ive found a common denominator for the people that have had bsod on windows, most of these users have previously used DDU. I had a new installation using windows server 2012 r2, and have changed to various versions of amd drivers, and ive had no issues with new batch. Now before some DDU fan comes at me on rampage, i just think maybe it has some bug, that may be conflicting on different system configurations. Diablo 3 performance has improved, alltho im not using high shadows (smooth) but the normal high shadows. MWO dx9 client has some improvements too. (crysis 3 engine, poor dev coding btw) cheers.

I`ll leave this one for someone else to test this time if you don't mind, Ive had enough of AMDs drivers this week to last me a life time

I can take your export with the driver installed only too no problem. having both is just easier but I can find the problem too even if you dont uninstall it. Your choice 🙂

Hi there, just reporting my experience with this new driver, ive had no issues so far, alltho reading the comments here, ive found a common denominator for the people that have had bsod on windows, most of these users have previously used DDU. I had a new installation using windows server 2012 r2, and have changed to various versions of amd drivers, and ive had no issues with new batch. Now before some DDU fan comes at me on rampage, i just think maybe it has some bug, that may be conflicting on different system configurations. Diablo 3 performance has improved, alltho im not using high shadows (smooth) but the normal high shadows. MWO dx9 client has some improvements too. (crysis 3 engine, poor dev coding btw) cheers.

I dont think so, but nothing is impossible with computers. Many user use DDU some have the bsod problem some dont. Honestly I think its a driver bug. Myself doesnt have the BSOD (I use DDU a lot :P )

I dont think so, but nothing is impossible with computers. Many user use DDU some have the bsod problem some dont. Honestly I think its a driver bug. Myself doesnt have the BSOD (I use DDU a lot :P )

i think it has to do with different setups(mobos more likely), but since i stopped using regcleaners, uninstallers, etc ive hand non issues so far with drivers and with windows overall. is just my 2 cents, not meant to upset anyone or make statements =)

It’s anti DDU day it seems. :whip:

It’s anti DDU day it seems. :whip:

i dont think it is, but you cant deny the posts with most issues are like: ´´this driver is crap it bsod!!! , ima ddu and back to xx.xx driver it was fine´´ i suggest to take a look at the systems these users have to see if there is any bug that can be replicated, in the drivers or DDU. (for the sake of misleading of a good driver release)

i dont think it is, but you cant deny the posts with most issues are like: ´´this driver is crap it bsod!!! , ima ddu and back to xx.xx driver it was fine´´ i suggest to take a look at the systems these users have to see if there is any bug that can be replicated, in the drivers or DDU. (for the sake of misleading of a good driver release)

No worries I don't deny anything. If thing those who know me around know that I always been quite open to hear and fix stuff. (at least I hope )

Wagnard, if you include me into this "anti-ddu day" i have to tell you that you are wrong 🙂 DDU is a very nice tool, i like it. It is simple, complex and does its job, but as with any clean up software in distanced future using it may cause problems and obviously it is not perfect. For example, 14.7 driver in ccc or msi afterburner or any other software was always recognized as 14.6 even after using ddu. By my awesome superpowers i was forced to reinstall os, freshly installed windows 8.1 x64 enterprise, installed 14.7 right after updating freshly installed os and guess what? CCC, afterburner.... etc were recognizing driver as 14.7, not 14.6. Concluding this story: even ddu was unable to clean all things to make software recognize proper driver version. I understand, reason of this specific problem lies somewhere between amd and windows. My point is... ddu shouldn't be used in routine as replacement for amd's regular driver uninstaller but should be used only if some regular things fail.

The anti DDU was more a joke than anything else 🙂 I wasn't pointing to anyone to be honest. And totally agree with what you said. While I consider DDU safe, you guys should always think of this simple rule (if it's not broke, don't fix it). Interesting stuff about MSI afterburner I may look at this. I havent really had this problem myself. CCC always shown correct version except for some RCx but it was clearly the driver team that forgot to add driver version to the CCC. Gonna play a bit around with 14.6 and 14.7 Edit: done, I played with 14.6 up to .8 and I havent saw the issue you mentioned on MSI AB. I even cleaned each time in normal mode. Could be a possible issue on some earlier DDU version before I launched it as a system process. Thanks for reporting anyway 🙂

I ll export mine as soon as I can. Just to point out that I get that warning message and most of the time I have to install the driver again. I haven't used DDU in a while but I am still in the same windows installation.

Thanks. Only when you have time and feel for it. Also, can someone share their .DMP of their bsods? I want to give a look at them just in case I find something interesting.

Funny thing these are not on the AMD's website yet. I'll give them a try and post my impressions!

just tested this driver BF4 + mantle still have huge fps drops.

the 2gb vram of your 7870 are to less for mantle, and no driver will ever change that.