AMD releases Radeon Software Crimson Edition 16.3 drivers with loads of new features

Typical AMD.. update tells me I'm up to date. I've had it with AMD been running crossfire since 4870. Since 15.11 through 16.2.1 I've had nothing but trouble with my 390X.

Issues I have had or still have.
Just Cause 3 corrupted textures.
Can't control Crossfire in games I want them to run or disable it for games I don't want to run Crossfire.
Rise of Tomb Raider flashes.
Rainbow Six: Siege when in Crossfire corrupted texture
The Division looks like absolute crap and get flashing throughout.

Here's video of the flashing.

Reading the release notes for 16.3 haven't fix Tomb Raider, The Division, or Star Wars. How long has Star Wars been released?
Yes it is quite liberating to be away from AMD - used to be excited to see a driver release as it might fix my problem only to be disappointed and wait for a few more months.

On NV, haven't had an issue yet touch wood...
 
Typical AMD.. update tells me I'm up to date. I've had it with AMD been running crossfire since 4870. Since 15.11 through 16.2.1 I've had nothing but trouble with my 390X.

Issues I have had or still have.
Just Cause 3 corrupted textures.
Can't control Crossfire in games I want them to run or disable it for games I don't want to run Crossfire.
Rise of Tomb Raider flashes.
Rainbow Six: Siege when in Crossfire corrupted texture
The Division looks like absolute crap and get flashing throughout.

Here's video of the flashing.

Reading the release notes for 16.3 haven't fix Tomb Raider, The Division, or Star Wars. How long has Star Wars been released?
just do a clean install like how it's recommended. download the uninstaller from AMD's website.
and also, most of the bugs are not something that are from AMD's side, but from your side.
it's the same with Nvidia drivers too. updates tend to break stuff.
Don't be surprised if the obvious answer is the right answer... way too much goes wrong on AMD based setups for the woe is me defense.
 
Not sure if this will help or not, but there's a tool for AMD cards that allows you to edit the cards core clock settings at the firmware level. I had to do this for my 5870s years ago to get them to maintain a stable clock speed and solve my flickering issue. The tool was called ATI Win Flash and allows you to download the cards firmware then I used ATI RBE to modify the clock settings for the VRAM and the Core clock raising all the minimum clocks to something a little more sensible, saved the ROM and flashed it back to my cards. This prevented the cards from throttling in 2D which was causing tearing on my desktop, and it fixed my 3D stuttering in games. Also this matches the firmware up on your cards, sometimes if you buy them on separate dates they could have different firmware revisions causing issues as well.

If these programs are compatible with the new GPUs from AMD it could be worth trying, just be sure to backup the original firmware from your cards in case you need to flash them back for RMA purposes.


here is the link for a Hawaii Bios editior

http://www.overclock.net/t/1561372/hawaii-bios-editing-290-290x-295x2-390-390x
 
Don't be surprised if the obvious answer is the right answer... way too much goes wrong on AMD based setups for the woe is me defense.

Are you being serious or just trolling. The latest WHQL drivers by nvidia have been an absolute disaster http://wccftech.com/nvidia-users-beware-latest-drivers-damage-pc/ Some people have had systems not starting up and in a constant loop and all kinds of other problems. And this isnt the first time either, especially since Win10 (DX12).

196.75 WHQL http://www.zdnet.com/article/warning-nvidia-196-75-drivers-can-kill-your-graphics-card/
267.52 http://www.gamespot.com/forums/pc-m...ce-driver-26752-could-kill-your-590-28349443/
320.18 WHQL http://modcrash.com/nvidia-display-driver-damaging-gpus/
364.47 WHQL http://wccftech.com/nvidia-users-beware-latest-drivers-damage-pc/

AMD "Beta" drivers have been far more stable over nvidia "WHQL" drivers, so thanks but no thanks.
 
Are you being serious or just trolling. The latest WHQL drivers by nvidia have been an absolute disaster http://wccftech.com/nvidia-users-beware-latest-drivers-damage-pc/ Some people have had systems not starting up and in a constant loop and all kinds of other problems. And this isnt the first time either, especially since Win10 (DX12).

196.75 WHQL http://www.zdnet.com/article/warning-nvidia-196-75-drivers-can-kill-your-graphics-card/
267.52 http://www.gamespot.com/forums/pc-m...ce-driver-26752-could-kill-your-590-28349443/
320.18 WHQL http://modcrash.com/nvidia-display-driver-damaging-gpus/
364.47 WHQL http://wccftech.com/nvidia-users-beware-latest-drivers-damage-pc/

AMD "Beta" drivers have been far more stable over nvidia "WHQL" drivers, so thanks but no thanks.
Did not know that... good to know tho.

And no... my last card HD7950 was unstable on my X99 mobo for every driver release installed. Would constantly (every 15 min in Blizzard games) reset graphics driver so yes I am dead serious for me it was the worst gfx hardware experience I'd had. Been lucky to not have any card brick itself tho.
 
I know of the "Known issues" section. Here is the link

http://support.amd.com/en-us/kb-articles/Pages/AMD_Radeon_Software_Crimson_Edition_16.3.aspx

The only issue you are having that is on there is from the division and that's to be expected, that's a new game.

According to hardware forms, Crimson should have fixed any raindow six siege issues. Many people who were having problems before-hand aren't after installing Crimson.

Can you try to run your Cross-Fire setup on a game that you know should run well (other than something you have tried so far)? Also, these two cards are the same right? You should also make sure that they are running the same memory type as well. Sometimes OEM will mix memory manufacturers on cards and that can cause issues in Cross-fire.

I run Dirt Rally in Crossfire and it runs great.

Rainbow Six hasn't been able to run in Crossfire since 15.12, then it was corrupted textures. Star Wars doesn't bother me because it's between rounds at the loading screen.

16.2.1 in Rise of Tomb Raider got me a still over my video in some instances.
 
Back