7970 load temps too good to be true.. or is Furmark not pushing my card enough?

I recently installed a Watercool Heatkiller GPU-X³ 79X0 waterblock on my 7970 and added it to my loop that consists of:

XSPC dual bay res/D5 pump combo > EX240 (with 2x GT AP-15 fans) > XSPC Raystorm CPU Block > 7970 Heatkiller GPU Block > EX240 (with 2x XSPC Xinruilian 1650rpm fans) > Back to res/pump

Here is a picture of my setup:



I'm a bit of an overclocking n00b, having only dabbled with my 2500K at bit before i added water to my system, and my old 6870s wouldn't handle an overclock of more than 50mhz without causing huge stability issues. I also wasnt expecting much from my watercooling setup, especially because one of the rads exhausts heat into the case.. So i was very happy today to find that i could over-clock my 7970 to 1200Mhz GPU clock and 1600Mhz memory clock and run a 1080p Furmark benchmark with no issues. What surprised me the most is that i am getting 100% load temps of only 35 degrees C on the card D:



I am in the process of downloading 3DMark 11, but its taking ages due to slow internet at my girlfriends house.
What I wanted to know is if Furmark is a good program to use to put my GPU under 100% load?, and if a temperature of 35 degrees C is actually reasonable for such a high overclock.. or is the temp sensor in my 7970 giving falsely low readings? I am using Sapphire Trixx to OC, and monitoring temps/clocks with GPU-Z and Trixx. I get idle GPU temperature around low to high 20s. When running Prime95 torture test on my i5 2500K at 4.2Ghz I get temps around 45-52 degrees C.. and i thought my GPU would be the one creating more heat.
Edited by beanscene - 6/25/12 at 9:45pm

Thanks for the feedback guys, i've been testing with Heaven DX11 and its getting 38C when tessellation is maxed. Guess I just expected it to be higher... Im even happier that I went to watercooling now
Although my 1200/1600 overclock was perfectly stable with Furmark when I tried doing anything else it went into struggle town hahaha, so that definitely was too good to be true.

I'm using 12.6 beta drivers.. but i see you are using 12.7? Not sure if that is somehow causing a problem? I will run Furmark again at the same clock speeds and report back, if I get the same results I might revert back to 12.4 or 12.3.