The Test

For the review of the R9 380X we’ve had to make a few accommodations to our GPU testing protocol since our last major video card review, which we'd like to note.

Civilization: Beyond Earth has been deprecated, as the Rising Tide update has removed the built-in “lategameview” benchmark. Meanwhile AMD’s launch drivers for the R9 380X, Catalyst 15.11.1 Beta, are unfortunately not as solid as we’d like to see, as they have a repeatable issue with Far Cry 4 that causes it to crash with various AMD cards, including the R9 380X. As a result we’re unable to benchmark Far Cry 4 on the 380X at this time. Finally, we’re also unable to include compute benchmarks for R9 380X at reference clocks, as AMD’s drivers do not honor underclocking options with OpenCL programs.

CPU: Intel Core i7-4960X @ 4.2GHz
Motherboard: ASRock Fatal1ty X79 Professional
Power Supply: Corsair AX1200i
Hard Disk: Samsung SSD 840 EVO (750GB)
Memory: G.Skill RipjawZ DDR3-1866 4 x 8GB (9-10-9-26)
Case: NZXT Phantom 630 Windowed Edition
Monitor: Asus PQ321
Video Cards: AMD Radeon R9 390
AMD Radeon R9 380X
AMD Radeon R9 380
AMD Radeon R7 370
AMD Radeon HD 7970
AMD Radeon HD 7850
NVIDIA GeForce GTX 970
NVIDIA GeForce GTX 960 (2GB)
NVIDIA GeForce GTX 660
Video Drivers: NVIDIA Release 358.50 Beta
AMD Catalyst Cat 15.11.1 Beta
OS: Windows 8.1 Pro
Meet the ASUS STRIX R9 380X OC Battlefield 4
Comments Locked


View All Comments

  • CaedenV - Monday, November 23, 2015 - link

    My guess is that these cards are factory OC'd, which means that they would need to be underclocked to run an apples-to-apples comparison at true 'stock' settings.
  • Zeus Hai - Monday, November 23, 2015 - link

    Can anyone confirm that AMD's Frame Limiter still doesn't work on Windows 10?
  • nathanddrews - Monday, November 23, 2015 - link

    That's news to me.

    Just for you, I tested it using my i3-2100/HD7750/W10 test mule. VSync globally disabled in CCC, VSync disabled in Dota 2, Frame Target set to 60fps. Steam overlay shows 60fps and I see no signs of tearing or stuttering. To my knowledge, it never stopped working.
  • Zeus Hai - Monday, November 23, 2015 - link

    Hmm.., it should have some tearing because it doesnt really sync with the monitor anyway, mate. Can you set it to 65, 70, 75? Mine doesnt work in LoL, I set it to 60, but it always fires up over 150fps+
  • Dirk_Funk - Monday, November 23, 2015 - link

    LoL does have its own fps limiter, so perhaps that's causing a mix-up in the software. Also, LoL might be running in fake fullscreen mode whereas the catalyst fps limiter specifies it will "Reduce power consumption by running full-screen applications at reduced frame rates." I'm gonna go try a round of LoL now because you have me curious.
  • Asomething - Tuesday, November 24, 2015 - link

    Mine does, was just benching my new 290x and forgot to turn it off so my results were skewed by the 75fps frame cap i set.
  • nirolf - Monday, November 23, 2015 - link

    There's "ASUS R9 Fury OC" mentioned in the first table in the Overclocking section.
  • Ryan Smith - Monday, November 23, 2015 - link

  • Shadowmaster625 - Monday, November 23, 2015 - link

    Tonga is an epic disaster. It is less than 10% more efficient than tahiti in terms of performance per watt, and in terms of performance per transistor (fps per mm^2) it apeears to be actually worse. Meanwhile, Nvidia releases maxwell which outperformas kepler on both these metrics not by some paltry 10% or less, but by a very wide margin.
  • CiccioB - Tuesday, November 24, 2015 - link

    All the GCN architecture is a disaster.
    With TeraScale architecture AMD could fight with smaller dies and less W for a bit less performance.
    With GCN AMD has to compete using larger and power hungry dies that have brought it to go in red also in the graphics division, while with older TeraScale it at least could be at least on par.
    GCN is an architecture not up with that of the competition.
    DP64 presence is not the problem, as AMD has kept on reducing it influence over every GCN step (starting from 1/4FP and ending to 1/24FP) with no real results under the power consumption term. They probably could just spare few mm^2 on the die, but they are too way back with memory compression (I can't really believe they never thought about that) and their bus are way too big, expensive and power hungry.
    All the architecture is a fail. And DX12 is not going to solve anything, as if they ever raise their performances of 10% over the competition, they are still way back in efficiency both in terms of W and die size.

Log in

Don't have an account? Sign up now