"Please dont put words in my mouth 

The OP is "WARNING: 320.18 Drivers are Killing GPU's" 

You have posted no evidence that this is occurring other than your having problems, and only typed words to back it up. 
Please show your "experience" levels and document this issue -or- I will lump you into the novice user error group"


This is the exact same response I gave to people on Overclock.net in their thread of the same name.
Nobody shows any evidence.....inb4 a youtube video of you with the problem isn't evidence.
Everyone with issues gives a one paragraph reply which indicates they didn't read through the thread.
If they had they would give more information not just "having issues".   

No mention of NV experience, installing with a OC program running etc.  their install method etc.

Nobody said RTSS is bricking cards and if you read it that way....well it is pretty obv why you are having issues.  Skimming a thread and not knowing what is being said and forming an opinion while in a haze of confusion is just stupidity personified.

Thanks Maniacvvv and other sober minded users here.  I am done with this topic. Another day of BF3 maxed and no issues.   

maskedmenace

Look, I'm not standing here saying this is going to brick every card...That's just stupid.

What I am saying is that with Fermi specifically, vendors are saying there are problems. "We", those who own computer businesses and some of these guys build 100/week compared to my 2/3, are saying there are problems with 320.18. Particularly in regards to Fermi. (Referring to their customers with active Fermi cards)

