LN2 Cooled Galaxy 9600 GT Breaks World 3D Records

OC-Team.be by massman @ 2008-04-05

Madshrimps cooperating with Belgium´s finest overclockers pay offs, in this article we detail the efforts of two OCTB crew members as they push a Galaxy 9600 GT past its limits using LN2. Warning: Frozen World Records Inside!

Introduction

Clocky, the Galaxian

Madshrimps (c)


Nvidia's Geforce 9600GT

It has only been 1 month since the new mid-range from NVIDIA was launched, however this launch was quickly overshadowed by the very high end 9800GX2. Time to turn the spotlight back on this more budget friendly card.

Our colleague reviewer Geoffrey tested this custom Galaxy samples with promising outcome, delivering high performance, silent cooling and above all, an affordable price-tag. However his overclock results in that review were a little bit too basic and boring for us.

While he wasn’t looking we snuck into his test lab and took Galaxy 9600 GT 512Mb Video Card to give it a proper overclocking session.

Let’s quickly recap why the 9600 GT in general, and especially the Galaxy version, makes for a good mid-range video card.

The Galaxy GeForce 9600GT 512MB OC Xtreme Tuner edition:

Madshrimps (c)


+ High performance
+ Silent Cooling
+ Lowest consuming mainstream video card
+ Low GPU temperatures
+ Dual BIOS
+ Xtreme Tuner software
+ Tweaked Anti-Aliasing engine
+ Affordable price-tag of ~€180

- Does not add much value for money compared to reference 9600 GT
- Moderate overclock due to issue's in early board design
- not HDMI compatible out-of-the-box


Not long after that article was released, we were informed that the moderate overclocking has little to do with the design of the card itself, but with the design of the 9600GT.

