maniacvvv

Ridiculous! 
 
While there certainly may be users have issues with this driver, it NOT killing anyones GPU 
 
What we are seeing here is NVIDIA DRIVER INSTALL ERRORS  
If you read the first link, the recovery posted is not only the stupidest driver uninstall procedure, it is of course completely WRONG. The author appears to know NOTHING about correctly Uninstalling Nvidia drivers,  correct Nvidia driver install method and Windows 8 behavior.  
 
Wake up people 
You DO NOT use a -default- Nvidia driver "EXPRESS" install -ever-   
These issues are being caused by users who have installed the GeForce Experience and/or are NOT correctly shutting down Precision and the RTSS service before installing drivers. 
 
People who use CORRECT procedure by shutting down Precision/Afterburner and the RTSS -AND- who did not install the GeForce Experience in the first place....  
-->are NOT REPORTING ANY PROBLEMS AT ALL  -none-zero- 
   
 
Turn off Precision and the RTSS -before installing drivers- and ONLY use a CUSTOM Mode install with GeForce Experience and Nvidia Update UNCHECKED 
And always put a check mark in "Perform a clean install" 

ambassador_pineapple

Now that I think about it, I have had pretty much every single game crashing on me since I updated to 320.18.  I was thinking it is because of my 4.5GHz overclock on my CPU or even a mild overclock on my 570 Asus DCII.  This is starting to make sense.  I am about to go pickup my 780 from UPS center.  Can anyone tell me if I can just use 314.22 drivers with the 780?

ambassador_pineapple

Ya.  Modifying the ini files right now.  Went back and saw the post.  Thanks for reminding me man.

maskedmenace

Everyone should know the rule with non manufacturer approved laptop drivers, due to laptop proprietary temp and power software .... 
So I'll skip that

It doesn't change the fact that it has happened and has been documented as being possible. The M17x notably had this issue because we swapped profiles...When that swap was made, the OCP profiles were swapped and over-heated cards left and right -- So your assumption that this is "Ridiculous and impossible" is in fact, not true.

So, you're debating with a vendor that a system, with 100% fresh hardware, fresh windows and fresh, everything, shouldn't work on a brand new driver? Really now? Because that's exactly what you said: 

So your NOT reporting this from a known working system, but a new build with new cards that has never worked correctly? 
That speaks for itself

I'll be sure to inform the other vendors of their fallacy. How dare we system builders expect brand new hardware, new 780's and new everything to work on fresh installs...I never knew we could be so stupid! 

Oh wait, we as a whole, disagree with you.

I believe you have Fermi and Kepler confused, but it doesnt really matter.

LOL, this gets better after each rebuttle.

I do NOT have Kepler and Fermi confused because every single individual that uses this driver does not have to have the latest and greatest to benefit from it...You know, typically on a WHQL, that's where //everyone// updates, even those with older cards?

No 2 cores in the history of this business have ever been the same. That applies for everything and is an absolute FACT in this industry. What's that mean? 

Simple. Fermi was known for having heat issues because most of the cores were OC'd to actually run at stock speeds...In fact, most of the run was OC'd @ 10% so it could even reach stock speeds.

So what's that mean with new driver? You're taking a driver profile that's been PROVEN to hit 100% load with overvolting and now tossing a card that's already overworked into that equation -- As a system builder, one that builds about 100+ enthusiast builds a year, I don't need a screenshot to prove what's possible -- Common sense would dictate that SOMEONE with a Fermi in the very least has a blown card due to the overvolting of a card that's already at max trying to hit stock.

I don't know who highlighted your initial post but, whoever did, quite frankly hasn't worked in this industry long enough.

YOU stated it was impossible. I'm telling you, directly, unequivocally, you're WRONG. 

Drivers absolutely have the capability to overheat and overload a card to the point of no return and have done so in the past regardless of it being a laptop or a desktop...When combined with a core that's already OC'd to hit stock, you //WILL// have issues...Which Fermi cards, are now proving over and over again.
This has been a probable issue since the driver was released. Once again, no 2 cores are ever the same...Should keep that in mind. 

feniks

does anybody know for sure if any problems coming from 320 WHQL were replicated in Custom Clean Install mode with only the driver itself and physx component and NOTHING else selected?

just a thought, I never had problem with that driver, but I am running 670 Kepler SLI, not Fermi.

I see zero issues on my end, not using 3D, HD audio, experience/updater thingy.

maskedmenace

maniacvvvLOLOLOL

I ran the 320.18 on Fermi cards since its release, both at stock and highly overclocked....
-->saw all of 1c difference (increase) from the previous driver, voltage behavior unchanged.
Thru testing in Heaven 4.0, Valley and Mark11... textbook standard runs, no issues seen
Got a good 30-40hrs of BF3 gameplay in on the driver, no issues seen

I just removed my 580 SLI and replaced it with Keplers
Same testing, same textbook standard runs and no issues seen
Maybe 10hrs of BF3 now, no issues of any kind seen.

No unusual temps, no voltage spikes of anykind noted at all

------------------

Your telling me its happening to you, that you can see this on your own and other systems....
But you cant even provide a simple screenshot?

Yeah right bud.
If you cannot be bothered to post a screenshot, I dont think you are being honest and I certainly dont believe you have the experience levels you claim.
A monkey can build systems.... takes alittle more to be able to take screenshots and post real data

If anyone who DOES have some real tangible proof of this behavior, I am very interested in seeing it.   

