Overclock.net › Forums › Graphics Cards › NVIDIA › 320.18 killed my GTX590, did it?
New Posts  All Forums:Forum Nav:

320.18 killed my GTX590, did it? - Page 4

post #31 of 36
Quote:
Originally Posted by Feud View Post

Clock speeds wouldn't kill the memory though and instead only slow it down because of errors and the error correction code in modern GPU's. Even the memory voltage is predefined in the vbios and only specific cards allow even control of it on a driver level.

All the drivers really do is create a bridge between hardware and software. This is all done on a read level and not write which is also why factory overclocked cards are treated the exact same as reference design cards. All of the hardware control of cards comes from the vbios which sets our voltage limits, clock limits, boost limits, etc.
Well, I've not had much experience killing graphics cards, but I've heard of people having cards die because of memory overclocks. It puts additional stress on the memory, and the memory is pretty sensitive. I think Mhill2029 was one of the people who told me about that.
post #32 of 36
Quote:
Originally Posted by Feud View Post

Clock speeds wouldn't kill the memory though and instead only slow it down because of errors and the error correction code in modern GPU's. Even the memory voltage is predefined in the vbios and only specific cards allow even control of it on a driver level.

All the drivers really do is create a bridge between hardware and software. This is all done on a read level and not write which is also why factory overclocked cards are treated the exact same as reference design cards. All of the hardware control of cards comes from the vbios which sets our voltage limits, clock limits, boost limits, etc.

You guys keeps on insisting that it can not happen. One guy here does bios modification for a living and he said they killed hundreds of cards because mhe messed on the bios. Nvidia also requesting those affected users to send in their cards so that they can figure out and fix their drivers. If it really is impossible for a driver to kill gpus then nvidia should have stated it right now to cover their rears, But no they did not, because they know that it can happen.

I Guess you guys know better that the guy who mods bios professionally and nvidia itself.
post #33 of 36
Quote:
Originally Posted by ghostrider85 View Post

You guys keeps on insisting that it can not happen. One guy here does bios modification for a living and he said they killed hundreds of cards because mhe messed on the bios. Nvidia also requesting those affected users to send in their cards so that they can figure out and fix their drivers. If it really is impossible for a driver to kill gpus then nvidia should have stated it right now to cover their rears, But no they did not, because they know that it can happen.

I Guess you guys know better that the guy who mods bios professionally and nvidia itself.


Messing with the bios is a user implication and not driver related. Of course messing with the bios has a chance to kill the card seeing as there are many variables controlled on a hardware level by the bios. Drivers simply interface with the bios on a read-only level. Nvidia requesting people to send in their cards is merely them quieting rumors. I have yet to hear back from anyone who has sent their card in as to whether Nvidia ever even shared their findings.

Drivers do not kill cards, users and hardware level modifications are what kill cards. Software has not been able to kill hardware in many years.


Edit: People who claim drivers killed their hardware are typically people who do bios modding, extreme overclocking, voltage changing, etc which have the highest possibility of killing their hardware. They merely cling to the nearest change in their system as to the reason their hardware died. There has yet to be someone who just "uses" his hardware normally who has experienced hardware failure truly due to drivers because it is not possible.
Edited by Feud - 6/13/13 at 1:01pm
Justice
(13 items)
 
  
CPUMotherboardGraphicsGraphics
Intel Core i7 5820K Asus X99 Deluxe MSI GTX 980 4G GAMING MSI GTX 980 4G GAMING 
RAMHard DriveCoolingOS
Crucial DDR4 Samsung 840 EVO Coolermaster Hyper 212 EVO Windows 7 Professional 
MonitorKeyboardPowerCase
Auria EQ276w Razer Blackwidow Ultimate 2013 Seasonic X750 Corsair Carbide 
Mouse
Logitech G500 
  hide details  
Reply
Justice
(13 items)
 
  
CPUMotherboardGraphicsGraphics
Intel Core i7 5820K Asus X99 Deluxe MSI GTX 980 4G GAMING MSI GTX 980 4G GAMING 
RAMHard DriveCoolingOS
Crucial DDR4 Samsung 840 EVO Coolermaster Hyper 212 EVO Windows 7 Professional 
MonitorKeyboardPowerCase
Auria EQ276w Razer Blackwidow Ultimate 2013 Seasonic X750 Corsair Carbide 
Mouse
Logitech G500 
  hide details  