Been in this business for almost a decade, long enough to know that if load is being taken to 100% and voltage profiles are swapping (Which was actually reported by 5/6 users on OCN, [H] and Tom's) then you will, eventually, have a couple dead cards.

I don't need a walk-through of how to install a driver -- I don't need a lecture on minority or majority -- People in general are having issues with this driver, more comparably then previous. That's all I care about.

Again, I'm not standing on a pedestal and saying EVERYONE is having issues, I'm saying that it's absolutely POSSIBLE for a few people to have real issues with this driver release.

I just finished another build not but 15 minutes ago, fresh everything, GTX 770's for a friend -- Once again on 320.18 ONLY INSTALLING WHAT'S NECESSARY, it crashes out of every bench I try to load...In fact, while I'm typing this it just got a nvlddmkm.sys...

To me, this is a failed driver launch. To other vendors this is a failed driver launch. To hoards of other users, this is a failed driver launch. -- It is what it is.

 I just came from AMD and their driver team is skeletal you wait months for a fix to a bad driver stuff happens on both sides of the pond.  Willing to bet the next nvidia WHQL comes out quick.  

It is only a failed launch to people who can easily just roll back to the last driver. If they do that improperly or fail to realize NV experience may have edited configs and a simple driver roll back won't solve the issue.  Numerous people with the multi colored on Overclock.net have solved it by rolling back to the prior driver and generating a new config.   Please link me something that shows evidence of an actual dead card.  Until then it is simply a case of people thinking a roll back is all that is needed as far as everything I have read. 

What most likely really happened to some users(conjecture)
-Kid has multi color issue in BF3 on new driver express install
-He rolls back issue persist
-"Nvidia driver killed my card must post everywhere then RMA!!!!"
-In reality his game config is altered...NV experience is now gone uninstalled when he did his clean prior driver install and the screwed  up configs remain.
-New card comes in mail issue persists
-New thread inc:  Nvidia driver kills my entire computer 

I have tested the latest driver with my card (GTX570) No problems here.
 
As usual, did clean install with only video driver, PhysX, and HD audio driver checked. (I normally would leave out HD audio, but I am currently using a TV for a monitor and using the TV's speakers)
 
I have noticed no increase in temperature or voltage under load compared to the previous driver. Tested with Arma 2 and Arma 3.
 
It is a good idea to always perform a clean install, and install only the driver components that you will be using.

OMG A FURRY

Unwinder
Excellent, now RTSS name is also associated with killing GPUs in mind of average newbie reading this thread. Thanks a “lot", maniacvvv, now nonsense about “RTSS killing GPUs”

 
I think you may have misread something. No one is blaming RTSS for the problems caused by the new component that was added to the latest driver...

Unwinder 
So do at least one real thing for community and replace me, spend a few years of your life on coding some free RTSS replacement for a company.

 
You should not be so upset every time you perceive that someone has blamed your software for something happening to their system. There will always be people complaining about any and every piece of software that exists, deal with it.

Please stop taking it out on all Precision users. The RTSS is an important and useful component.

Agreed. 

Thoth42

So many animals talking in this thread....:D

Off-topic. Reported.
 
Jk rofl, ikr, I like there are a few other fuzzies around here other then me. I'm normally the only one (insert forever alone face here).

Unwinder

Excellent, now RTSS name is also associated with killing GPUs in mind of average newbie reading this thread. Thanks a “lot", maniacvvv, now nonsense about “RTSS killing GPUs” is being blindly cloned by idiots across different forums. You don't seem to have even a basic understanding of RTSS functioning principles but sadly post  tutorials related to "RTSS corruption during driver install", hope your FAQs and the moments of fame you're receiving after posting them make you happy.
Anyway, I planned to remove RTSS from Precision completely after discussion of your previous posts. Seeing it as a separately installable application is a direct result of our last dialog and the problems I had because of your “guides”. But Jacob asked me to keep OSD feature and I was stupid enough to agree again and allow Precision users to install RTSS at least optionally. I'm sorry but I'm done with it. It is ok for me that unlike commercial Precision application, the company doesn't pay even a single cent for OSD server, it is a hobby and it was interesting to develop OSD part of functionality freely during many years. But constantly coming here and wasting time and nerves on defending RTSS against such posts and doing it RIGHT HERE at EVGA ground is beyond any limits. It costs nothing to company, it cost me time, nerves and reputation because of such posts. I don’t need it anymore, sorry.  
So maniacvvv, with your guides you’re trying to appear like a person knowing everything about the things you’re discussing, including RTSS, drivers, 3D API hooks and so on. So do at least one real thing for community and replace me, spend a few years of your life on coding some free RTSS replacement for a company. And thanks to everyone who liked OSD and supported it, but I cannot longer resist this RTSS related hell here and absolutely cannot continue supporting it in EVGA Precision product. Sorry and bye.

To be fair to Maniac I consider my self a novice/moderate user and I didn't read it like that.  I have used the Riva tuner OSD for the past two years with MSI Afterburner and the framerate limiter literally saved my life in Skyrim.  The fact that it is optional is also amazing and I think part of the mis understanding.  Sorry if I am incorrect because I just went from MSI AB on an HD6970 to using Precision on a 770 SC but I read that you said you made the installer separate and I noticed that when installing precision.

I think what maniac(if I am wrong then I apologize) was saying was since they are now essentially two installs in one installer just to be safe to uninstall RTSS first > reboot then uninstall precision > reboot and then proceed to do whatever you are doing with drivers.  In the past with my last card I always just turned off MSI AB(and thus the riva tuner) prior to doing any driver swapping and that worked fine on its own.  

The way I read it was just a super safe way to ensure that after each uninstall you do a reboot before taking the next step.  I didn't walk away from the thread thinking anything ill of RTSS or Precision.  The only thing I left the thread with ill thoughts of was Nvidia experience.  I was skeptical about that anyway since I personally am 100% sure I know how to better set up my games settings than some automated program. 

I hope you will reconsider.  Your software is pretty invaluable to lots of members of overclock.net where I spend most of my forum time.  

Unwinder

Excellent, now RTSS name is also associated with killing GPUs in mind of average newbie reading this thread. Thanks a “lot", maniacvvv, now nonsense about “RTSS killing GPUs” is being blindly cloned by idiots across different forums. You don't seem to have even a basic understanding of RTSS functioning principles but sadly post  tutorials related to "RTSS corruption during driver install", hope your FAQs and the moments of fame you're receiving after posting them make you happy.
Anyway, I planned to remove RTSS from Precision completely after discussion of your previous posts. Seeing it as a separately installable application is a direct result of our last dialog and the problems I had because of your “guides”. But Jacob asked me to keep OSD feature and I was stupid enough to agree again and allow Precision users to install RTSS at least optionally. I'm sorry but I'm done with it. It is ok for me that unlike commercial Precision application, the company doesn't pay even a single cent for OSD server, it is a hobby and it was interesting to develop OSD part of functionality freely during many years. But constantly coming here and wasting time and nerves on defending RTSS against such posts and doing it RIGHT HERE at EVGA ground is beyond any limits. It costs nothing to company, it cost me time, nerves and reputation because of such posts. I don’t need it anymore, sorry.  
So maniacvvv, with your guides you’re trying to appear like a person knowing everything about the things you’re discussing, including RTSS, drivers, 3D API hooks and so on. So do at least one real thing for community and replace me, spend a few years of your life on coding some free RTSS replacement for a company. And thanks to everyone who liked OSD and supported it, but I cannot longer resist this RTSS related hell here and absolutely cannot continue supporting it in EVGA Precision product. Sorry and bye.

I like it. However, Precision DID fry a card of mine with the bug where logging out and back in would make the card's fan stick to 40%, good job buddy. Glad you fixed that bug. You have always been my favorite narcissist on EVGA forums. Keep up the proud work!  I am sure someone would pick up the slack if you were gone, God! 

XrayMan

Baltothewolf

Thoth42

So many animals talking in this thread....:D

Off-topic. Reported.

Jk rofl,

 

                

 
More OT: I just... I fail to see the logic in blaming the driver when only certain GPU's are having problems, now, if there was a fan not working issue with a driver (which happened a long time ago back in the 2xx drivers) then yea, that would be a series issue... But if the DRIVER was broken, every user would be having problems, not just some. They are all the same chip, while no 2 clock the same or whatever, they are still the same darn chip.

Baltothewolf
More OT: I just... I fail to see the logic in blaming the driver when only certain GPU's are having problems, now, if there was a fan not working issue with a driver (which happened a long time ago back in the 2xx drivers) then yea, that would be a series issue... But if the DRIVER was broken, every user would be having problems, not just some. They are all the same chip, while no 2 clock the same or whatever, they are still the same darn chip.

That's not true at all, actually.
 
There are thousands of examples of your bolded statement being incorrect.
 
For example, i can run 680's that prefer 320.18, they work fine/well with my hardware combination...However, for your they're terrible...So bad that your 3D Mark score, plummets...So, you revert to 314--...Or even a beta driver.
 
Generally with the same hardware there aren't issues but, what 2 enthusiasts on this website have the same EXACT hardware? Or, in the entire "driver network"??? 
 
The underlined is also not entirely correct.
 
This is hard to explain unless you really understand it so, I'll try to TLDR this.
 
Say your cores are advertised at 1000/1200 bla bla, right? Well, some of those chips couldn't hit that mark, stock. So, let's say we have a "bad chip" and it hits 900/1000 24/7. Well, that's not an advertised speed so, that card is overclocked to reach the advertised speeds. So now that 900/100 is 1000/1200 with a 5% overclock. -- This is actually...Business as usual and has been an industry standard for decades.
 
Still with me?
 
Now add in a voltage problem like some are experiencing or, a voltage profile swap or, a fan profile swap or, the cards constantly maxing to load...And that card that was struggling originally with that 5% overclock is now on the verge of death trying to cope with what the driver is putting it through.  -- There is a strong likelihood that this card, may die.
 
What I'm saying and have said the entire time is that vendors are reporting issues with the driver itself, maxing out to full load and swapping voltage profiles. If I'm a COMMON USER, I click next, express install and install everything. That is NOT THE COMMON USER'S FAULT...That is 100% the fault of Nvidia for having a corrupt experience profile or whatever you want to refer to it.
 
When you combine the COMMON USER that does not visit OCN/Tom's/[H] etc, I almost guarantee you this situation has already occurred where, more than likely, a Fermi fried...They don't know how to take screenshots or, post them for all of us, all they know how to do is call Dell/Alienware/Falcon or whoever and get a replacement. (Which according to vendors I spoke to yesterday, had already been happening btw)
 
Is there HARD evidence of this driver blowing up cards? As far as I've actually SEEN, no...But, if people are calling in warranties, specifically after an update, once again, I give that credence.
 
You can believe whatever you guys want. I'll do the same.

2themax

I've had exactly this problem with my brand new GTX780 SC ACX.

It's exactly like this:
you will have to add www . youtube .com before since I have not made enough posts before this.
/watch?feature=player_embedded&v=g7iGxZp94wE

So I'm reverting now to 314.22 

Edit: Can't even install 314.22, says that no product is found. Only driver I seem to be able to install is 320.18...

 
What is your hardware config? whats the extra videocard? What OS are you using?  
 
Here is a screenshot of your OSD from the video  

 
-->You are running a outdated version of Precision -and- the RTSS OSD
Go back and read page two of this thread where I posted the fix for BF3
 

maniacvvv

2themax

I've had exactly this problem with my brand new GTX780 SC ACX.

It's exactly like this:
you will have to add www . youtube .com before since I have not made enough posts before this.
/watch?feature=player_embedded&v=g7iGxZp94wE

So I'm reverting now to 314.22 

Edit: Can't even install 314.22, says that no product is found. Only driver I seem to be able to install is 320.18...

What is your hardware config? whats the extra videocard? What OS are you using?  

Here is a screenshot of your OSD from the video  


-->You are running a outdated version of Precision -and- the RTSS OSD
Go back and read page two of this thread where I posted the fix for BF3

Thats not my video. I just got the exact same artifact error.
 
My setup is;
Intel Core i7-4770k
16gb Corsair ram
Sabertooth Z87
and EVGA Geforce GTX 780 SC ACX..
 
But I shall check your previously post regarding BF3 :)
 

What is causing the card to fry is NVidia experience client, it make the gpu go at 100% load when the screen turns off (after 10 or 15 minutes power plan) after you hit a key or move the mouse the gpu returns to normal (idle), so, the solution: end the process in task manager.
 
This ^^ is for the gtx 770,
 
hope this helps

earthlight1

What is causing the card to fry is NVidia experience client, it make the gpu go at 100% load when the screen turns off (after 10 or 15 minutes power plan) after you hit a key or move the mouse the gpu returns to normal (idle), so, the solution: end the process in task manager.

This ^^ is for the gtx 770,

hope this helps

 
NOPE!  I Have NEVER done any sort of express install.  With AMD I don't even install CCC.
Anyway...back on topic...
I had an EVGA 780GTX ACX SC and got these artifacts in BF3 (and HAWX 2).
Fresh Windows install, 320.18 drivers with only Display Driver and PhysX checked, no Precision or RTSS installed (I did install it later).
Artifacts in BF3 - 
Here is a video:
http://www.youtube.com/ed...d=e5EJwNxSEFU&ns=1
I sent the card back.  New one is on the way.  I wish I had found this thread before, however, I'll be spared the frustration the second time around.

 
Ironically, last night I got the first BSOD I've had for a couple of years (outside of tweaking new CPU overclocks), and certainly the first BSOD I have had on my current system (RIVF, 3930k, 2xGTX680FTW)... I was playing GW2 at the time. I don't know what caused the BSOD, just as likely completely unrelated to this new driver, buy I have now reverted back to 314.22 just to play it safe. No BSOD since then.. keeping fingers crossed though. :)
 
 

Biohazardsperm,
Do you mean Realmware? I had it installed before with my 7970, but on this fresh install of windows, I did not have it installed.
From everything I've read regarding BF3 and drivers the 306.97 version is the best. Those are how old? So much for Nvidia having much better drivers than AMD.