OC: Power, Temperature, & Noise

Our final task is our look at GTX 670’s overclocking capabilities. Based on what we’ve seen thus far with GTX 670, it looks like NVIDIA is binning chips based on functional units rather than clockspeeds. As a result GTX 670 could have quite a bit of overclocking potential, albeit one still limited by the lack of voltage control.

GeForce 600 Series Overclocking
  GTX 670 EVGA GTX 670SC GTX 680
Shipping Core Clock 915MHz 967MHz 1006MHz
Shipping Max Boost Clock 1084MHz 1188MHz 1110MHz
Shipping Memory Clock 6GHz 6GHz 6GHz
Shipping Max Boost Voltage 1.175v 1.162v 1.175v
       
Overclock Core Clock 1065MHz 1042MHz 1106MHz
Overclock Max Boost Clock 1234MHz 1263MHz 1210MHz
Overclock Memory Clock 6.9GHz 6.6GHz 6.5GHz
Overclock Max Boost Voltage 1.175v 1.162v 1.175v

Because of the wider gap between base clock and boost clock on the GTX 670 we see that it doesn’t overclock quite as far as GTX 680 from a base clock perspective, but from the perspective of the maximum boost clock we’ve slightly exceeded the GTX 680. Depending on where a game lands against NVIDIA’s power targets this can either mean that an overclocked GTX 670 is faster or slower than an overclocked GTX 680, but at the same time it means that overclocking potential is clearly there.

We’re also seeing another strong memory overclock out of a GK104 card here. GTX 680 only hit 6.5GHz while GTX 690 could hit 7GHz. GTX 670 is only a bit weaker at 6.9GHz, indicating that even with the relatively small PCB that NVIDIA can still exceed the high memory clocks they were shooting for. At the same time however this is a luck of the draw matter.

The EVGA card meanwhile fares both worse and better. Its gap between the base clock and and maximum boost clock is even larger than the reference GTX 670, leading to it having an even lower overclocked base clock but a higher overclocked maximum boost clock. The real limiting factor however is that it couldn’t reach a memory overclock quite as high as the reference GTX 670 – again, luck of the draw – which means it can’t match the overclocked reference GTX 670 as it’s going to be more memory bandwidth starved more often.

Moving on to our performance charts, we’re going to once again start with power, temperature, and noise, before moving on to gaming performance. We’ll be testing our GTX 670 cards at both stock clocks with the maximum power target of 122% (170W) to showcase what is possible at validated clockspeeds with a higher power cap, and a true overclock with a maximum power target along with the largest clock offsets we can achieve.

Not surprisingly, since we’re almost always operating within the realm of the power target as opposed to the TDP on the GTX 600 series, our power consumption closely follows our chosen power target. Cranking up the power target on the GTX 670 for example to 170W puts us within 6W of the GTX 680, which itself had a 170W power target in the first place. This is true for both Metro and OCCT, which means power consumption is very predictable when doing any kind of overclocking.

This also means that power consumption is still 18W-30W below the 7970, which in turn means that if these overclocks can close the performance gap, then the GTX 670 still has a power consumption advantage.

As to be expected, with an increase in power consumption comes an increase in load temperatures. However the fact that we’re only able to increase power consumption by about 30W means the temperature rise is limited to 4-5C, pushing temperatures into the low 80s. This does end up being warmer than the equivalent GTX 680 however due to the 680’s superior heatsink.

Finally, when it comes to noise we’re also seeing the expected increase, but again it’s rather small. Under Metro the amount of noise from the reference GTX 670 rises by under 3dB when pushing the power target higher on its own, while it rises 3dB when adding in our full overclock. Again the smaller cooler means that the GTX 670’s fan has to work harder here, which means our gaming performance may be able to reach the GTX 680, but our noise is going to slightly exceed it. As a point of reference, in the process we’ll also exceed the GTX 580’s noise levels under Metro. Still, in both OCCT and Metro none of our GTX 670 cards exceed the Radeon HD 7900 series, which means we've managed to increase our performance relative to those cards without breaching the level of noise they generate in the first place.

Power, Temperature, & Noise OC: Gaming Performance
Comments Locked

414 Comments