Reply
post #34 of 36
Bios modded my GTX 480 around 30+ times....

Gotten different result almost every time, lower idle states, higher max voltage, PWM frequency etc etc...


Never broken a GPU in my life, i however did purposely smash a 6990 i owned, it was dog poo.
PROGENITOR
(17 items)
 
Emulator Box
(17 items)
 
The contender
(15 items)
 
CPUMotherboardGraphicsGraphics
i7 4770k Gigabyte GA-Z87X-OC Gigabyte Windforce 780Ti 3072mb Gigabyte Windforce 780Ti 3072mb 
RAMHard DriveHard DriveOptical Drive
16GB Avexir Orange 2133mhz 1TB Crucial M550 2TB Seagate Barracuda 7200 LG BDR/DVDR 
CoolingCoolingOSMonitor
OCUK Fathom with HW Labs Black Ice 240 rad Mayhem's Gigabyte Orange 8.1 64 OEM Dell U2713HM 
KeyboardPowerCaseMouse
Ducky DK-9008 Shine III MX Brown Superflower Leadex 1000w Platinum Black NZXT Switch 810 Logitech G602 
Audio
SoundBlaster Z PCI-E 
CPUMotherboardGraphicsRAM
AMD FX 8320 Vishera ASUS M5A99X EVO R2.0 Sapphire R9 290 Tri-X 4096MB Avexir Blitz 2000mhz 8GB 
Hard DriveOptical DriveCoolingOS
1TB Hitachi Deskstar + 500GB Hitachi Deskstar 7... Samsung DVDR/CDR Noctua NH-U12P windows 7 Ultimate 64-bit 
MonitorPowerCase
AOC 22" LED 1920x1080 SuperFlower Golden Green HX 550W 80 Plus Gold Xigmatek Utguard 
  hide details  
Reply
PROGENITOR
(17 items)
 
Emulator Box
(17 items)
 
The contender
(15 items)
 
CPUMotherboardGraphicsGraphics
i7 4770k Gigabyte GA-Z87X-OC Gigabyte Windforce 780Ti 3072mb Gigabyte Windforce 780Ti 3072mb 
RAMHard DriveHard DriveOptical Drive
16GB Avexir Orange 2133mhz 1TB Crucial M550 2TB Seagate Barracuda 7200 LG BDR/DVDR 
CoolingCoolingOSMonitor
OCUK Fathom with HW Labs Black Ice 240 rad Mayhem's Gigabyte Orange 8.1 64 OEM Dell U2713HM 
KeyboardPowerCaseMouse
Ducky DK-9008 Shine III MX Brown Superflower Leadex 1000w Platinum Black NZXT Switch 810 Logitech G602 
Audio
SoundBlaster Z PCI-E 
CPUMotherboardGraphicsRAM
AMD FX 8320 Vishera ASUS M5A99X EVO R2.0 Sapphire R9 290 Tri-X 4096MB Avexir Blitz 2000mhz 8GB 
Hard DriveOptical DriveCoolingOS
1TB Hitachi Deskstar + 500GB Hitachi Deskstar 7... Samsung DVDR/CDR Noctua NH-U12P windows 7 Ultimate 64-bit 
MonitorPowerCase
AOC 22" LED 1920x1080 SuperFlower Golden Green HX 550W 80 Plus Gold Xigmatek Utguard 
  hide details  
Reply
post #35 of 36
Feud. In general, I agree with you.
However, it is possible for nvidia drivers to override the card bios.
From what I've read, nvidia drivers for the GTX 590 are able to force voltage lower than what is specified in the card bios.
There were some upset GTX 590 owners would had to reduce their overclock because some drivers forced voltage to be lower.
Nvidia did that because the VRM is weak. The bios specified voltage was enough to kill the VRM.
Since software such as Afterburner and Precision can change voltage and clock frequency, then it should not be any surprise that drivers also can.
However, as you said, the default voltages are normally specified in the bios and usually not changed by the driver.