Again, YOU stated it was impossible while acknowledging that drivers HAVE destroyed a card before. Period. Done. End.

I quite frankly, don't care about your setup. Just because YOU didn't see any performance issues, doesn't mean the next guy with the same exact setup, won't.

Worked in the Beta office @ Alienware for YEARS, have seen 100s of different issues occur in the SAME EXACT BUILDS...They just happen. No 2 cores in this industry are created equal...Regardless of your personal experiences.

Now, am I saying this is an epidemic and everyone's Fermis are going to die? Absolutely not.

Am I saying the conditions are right that it's possible for SOMEONE'S card to die? Yes, absolutely...Because it is.

A significant amount of the Fermi run could not reach stock clocks without being OC'd - Fact.
If you take an already struggling platform and introduce another hurdle/problem it will be MORE likely to fail - Fact.

The Fermi that I ran on my fresh build was a 480 -- Easily hit 90c within 10 minutes just on the Windows 7 screen...Could I have gotten screenshots? Probably but, I really just wanted verification for myself that the issues my clients were complaining about were possible and they are.

Users on [H], Tom's, OCN and Nvidia are complaining about the voltage profiles randomly swapping (Under fresh installs) and the cards randomly hitting max load (Again, fresh installs)...Considering the source, I give those individuals credence and weight.

Just because the weather conditions are right for a Tornado, doesn't mean it's going to happen but, it sometimes, does ~ Nobody ever thought a Tornado would land in Connecticut but, it did.

Again, I'm not saying Fermis are dying left and right, I'm saying you're wrong to believe that it's impossible because under the right conditions, any driver can blow up a card.

Once again, I quite frankly, don't care about 1 individual's conclusions in an enthusiast market of over 1 million users -- If the outspoken majority have an issue with the driver, there's an issue with the driver.

maskedmenace

maniacvvvLOLOLOL

I ran the 320.18 on Fermi cards since its release, both at stock and highly overclocked....
-->saw all of 1c difference (increase) from the previous driver, voltage behavior unchanged.
Thru testing in Heaven 4.0, Valley and Mark11... textbook standard runs, no issues seen
Got a good 30-40hrs of BF3 gameplay in on the driver, no issues seen

I just removed my 580 SLI and replaced it with Keplers
Same testing, same textbook standard runs and no issues seen
Maybe 10hrs of BF3 now, no issues of any kind seen.

No unusual temps, no voltage spikes of anykind noted at all

------------------

Your telling me its happening to you, that you can see this on your own and other systems....
But you cant even provide a simple screenshot?

Yeah right bud.
If you cannot be bothered to post a screenshot, I dont think you are being honest and I certainly dont believe you have the experience levels you claim.
A monkey can build systems.... takes alittle more to be able to take screenshots and post real data

If anyone who DOES have some real tangible proof of this behavior, I am very interested in seeing it.   

Again, YOU stated it was impossible while acknowledging that drivers HAVE destroyed a card before. Period. Done. End.

I quite frankly, don't care about your setup. Just because YOU didn't see any performance issues, doesn't mean the next guy with the same exact setup, won't.

Worked in the Beta office @ Alienware for YEARS, have seen 100s of different issues occur in the SAME EXACT BUILDS...They just happen. No 2 cores in this industry are created equal...Regardless of your personal experiences.

Now, am I saying this is an epidemic and everyone's Fermis are going to die? Absolutely not.

Am I saying the conditions are right that it's possible for SOMEONE'S card to die? Yes, absolutely...Because it is.

A significant amount of the Fermi run could not reach stock clocks without being OC'd - Fact.
If you take an already struggling platform and introduce another hurdle/problem it will be MORE likely to fail - Fact.

The Fermi that I ran on my fresh build was a 480 -- Easily hit 90c within 10 minutes just on the Windows 7 screen...Could I have gotten screenshots? Probably but, I really just wanted verification for myself that the issues my clients were complaining about were possible and they are.

Users on [H], Tom's, OCN and Nvidia are complaining about the voltage profiles randomly swapping (Under fresh installs) and the cards randomly hitting max load (Again, fresh installs)...Considering the source, I give those individuals credence and weight.

Just because the weather conditions are right for a Tornado, doesn't mean it's going to happen but, it sometimes, does ~ Nobody ever thought a Tornado would land in Connecticut but, it did.

Again, I'm not saying Fermis are dying left and right, I'm saying you're wrong to believe that it's impossible because under the right conditions, any driver can blow up a card.

Once again, I quite frankly, don't care about 1 individual's conclusions in an enthusiast market of over 1 million users -- If the outspoken majority have an issue with the driver, there's an issue with the driver.

KEVRAY

A couple of my games froze up on me like the ArmA3 alpha, to be expected i suppose being a wip game, Metro last light on some chapters at certain spots. Oddly, last night whilst playing Hitman Absolution i got a message pop up and tell me my system memory is running low, first time that's happened, maybe i have too many programs open?, i had Precision X plus RTSS and win 7 aero all running in the background and i'm using 8 gb ram, hmmm, strange goings on, this has only started to happen. This is with 320.11 from evga driver disc and 320.18 from GeForce.com, haha. I'm not sure if mine is due to heat problems though?, my GTX 780's get a bit hot really. Think i am regretting GTX780 SLI?.

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.

Lord Odin
Ok, so I'll be getting a 780 soon and am confused.  Do the 320.18 drivers cause issues or not?  Is modifying the 320.14 drivers the only solution?