• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

The AMD Driver Thread

Crimson 16.1 downloaded, installed and running okay so far. No problems in BF4 anyway. I will report anything unusual if it happens.

I have never had an issue with the Crimson drivers so fingers crossed eh! :)
 
Maybe mate, but that's just as bad...aren't Dice and Ea partnered for bf games still lol

Crossfire and SLI always comes down to if the engine supports it; if it doesn't or is broken; there's nothing AMD or Nvidia can do until devs fix it......I'd put my money on Dice over AMD on this one ;)
 
Is there still no fix for Dying Light and Just cause 3 regarding crossfire?

Just Cause 3 is still a no for multi-GPU. Someone from Nvidia was quoted shortly after launch as saying the engine is compatible with multi-GPU and support will need to be patched in by Avalanche before AMD/Nvidia can add support. Sucks as this is the only game I'm playing and it would be nice to get double the horsepower to run 3 screens at a higher rate.

No idea on Dying Light, I'm afraid, don't have that game.
 
Have you guys tested to see though? A bug I reported that was fixed but not listed. CSGO if you tabbed out on 15.12 with Freesync enabled the screen would flicker. This is now fixed.
 
Since moving to the Crimson drivers I seem to have some kind of mouse pointer bug where my pointer turns into a square patch of multi coloured pixels.

I think it occurs when I cold boot my PC, but don't touch anything letting the screen suspend after 10 minutes, when I come back I'll hit a key on my keyboard to wake my screen and after moving the mouse it turns back to the normal pointer.

After installing the hotfix this bug happened again but moving the mouse didn't sort it, I had to reboot.

Running Windows 10, anyone else getting this?
 
Have you guys tested to see though? A bug I reported that was fixed but not listed. CSGO if you tabbed out on 15.12 with Freesync enabled the screen would flicker. This is now fixed.

No i havn't, as theres no point, its not in the release notes, so i know it hasn't been fixed yet, as with the amount of people suffering from it, if it had been fixed, then it would have been in them.
 
Last edited:
No i havn't, as theres no point, its not in the release notes, so i know it hasn't been fixed yet, as with the amount of people suffering from it, if it had been fixed, then it would have been in them.

Not all fixes get put into the release notes though mate like I just pointed out with csgo bug.

I would test and report back to amd.
 
I just noticed under the crossfire section, there is now no option to "Enable CrossfireX for applications that have no associated application profile"? Theres just on or off now, everyone else the same?

24225452946_1735b47d5f_b.jpg
 
Last edited:
Have you guys tested to see though? A bug I reported that was fixed but not listed. CSGO if you tabbed out on 15.12 with Freesync enabled the screen would flicker. This is now fixed.

I have tested, csgo shows a core clock of 300mhz on main menu and ranges from 500 to 800mhz in game so back to using AB till its fixed
 
I have tested, csgo shows a core clock of 300mhz on main menu and ranges from 500 to 800mhz in game so back to using AB till its fixed

Csgo isn't a good game to showcase mate.
You do understand that your core will change up and down based on how demanding the game is pushing the GPU.

For example, 100fps your GPU might only need 500mhz to achieve this frame rate..

Has a test put csgo with unlimited fps_max 999 and see what your core clock is now.
 
All my games now hang after 40 minutes instead of the other issue

Crimson 16.1

Catalyst 15.7 to Crimson 15.12


Since June, AMD has been breaking all sort of stuff for my setup... as long as the mass is happy it's fine I guess, but I'm not happy anymore, thanks to you AMD.


Lets not forget about the 2d idle bug that is FINALLY on the known issue list after 6 freaking months.

[82892] Display corruption may occur on multiple display systems when it has been running idle for some time
 
Really nice to see another WHQL driver so soon after the last one, great job with the release schedule, AMD!

Installing these on my system now, hopefully they'll run as well as the last ones did :)
 
Back
Top Bottom