View All Comments

  • CeriseCogburn - Sunday, May 13, 2012 - link

    This is your false claim about obviously. It's your and Charlie D's semi-accurate hit piece opinion and nothing else.
  • dagamer34 - Thursday, May 10, 2012 - link

    Products actually have to be consistently available for significant price drops like what you want to happen. Right now, if you need a high end card TODAY, waiting around for a GTX 680 isn't really an option, you'll have to go for the 7970 and AMD knows that.
  • CeriseCogburn - Thursday, May 10, 2012 - link

    Nope, 670 is all over the egg. Sorry you're late with that crap, and it's USA only BTW concerning 680 - the rest of the non obama world isn't suffering and can you really blame the asain(China/ commie cap government) manufacturers ?
  • anubis44 - Friday, May 11, 2012 - link

    "In the end they can't keep GK104 in stock anywhere and they still manage to beat AMD convincingly in both price and performance."

    You mean nvidia can't seem to make any. According to this article, nvidia has only been able to make a fraction of the GK104s that AMD has made Tahitis:

    http://semiaccurate.com/2012/05/08/nvidias-five-ne...

    That's what happens when you don't understand the manufacturing process you're moving to. You design a chip that's so ambitious, the failure rate is spectacular. AMD (and ATI before) on the other hand are much more familiar with the limits of successive process technology at TSMC, hence they are getting higher yields per wafer despite having a slightly larger die size, even without neutering their GPGPU compute circuitry like nvidia did.
  • eddman - Friday, May 11, 2012 - link

    I wouldn't put too much weight in charlie's opinionated so called articles.
  • CeriseCogburn - Friday, May 11, 2012 - link

    If you read them on nVidia, and it is painful to see the twisted incoherent lies and completely contradictory links that disprove his stated reason for posting them or simply do not contain what he claimed they do, any bit of weight is too much weight at all.
    It's an amd fanboy firestarter flamer site, charlie's biggest purchase is red tipped matches and gasoline in a red can.
  • chizow - Sunday, May 13, 2012 - link

    Can't agree with this for a lot of reasons. Maybe in the past with the huge GPU dies, but GK104 is *SMALLER* than Tahiti so there's really nothing ambitious about it.

    For capacities, Nvidia and TSMC have very close relationships and we know for a fact Nvidia is selling 2 GPUs for every 1 of AMDs, so Nvidia has an advantage there in terms of orders placed as well.

    There's no reason to believe Nvidia is at any process disadvantage relative to AMD on 28nm, if anything everyone is supply constrained as other players try to move in (like Apple).

    The fact there's plenty of GTX 670s still available after 3 days after launch with EXTREMELY favorable reviews tells me supply is excellent, and that Nvidia is only supply constrained on the high-end with perfect ASICs splitting good die between GTX 680 and 690.
  • chizow - Thursday, May 10, 2012 - link

    Per usual Ryan, very relevant observations and interesting insight in regard to the changes Nvidia has made.

    I think I would take some of your first page insights a bit further:

    1) GTX 680 is probably already heavily "overclocked" and binned to achieve a SKU Nvidia may not have planned originally, in order to beat the 7970 with a mid-range ASIC.

    2) We will probably see an even more heavily harvested GK104 chip soon, given how little GTX 670 cuts from GTX 680 (just 1 SMX), but Nvidia can't cut too much without significantly impacting performance.

    3) Pricing as you've laid out nicely, is probably $50-$100 too high across the board for all of these 28nm parts somewhere in the +20-25% premium range based on relative performance and historical pricing.

    There's quite a few minor grammar errors throughout your article, nothing a quick proofread won't correct, but the content is excellent as usual.
  • Iketh - Thursday, May 10, 2012 - link

    will you take the words "historical pricing" and remove them from your vocabulary? PLEASE?
  • chizow - Thursday, May 10, 2012 - link

    Its obvious the term is completely foreign to many here, including yourself, so until its well understood what it means and why its important and relevant to the discussion, I'll continue to use it.

    "Those who do not learn from their mistakes are doomed to repeat them".

    You're not even in a position to learn from your mistakes when you don't even understand the importance of "historical pricing".

Log in

Don't have an account? Sign up now