Quote Originally Posted by v_rr View Post
It´s not rivatunner bug.
Actualy is right the article in the first post.
OMG LOLOLOLOL

The article says rivatuners bugs because it reads the final clock by using the gpu multiplayer x 27mhz ALWAYS, as you only find 27mhz crystal clock on the PCB, BUT this is the memory clock generator.

As I managed to test this bug with destr0yer, he's readings at stock clocks (675mhz) were 729mzh with rivatuner monitoring. Do you know why? Because:

675mhz:25mhz=27; multiplier27x27mhz= 729mhz

Then, I asked him to raise core clock 25mhz, so the multiplier would increase by 1. Like, 700mhz:25mhz=28
So, multiplier28x27mhz=756mhz, and he confirmed that happened, rivatuner was now reading 756mhz with hw monitoring.

Did you understand it or should I make a draw?

God damn it man, read the damn thread!