In regards to sending in cards, Nvidia did the same thing 1-2 years ago with Fermi cards.
The conclusion was, drivers are fine (except for the usual bugs of course) and that some cards are bad.
I have noticed that when a new series of cards launches, the first driver is very buggy.
I think there are a lot of bugs in 320.18 and that's the main reason why there are so many reported problems.
I personally found one bug, almost immediately after installing 320.18 (3D Vision bug in Neverwinter Online), and I immediately switched back to the previous driver.
Due to bad publicity surrounding 320.18, some people will blame all their software,hardware problems on the driver.
Edited by Partol - 6/13/13 at 4:15pm
     
CPUMotherboardGraphicsRAM
Athlon II X4 750k Asus F2A85-V MSI GTX 750 Ti Team 2x2GB 
Hard DriveCoolingOSMonitor
Kingston SSD V300 120GB Zalman CNPS5X performa + Arctic MX-4 Windows 7 64-bit Asus VW222 22" LCD 1680x1050 
PowerCase
FSP 460W Foxconn TSAA-426 
CPUMotherboardGraphicsRAM
Pentium G3258 @ 4.4 GHz ~1.38Vcore ~1.9Vccin Ri... MSI H81M-P33 Asus GTX 750 Ti OC + Thermalright HR-11 backsid... Transcend 2x2GB @ 1400MHz (5-7-5-18) ~1.62V 
Hard DriveCoolingOSMonitor
Intel SSD 330 240GB ZM CNPS5X (not performa) + 120mm fan (push) Windows 7 64bit Acer GD245HQ - 1920x1080 120Hz - Nvidia 3D Vision 
PowerCaseAudio
FSP 500W Enermax Phoenix Neo + 220mm Globefan (side) Creative Titanium HD + Beyer DT 880 - 250 ohm 
  hide details  
Reply
     
CPUMotherboardGraphicsRAM
Athlon II X4 750k Asus F2A85-V MSI GTX 750 Ti Team 2x2GB 
Hard DriveCoolingOSMonitor
Kingston SSD V300 120GB Zalman CNPS5X performa + Arctic MX-4 Windows 7 64-bit Asus VW222 22" LCD 1680x1050 
PowerCase
FSP 460W Foxconn TSAA-426 
CPUMotherboardGraphicsRAM
Pentium G3258 @ 4.4 GHz ~1.38Vcore ~1.9Vccin Ri... MSI H81M-P33 Asus GTX 750 Ti OC + Thermalright HR-11 backsid... Transcend 2x2GB @ 1400MHz (5-7-5-18) ~1.62V 
Hard DriveCoolingOSMonitor
Intel SSD 330 240GB ZM CNPS5X (not performa) + 120mm fan (push) Windows 7 64bit Acer GD245HQ - 1920x1080 120Hz - Nvidia 3D Vision 
PowerCaseAudio
FSP 500W Enermax Phoenix Neo + 220mm Globefan (side) Creative Titanium HD + Beyer DT 880 - 250 ohm 
  hide details  
Reply
post #36 of 36
Quote:
Originally Posted by Feud View Post

Messing with the bios is a user implication and not driver related. Of course messing with the bios has a chance to kill the card seeing as there are many variables controlled on a hardware level by the bios. Drivers simply interface with the bios on a read-only level. Nvidia requesting people to send in their cards is merely them quieting rumors. I have yet to hear back from anyone who has sent their card in as to whether Nvidia ever even shared their findings.

Drivers do not kill cards, users and hardware level modifications are what kill cards. Software has not been able to kill hardware in many years.


Edit: People who claim drivers killed their hardware are typically people who do bios modding, extreme overclocking, voltage changing, etc which have the highest possibility of killing their hardware. They merely cling to the nearest change in their system as to the reason their hardware died. There has yet to be someone who just "uses" his hardware normally who has experienced hardware failure truly due to drivers because it is not possible.

I'Ve made a mistake in my statement, when i said bios modding, i actually meant driver modding.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: NVIDIA
Overclock.net › Forums › Graphics Cards › NVIDIA › 320.18 killed my GTX590, did it?