Apparently, NVIDIA decided to change the ways clocks are being build up. Earlier, a 27MHz crystal was used; the clock frequency got multiplied and divided until you get the final clock speed, 650MHz for example. With GeForce 9600GT the GPU core frequency is partially based on the PCIe speed, which makes it possible to overclock the card without the user knowing it is overclocked. Geoffrey's test system had a PCIe bus at 110MHz, and thus the card was running overclocked without him knowing. To read more about this problem, please check out the following articles:

  • Shady 9600GT trick
  • 3DMark06 practical example, and more info still

    Galaxy 9600GT

    In our previous Galaxy overclocking article we modified a Geforce 8600 for extreme performance, this time will be no different, here’s what you can expect to find in our 9600 GT article:

  • Voltage modifications
  • Performance scaling when overclocking
  • Air cooled overclocking results
  • Ln² cooled overclocking results

    Let’s get started with the riskiest business first: volt modifications ->
  • Voltage Modifications

    GPU voltage modification:

    We start of with the modifying the amount of voltage goes the GPU, in the photos below we have noted where to solder:

    Madshrimps (c)


    Solder a 50K or 100K trimmer between the red point and the blue point in order to change the voltage of the GPU.

    Memory voltage modification :

    Madshrimps (c)


    Solder a 50K or 100K trimmer between the red point and the blue point in order to change the voltage of the Memory. Note that the blue stripe refers to ground.

    Voltage readout points :

    Madshrimps (c)


    Madshrimps' modified card:

    Let's have a look at how we modded the cards.

    Madshrimps (c)


    Attached two 50K trimmers to the card and soldered the middle pin to each other. This way, we only need to solder to a ground pin once, which makes the mod a lot cleaner.

    We soldered a molex pin to the readout point to be able to measure the voltage of the memory or the gpu core without having to twist 'n turn our way to the back of the card all the time.

    Madshrimps (c)


    We tried to hide the wire to the memory voltage chip a bit to ensure we won't be ripping it off by accident

    Test setup

    Test setup

    Madshrimps' LN² overclock setup

    Madshrimps (c)

    CPU Intel Core 2 E8500
    Cooling
  • Stock Aluminum Intel Heatsink
  • Stock Galaxy 9600GT cooler
  • K|ngp|n Dragon F1 EE
  • K|ngp|n Tek9 3.0
  • Mainboard DFI Lanparty UT P35-T2R
    Memory 2 * 1GB Teamgroup PC-6400
    Other
  • Tagan 480W PSU
  • Western Digital 320Gb SATA HDD
  • Windows XP SP3
  • ForceWare 174.53


  • We did not raise the PCIe bus because of the known issues with the relation between the pci-e bus and the core frequency of the video card.

    Benchmarks

  • 3DMark01
  • 3DMark03
  • 3DMark05
  • 3DMark06
  • Aquamark3


    Overclock teaser

    Madshrimps (c)


    Madshrimps (c)
  • Air cooled results

    How did we overclock on air

    To get you all warmed up (or rather, cooled down), let's start with some pre-bench session air cooled results. As we sat in the kitchen of Massman's residence, the ambient temperature was quite high, especially in contrary to the temperatures in the Bench room (which is the attic in this case). The overclock was therefore not as high as we'd achieved before, but it gave us a few pointers in order to know what results we could expect.

    All results were obtained using a completely stock cooled system. The video card was modified and ran at 1,35v vGpu. The nVidia drivers were tweaked quite roughly, which means set everything to performance and set lod to 4,9 (except for Aquamark which ran with lod 0). The 3DMark01 run was scrambled, so we took the time to choose the best bench order to obtain the highest possible score.

    3DMark01:

    Madshrimps (c)
    (Click for full size)


  • E8500: 4277 MHz
  • 9600GT: 850/2046/1100 MHz

    Note: Running the same vga clock speeds combined with an E6300 @ 3.5Ghz, we only reached 51k points.

    3DMark03:

    Madshrimps (c)
    (Click for full size)


  • E8500: 4277 MHz
  • 9600GT: 825/1986/1100 MHz

    3DMark05:

    Madshrimps (c)
    (Click for full size)


  • E8500: 4277 MHz
  • 9600GT: 825/1986/1100 MHz

    3DMark06:

    Madshrimps (c)
    (Click for full size)


  • E8500: 4277 MHz
  • 9600GT: 825/1986/1100 MHz

    Aquamark 3:

    Madshrimps (c)
    (Click for full size)


  • E8500: 4277 MHz
  • 9600GT: 850/2046/1100 MHz

    All in all, not that bad for a €140 on air cooling
  • Overclocking performance scaling

    Let's go a bit more into detail:

    We all know that the higher the clock frequencies of the video card are, the better your score will be. But sometimes the memory is limited by the gpu. Should the shader be linked to the gpu? What overclocks can I expect with what cooling?

    Solving these questions is important if you want to get the most out of your card. The answers are different for every card as not every card overclocks the same. If you want to be thorough, the following figures are a must.

    Overclock versus Voltage

    During the weeks of the preparation of the final bench session, I had the chance to test the clock frequencies with stock air-cooling. I have graphs ready to show, but they are not useful as a lot depends of the temperature of the environment and the card itself. Though, I will give you a few pointers.

    - The memory is very sensitive for higher voltages. Be careful when overclocking, because if you kill one memory chip, you're card is not useful anymore. Tests will show that raising the memory clock doesn't really help to get more FPS.
    - The GPU can clock very high with relatively low voltages IF the temperature stays low. When testing in the attic (room temp around 15°C) I reached 850MHz GPU stable with 1,35v.
    - Check where the limit of the shader clock lies. With my card this is 2150MHz, more Vgpu doesn't help.

    GPU, shader and memory clocks

    The frequency you set is not always the actual frequency! Most cards work with certain levels of frequencies. For instance, if you set 712MHz as GPU frequency, the actual frequency might be 718MHz. The same goes for shader and memory frequencies.

    Madshrimps (c)


    Notice how +100MHz set in Rivatuner equals exactly +100MHz real speed. It's very easy to calculate what speed you'll be working at now.

    Madshrimps (c)


    The shader clock can now be set unlinked, which means that you can overclock it separately. In theory both clocks are now working independent from each other; however, please know that the following rule always counts:

    Shader clock >= 2 x Core clock

    Madshrimps (c)


    GPU, shader and memory performance scaling

    Next up: how does increasing the frequencies translate into performance increase? We used 3DMark03's Nature test to calculate the performance and Rivatuner to overclock our card.

    Madshrimps (c)


    Gpu and shader clock are linked, as we can't overcome the rule we've stated above.. Two sets of data, one with the memory clocked at 1000MHz and one with the memory clocked at 1100MHz.

    The GPU/Shader overclock is pretty important as it keeps increasing the performance. Higher clocked memory means that the GPU/Shader performance scaling will be a lot higher. As a matter of fact, the score scales almost linearly with the raise in clock frequencies!

    Madshrimps (c)


    Many people tend to hype the Shader clock as the most important of all three. In fact, this isn’t the whole truth. The shader clock is important, but in some cases it doesn't really matter whether the shader is increased or not. As you can see, in some cases, we only get 5FPS more when clocking the shaders 150MHz higher.

    In our previous video card overclocking article with the 8600 GT, we saw less impact of the shader clock, but with the 9600GT, the shader seems to play a bigger role in the graphics card's power.

    When overclocking the card on air we noticed that the shader clock maxed out at 2150MHz. Even higher voltages didn't help us to go higher.

    Madshrimps (c)


    Is it interesting to risk to kill your memory chips due to over voltage? No, not at all. At 1000Mhz, the card is almost as fast as at 1100MHz. Raising the voltage to get higher clocks is not recommended, however, raising the voltage is interesting for another reason, which we'll get to later on in this article

    Overclocking Extreme Part one - CPU on ln²

    Cpu sponsor

    First of all, we would like to thank Alternate to lend us the same E8500 we've reviewed here.

    Madshrimps (c)


    Pictures

    Following the known saying "One picture says more than a thousand words", we bring you ... pictures, instead of thousands of words ;-)

    Madshrimps (c)

    Team is preparing the hardware (f.l.t.r: Massman, Blind)

    Madshrimps (c)

    Insulating the socket area to keep away the condensation.

    Madshrimps (c)

    Dewar ready, filled with 35L of LN².

    Madshrimps (c)

    First runs with the K|ngp|n F1 mounted.

    Madshrimps (c)

    Ow! Reached a critical temperature for the CPU, coldbug.

    Madshrimps (c)

    An older VGA container made by Piotres to the resque?

    Madshrimps (c)

    Gpu after the ln².

    Madshrimps (c)

    Ice around the socket area ... maybe more insulation next time. Luckily, we used Plastik70 to cover the board with a layer of plastik to keep the water from connecting two electrical lanes.

    Madshrimps (c)


    I can write a twenty-page book about what all went wrong that day, but I won't. Instead, here are some hints:

  • We originally wanted to attach the Tek9 3.0 container, as it's one of the better on this planet, but the mounting didn't fit exactly. It was off by inches, but luckily, K|ngp|n did everything to get an update mounting kit to Belgium as fast as he could.
  • The motherboard is slowly dieing, we presume. The CPU used to be stable at much higher frequencies, but now, the PWM area becomes quite unstable when reaching 5,5GHz. We will find out soon enough, as we've another board coming, but I'm pretty confident the DFI P35 will not be able to perform at the highest level anymore. Too bad, to be honest, it was a fantastic board!
  • The operating system was fully tuned for this benchmark session, but suddenly the drivers were corrupt and we had problems finishing benchmarks. Turns out the hard disk has issues, too bad we only noticed a few days after the benchmark session.

    Results

    Despite of the many problems, we managed to set one World Record that day: the 3DMark01 9600GT class world record. We've updated you already with this news, so no need to do that again. For those who missed out on the newspost, go check it out here

    As we were not satisfied with the first session, we decided a second one would follow as soon as the new mounting bracket for the Tek9 3.0 container arrived.
  • Overclocking Extreme Part two - Full ln²

    Pictures:

    The mounting kit arrived, we still had about 20L of LN2 left, so we teamed up again and go for another spin, and this time both video card and CPU cooled below zero!

    Madshrimps (c)

    Full bench table, including a notebook to check HWBot and chat while benching.

    Madshrimps (c)

    Almost ready to start.

    Madshrimps (c)

    Too bad we don't have four eyes.

    Madshrimps (c)

    Card heavily insulated and ready for LN2 action

    Madshrimps (c)

    Up and running.

    Madshrimps (c)

    The contact between the container and the card was excellent

    Results:

    The second day was much more promising, we had a series of good scores, however we had some typical extreme overclock issues to deal with. Let's summarize:
  • We had to re-install windows because the first SATA-drive was broken. Therefore, our setup was not tweaked the way we wanted and the scores were pretty low for these clocks.
  • The card had a cold bug around -50°C, which is very high. We've seen this issue pop up with the NVIDIA 9800GX2 as well and it seems that this issue can easily be resolved by flashing another bios. We're definitely hoping for a new bios release that solves this issue.
  • It's important to find the OVP/OCP. We ran the first couple of hours too close to the limit we had an extremely unstable system. Lowering the vGpu made it more stable and easier to bench with.
  • Please voltmod the memory as well! Not to reach at higher levels, but you need to have a higher vMem if you want to reach speeds over 1GHz core speed. We had removed the memory voltage modifications because it was fluctuating too much and in the end, we needed to lower the memory speed to 925MHz in order to keep the core running at 1GHz+.

    Despite of all these problems, we had some good results as well. First of all, we broke the 9600GT 3DMark2001SE record again ánd broke the 3DMark05 record. In 3DMark03, we took the second spot and in Aquamark3 the third place. By the time this review gets policed, these records might have been broken again, of course. 3DMark06 needs a beefier (read: Quad Core) CPU for us to get into the TOP 5.

    Madshrimps (c)


    Madshrimps (c)
    Click for full size
  • Conclusive Thoughts

    Conclusive Thoughts:

    In the end, both I and Blind were pretty happy after the two benchmark sessions. Not only did we spend 35L of LN2 this time actually getting some useful results, we learned a lot from benching a two-tube-headed system. With the two of us, it was pretty easy to keep an eye on the temperatures and overclock at the same time. And there's more, we even managed to set new world records, something we are very pleased about since the first overclocking adventure ended way too soon.

    Madshrimps (c)
    We end with three empty bottles ... satisfied though.


    The card still has a lot more left in it and we’re pretty sure we'll give it another shot in the future, however, as we've run out of cooling power and we still have other hardware lying on the bench table, in might take a while. Maxing out the card will require a better CPU/motherboard combo and a fully set-up operating system.

    We'll try to keep you updated on the coldbug issue, so as soon as we find out more, we'll inform you.

    Only thing that rests me now is to give credit to everyone that made this article possible:

  • Blind for the hours of LN² fun
  • Igor from Galaxy for providing the card and giving the possibility to take this one to the extreme
  • Raphaël from Alternate for providing the E8500
  • Geoffrey, our local vmod guru, who found the modifications without having a datasheet to his disposal
  •   翻译: