Nvidia cheating with #'s on the 7800GTX
THought I would share some information Viper John haad about my card.
Dude blows my mind!
"I am forcing the card to run at the advertised core clock
speed not the cheat speeds nVidia is running the cores at in 3D mode (about 40Mhz higher that
what bios is programmed for or what you set the core clock at manually ). nVidia is also defaulting
the driver to run at a "Quality" IQ setting instead of "High Quality" as a high end card should be
running at (and what ATI does BTW).
This BFG OC'ed card is advertised as a 450/650 . The bios is programmed for a 460 core clock
in 3D and the that is what both nVidia's an RivaTuner default to on the manual clock sliders (as they
should BUT when the card goes into 3D mode the core actually runs at 501Mhz or 41Mhz higher
than it is supposed to be or what you think the core will be running at.
The 3D core clock is actually set by the drivers. They read the bios to see what the 3D core clock"
is programmed for or what you are manually setting the core clock (which over rides the bios
programmed clock) and then sets that clock when the card goes into 3D mode.
Through either an error in the driver code, or a deliberate act by nVidia, the drivers are taking the
bios programmed 3D clock, or what you over ride it to manually, and adding 40Mhz to that number
and then setting the core clock genrator to the higher speed without you knowing it. I don't it is a
driver code error as NV did this before to make their cards appear faster to reviewers than they
really were at the advertised clock speeds. This behind the scene (read behind your back and
without your knowledge) 3D clock cheating appears to be confined to just the 7800's so that is
another reason to think this is deliberate by nVidia and not an accidental driver code error.
The problem with playing this stupid numbers game is if they correct the drivers to run the core at
what the bios or the manual core clock are actually set for the cards speed will drop and users
will be going "WTF", these new drivers are ****, they killed my card, they killed my computer,
they burnt down my house, they knocked the moon out of orbit, etc, etc, etc.
It will be interesting to see if FutureMark holds there approval of NV drivers that run the core higher
than it is supposed to be running. They have pulled their approval in the past for that very reason."
Hmmmmmmm
THought I would share some information Viper John haad about my card.
Dude blows my mind!
"I am forcing the card to run at the advertised core clock
speed not the cheat speeds nVidia is running the cores at in 3D mode (about 40Mhz higher that
what bios is programmed for or what you set the core clock at manually ). nVidia is also defaulting
the driver to run at a "Quality" IQ setting instead of "High Quality" as a high end card should be
running at (and what ATI does BTW).
This BFG OC'ed card is advertised as a 450/650 . The bios is programmed for a 460 core clock
in 3D and the that is what both nVidia's an RivaTuner default to on the manual clock sliders (as they
should BUT when the card goes into 3D mode the core actually runs at 501Mhz or 41Mhz higher
than it is supposed to be or what you think the core will be running at.
The 3D core clock is actually set by the drivers. They read the bios to see what the 3D core clock"
is programmed for or what you are manually setting the core clock (which over rides the bios
programmed clock) and then sets that clock when the card goes into 3D mode.
Through either an error in the driver code, or a deliberate act by nVidia, the drivers are taking the
bios programmed 3D clock, or what you over ride it to manually, and adding 40Mhz to that number
and then setting the core clock genrator to the higher speed without you knowing it. I don't it is a
driver code error as NV did this before to make their cards appear faster to reviewers than they
really were at the advertised clock speeds. This behind the scene (read behind your back and
without your knowledge) 3D clock cheating appears to be confined to just the 7800's so that is
another reason to think this is deliberate by nVidia and not an accidental driver code error.
The problem with playing this stupid numbers game is if they correct the drivers to run the core at
what the bios or the manual core clock are actually set for the cards speed will drop and users
will be going "WTF", these new drivers are ****, they killed my card, they killed my computer,
they burnt down my house, they knocked the moon out of orbit, etc, etc, etc.
It will be interesting to see if FutureMark holds there approval of NV drivers that run the core higher
than it is supposed to be running. They have pulled their approval in the past for that very reason."
Hmmmmmmm
Last edited: