LiuKangBakinPie
Diamond Member
- Jan 31, 2011
- 3,910
- 0
- 0
repost from "official" thread.
OK guys, I want you to pay attention to this video.
The reviewer in this video has his gtx590 at 809 core (30% overclock) memory at 2128 (20% overclock) , @ 1.05 volts (max afterburner voltage) running at 86c. Pulling over 500 watts, just like the 6990 did in the Anandtech review, so no surprises there.
Driver version 267.71.
http://www.linustechtips.com/ltt-vid...inus-tech-tips
It is VERY OBVIOUS that using the older driver was the problem. It not bad vrm's , overheating, or any other of these BS fanboy excuses.
In fact the same reviewer that blew up his gtx590 THEN used the right driver and the card ran fine.
QUOTE!
"The Swiss team tried again using the 267.71 drivers, which has the overcurrent protection built in and the GTX590 didn't fry itself."
The mistake that Nvidia made was packing the older drivers in with the gtx590 to some reviewers.
Bottom line?
Always use the latest drivers when reviewing a brand new card and for Nvidia, don't send the card to reviewer with the wrong drivers!
I now look forward to some real overclocking reviews like the one in the video I linked above.
edit: I found a good one..
Gtx590 overclocked vs 6990 overclocked using a 2600k @ 5.0 ghz.
http://www.microsofttranslator.com/B...the-titans/8
http://www.microsofttranslator.com/B...-frecventa-cpu
edit 2 : now back to my vacation. see ya around.
hi don't wanna be rude but you don't know how the driver works or how its implemented.
The voltage table is inprinted in the bios of the card where the driver reads the voltage of a table. Same way it reads the performance level of the table. A junk driver alone can't make it to go poof unless the voltage tables in the bios was wrong. Doesn't matter if its 1966 drivers. It knows nothing about the hardware. It reads it off the table which is in the bios.
So who added the table in the bios?
Or
Who modded the bios?
If the card was a Asus one then blame them. They are so stupid by zapping the pointer to the performance table by setting it to 0.
Last edited: