enigma442

As we wait to see what the next driver has in store.......a little pick. (i just had to.)

 

Should be sparks not fire...these cards don't get hot at all.
Still was hilarious. 

I have not installed these drivers yet as I have no need to. However, I get today my GTX 770 Twin Frozr and really don't want to install these drivers with all the problems I have read about.

Nothing from Nvidia? This is a bit ridiculous. Even if there are user errors when installing and uninstalling drivers, I cannot see this many people having issues based on this situation alone.

It bothers me greatly that installing a driver COULD burn my card up, especially since I will be installing a brand spanking new 770. I know I could RMA but I should not have too becuae of a faulty driver.

_Nite_

You can modify the 314.22 drivers to give support to the GTX 770, here is the guide

http://forums.guru3d.com/showthread.php?t=377158

Here you guys go. This is my modified 314.22 x64 drivers ready to go with the GTX 770 compatibility already added. Enjoy :)
 
http://www.mediafire.com/download/85gf69886galssv/314.22-desktop-win8-win7-winvista-64bit-english-whql.rar

Nooo thx for modified thing.

Here is a list of possible fixes that I have found on the web:
1) Set maximum pre-rendered frames to default (I usually set it to 1)
2) Turn on FXAA for BF3
3) Increase GPU voltage
4) Set all Nvidia control panel settings to default
6) Roll back drivers
 
 

Guys, I have no problem with 320.18 once I did a proper install/uninstall in safe mode. First I cleaned up with ccleaner and reg mechanic and then before install made sure afterburner was shutdown etc.... then installed just the graphics driver and physics driver, then rebooted again. All has been well. my max settings without moving the voltage are: Power-106, Core-194, Mem-233 on a stock card. I haven't seen any excessive temps or any other weird anomaly's. If you take your time and do the driver install properly you will be ok.
EDIT: Actually, I haven't even taken it apart yet to redo the TIM and lap, which ive pretty much done to every single card ive had since the Nvidia 7xxx cards.

 
Looks like these drivers killed another card, a GTX 570
 
http://forums.evga.com/tm.aspx?m=1960342
 

SeanEJohan

Yeah no problems here with 320.18 driver, in fact I've found it to be the best performer so far in my games. Since Nvidia didn't pull the driver or post any warnings, I wouldn't take the article serious. Rule of Thumb for drivers: If it isn't broken don't fix it, if your having issues with the 320.18 driver in older games like BF3, roll back to the 314.07 WHQL.

 
Nvidia can't pull the driver cause 320.18 is the only one that works on the GTX 770, if the GTX 770 had earlier drivers or beta drivers I bet they would have pulled it.

320.18 don't kill cards, I've been using it flawlessly since day 1. People need to learn how to install properly.. Go read Maniacvvv thread. Feeding the trollin fire.

I just think the 770's are garbage, they're spun out 680's, and they have a hard time beating the vanilla 680??!! I don't think its the 320.18 driver at all, at least for the 600 series their fine.

_Nite_

AzN-SoLjA

320.18 don't kill cards, I've been using it flawlessly since day 1. People need to learn how to install properly.. Go read Maniacvvv thread. Feeding the trollin fire.

and you believe maniac when he says these drivers don't kill cards? Not me

that thread I posted above is solid proof these drivers damaged a GTX 570, a fresh install of windows and older drivers afterwards DID NOT FIX IT, and he said all the drivers he loaded gave him no problems BEFORE loading 320.18 for the first time so what does that tell you?

 
-one- 570 thats goes bad during a driver change does not a "killer GPU driver" make.....
You also failed to mention, that the 570 user made -very serious- driver handling mistakes. His card could be fine... 
 
I have been keeping a very close eye on this issue, and I have not seen any cards that have been physically damaged.
*if this driver did indeed -kill- videocards, many thousands of users would be reporting it since day one. It would certainly have been pulled within 24hrs or less.
 
 
What we have here is ANOTHER NVIDIA driver release that -again- has changes in its installer and inside the driver.
This can and does cause the issues we are seeing with games and third party software.

My 680 and x3 560's are unaffected by this 320.18 troll fire. Could have been a dying card to begin with for all we know, or its fully functional but doesn't work since nobody knows how to install correctly or has potential conflicts.
 
I happily able to report ZERO issues, no crashes, no distortions, just perfection with this driver on 4 cards for a whole month now.

_Nite_

Nvidia probably does want to pull the 320.18 drivers, but they can't cause its the only ones that support the GTX 770, and the fact that they havn't even released a quick fix beta driver yet leads me to believe this is an extremely serious issue.

 
Thats ridiculous
Nvidia can and has pulled or re-released drivers in the past, and if a real issue was present would -certainly- do so.
Nvidia could pull the driver and release another with just a simple .ini change....
 
Its quite telling that the driver is WHQL and currently available as the suggested driver weeks after its release
 
*I will agree that the current GeForce Experience is not working correctly, and that the Install behavior is a booby trap...
But as far as hardware damage, not seeing that at all 
 
 

SeanEJohan

I think we all are in agreement that _Nite_ is blowing this way out of proportion. All but 2 threads I've read on this "issue," have been solved by un-installing drivers,  PrecisonX, and re-installing both again. Amazing what a difference a clean install can make!

 
the 570 thread I posted above, the OP reinstalled windows, and loaded a older set of drivers, and guess what still doesn't work, imagine that
 
Thats as clean of an install as you can get
 
But whatever, I think we can agree to disagree on this now

_Nite_

SeanEJohan

I think we all are in agreement that _Nite_ is blowing this way out of proportion. All but 2 threads I've read on this "issue," have been solved by un-installing drivers,  PrecisonX, and re-installing both again. Amazing what a difference a clean install can make!

the 570 thread I posted above, the OP reinstalled windows, and loaded a older set of drivers, and guess what still doesn't work, imagine that

Thats as clean of an install as you can get

But whatever, I think we can agree to disagree on this now

B/C  and pretty sure we all but officially established that if you let Nvidia Experience mess with stuff namely games that most people have the cloud enabled on Origin, Steam and Uplay and then reinstall your entire OS just to reinstall your games(assuming they weren't backed up) will install with their prior configs(gg cloud) and your issue would persist.  Generally speaking...

The issue you mentioned above is full of things you just shouldn't ever do when installing graphics drivers(be it nvidia or AMD).
At the least it is a terrible example to use in regard to making a statement about these drivers.  The primary failure that I see is that this wasn't made a pop up prior to driver install: Includes the production release of GeForce Experience (version 1.5) as an optional installation. GeForce Experience replaces NVIDIA Update as the easiest way to keep your drivers up to date.  
The majority of people having issues are using win8 and/or and older than 7xx card and thus have the same recourse that any AMD user with an old series card has when a driver comes out.....to not bother using it.  Others let a game config get corrupted with bad data and a driver swap most likely won't scrub your game configs on a rollback(if it does then I await the driver that makes me breakfast and finds my slippers).

You couldn't find anyone to spread your fear here so you moved right over to Overclock.net  to try and drum up some drama there.