Today’s Crimson Software 16.6.1 beta hotfix driver performance analysis charts the performance of 26 games focusing on the Fury X and the 290X compared with Crimson 16.5.3 hotfix drivers which we last tested for our recent SLI vs. CrossFire comparison. You can also compare today’s performance with last month’s Crimson 22.214.171.124 hotfix drivers here. AMD has released their latest June Crimson Software driver on June 5, but it is another Beta Hotfix non-WHQL driver which may give issues for users watching Blu-Ray movies or using other DRM-enabled programs. It has been well over 2 months since AMD has released a WHQL driver.
We are also featuring our newest 2016 games, Mirror’s Edge Catalyst and DOOM, and we are also including Ashes of the Singularity, Hitman, and Rise of the Tomb Raider using DX12. We will compare the performance of 26 modern games at 1920×1080, 2560×1440, and at 3840×2160 resolutions with maximum settings. We will also compare Nvidia’s top 3 cards with AMD’s current flagship performance to see if performance or if ranking has changed.
Our testing platform is Windows 10 Home 64-bit, using an Intel Core i7-4790K at 4.00GHz which turbos to 4.4GHz for all cores as set in the motherboard’s BIOS, an ASUS Z97E motherboard, and 16GB of Kingston “Beast” HyperX DDR3 at 2133MHz. The settings and hardware are identical except for the drivers being tested.
BTR’s The Big Picture, once reserved for video card reviews is now included in every driver performance analysis. We want to document the performance changes of our most recent drivers since we last tested them on Windows 10.
At R9 280X or at GTX 970 performance level and above, we test at higher settings and resolutions generally than we test midrange and lower-end cards. All of our games use average and minimum fame rates to test performance at 3 resolutions when the results make sense (generally above 25 fps average), and we use DX11 or DX12 when available and with a very strong emphasis on the latest demanding 2015-2016 AAA games.
Let’s get right to the test configuration, to the driver release notes, and then to the results.