• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

Latest Nvidia drivers kill overclocking

I see, its probably just a bug then, as i can't really see them blocking overclocking.

Is overclocking a cause of increased RMA's?
If so it's going to get quite expensive swapping out those GT200's for GT300's particularly for board partners that must already be struggling under financial strain.
 
Way too many little bugs like this have slipped in of late - even in WHQL builds :S

How on earth you release a driver without working OCing with any sort of quality control I don't know.
 
Is overclocking a cause of increased RMA's?
If so it's going to get quite expensive swapping out those GT200's for GT300's particularly for board partners that must already be struggling under financial strain.

Blocking overclocking wouldn't help - tho nVidia might deludedly think so - but if any remenant of sense remains they'd realise locking it out would drive enthusiasts away from their cards in droves and hence produce a trend away from their cards in general.
 
I have just installed these:

191.07 for windows 7 64bit with my GTX 260 SLI setup

They seem pretty good so far. I can now run the Resident Evil 5 benchmark DX10 without dropping to 3fps!
 
The sad thing is that we`ll probably have to wait till they release the next new WHQL certified drivers in another some months before this overclocking bug of whatever it is gets fixed.

If you ask me, they should have pulled this driver from there website.
 
Last edited:
I've been using Nvidia exclusively since 1997 when I purchased a 4MB Riva AGP card, however i'm getting cheesed off with driver support and may try ATI next time.
 
they haven't blocked anything go and read the original article...found here

original article

its just the usual semiaccurate (ie Charlie's website) sensationalist headlines

so as i said earlier the overclocking functions haven't been removed, else msi's afterburner app wouldn't work.
 
Last edited:
Ive been using 186.18 on Windows 7 64 with my GTX280, ive started getting 0x116 BSOD with nvlddmkm.sys, Im going to try the 191.07's and see if that helps.
 
Ive been using 186.18 on Windows 7 64 with my GTX280, ive started getting 0x116 BSOD with nvlddmkm.sys, Im going to try the 191.07's and see if that helps.

If its suddenly started happening it could be RAM dying, or GPU failing - quite common to see that happening when solder joints start failing on 200 series cards :( Asus chipsets - especially if they are getting too hot - are known to cause it as well but generally they do it from the start not just suddenly start.
 
Looks like EVGA precision has rushed out another update to allow OCing with these drivers... but imo the drivers are a write off.
 
If its suddenly started happening it could be RAM dying, or GPU failing - quite common to see that happening when solder joints start failing on 200 series cards :( Asus chipsets - especially if they are getting too hot - are known to cause it as well but generally they do it from the start not just suddenly start.



Well to be fair I did try out one of the more recent drivers, one of the early 189.xx or 190.xx then rolledback the drivers. TBH I think I will reinstall Windows at some point. GTX280 sounds like a jet engine when it crashes normally as well.
 
Actually on that note - a bit of warning... I had awful problems going from these 196.21 back to 191.07. Trying to install over the top would constantly hard lock the machine! and on reboot strange things happened because it had half one lot of drivers and half the other :S thank goodness for system restore/rollback.
 
Rroff : Thats quite possibly what has happened with mine, except whatever game im in freezes then the screen goes black for ~ 20 seconds then the blue screen comes up with the nv....sys file error. :\
 
they haven't blocked anything go and read the original article...found here

original article

its just the usual semiaccurate (ie Charlie's website) sensationalist headlines

so as i said earlier the overclocking functions haven't been removed, else msi's afterburner app wouldn't work.

NO, Lars is new and so far proven to be a complete twit, I wouldn't be remotely surprised to see him gone, very very soon. His writing is simply poor, his rumour type write ups(read the Apple one) literally don't have a single shred of info, its forum rumours, and yes theres a difference between writing an article based on forum rumours, and one from industry sources that starts forum rumours :p

I've so far seen from his first article to the latest, nothing but twaddle and a poor understanding of the situation he's commenting on.


Bru, its not Semiaccurate scaremongering, its talking about SOMEONE ELSES article and their conclusions. But having read it its Lars typical absolutely useless ability to draw conclusions from what others have writen. He's just thick as **** in all honesty.

THe original article is showing significant clocking problems, core/memory are the "non important" to a degree overclocking features, most Nvidia cards all the power is locked up in shader clocks, removing it is pretty big. But the article doesn't say it fantastically clearly, but seems to be hinting that these are set for Fermi OVERCLOCKING, and that it will just do it significantly differently on Fermi which is working against CURRENT overclocking functions.

Its not suggesting no overclocking but that its changed it to be compatible with Fermi, because if you're read on Fermi, a LOT of features that used to be on core clocks, are now on dividers under shader clocks, I would imagine that needs to be taken into account for overclocking.

Lars has misinterpreted it(and as I said its not fantastically clear in the original article) that they meant they've changed it so you won't be able to overclock Fermi so they've tried to inhibit shader overclocking. Which more than ever Fermi will be based, in terms of performance, almost completely on shader clocks as very little is left to be governed by core clocks.

Either way you've got, its not an original article, but commenting on someone elses, not brilliant english and a complete tool who misreads almost every situation it would seem.


In terms of Fermi, overclocking will be interesting, according to the white papers its a very low voltage design, but in doing so became an incredibly high amperage design. So now overclocking is supposed to be a huge extra power draw in amperage, I wouldn't be surprised to see some pretty significant "safety" limits in terms of overclocking to keep power usage in check.
 
Ive been using 186.18 for ages.

So far these have been the best drivers for my GTX285, dont know how nvidia are bringing out worse drivers :confused:

great driver for fallout 3 that is,one of my favourites in my driver folder,another brilliant driver with good vibrance and ultra smooth fps is the 187.66(XG)
 

your quite right :o ...... it isn't semiaccurates article,or even their scaremongering headline and i agree the original page isn't particularly good. but with them having a couple of apps that don't work fully one that does and one that didn't at all, to me it would seem that the overclocking abilities are still there nvidia have just changed the way they are accessed slight or something.

as for Fermi yes your quite right its all going to be tied in with the shader clock and divisions of it according to the anandtech article, so what this will mean for overclocking gf100 based boards who knows.
i also wouldn't be surprised to see some safety limits on whats doable with the Fermi overclocking, especially if they really do end up running as hot as the romour mill has them running at.
 
Last edited:
Just for peoples information, I installed these straight over the top of the 195.62s on win 7 64, all went fine until it didn't ask for a restart which I thought was a little bit odd.

Went to play dirt 2 and got some woefull fps (40-45 fps ish) with everything maxed out @ 1920x1200, I thought that's a bit strange considering these drivers were supposed to enable SLi in Dirt 2??

Anyway to cut a long story short, I ended up having to uninstall correctly via control panel, then boot in safe mode, run driver sweeper, reboot and then install the new driver.

End result a constant 60fps with vsync, as opposed to the 45ish I was getting after installing straight over the top of the older drivers.

I know a lot of people are suggesting install these new drivers straight over the top of your existing ones, but just be wary and check you're getting the best performance from them.
 
191.07 for windows 7 64bit with my GTX 260 SLI setup
195.62 for Windows 7 64bit for my GTX 260m laptop
195.62 for Windows XP 32bit single GTX 260

I've not tried the things that cause problems on the SLI setup on my laptop but everything else works fine with newer drivers.

With anything newer than 191.07 on my SLI setup several games/applications like the heaven benchmark, serious sam HD and some source games stall on a black screen for 10 seconds every 30-40 seconds or so when in 3D.

Can I borrow one of your GTX 260s?! :D

Damn, should've read this before updating my drivers. We'll see how games handle.
 
"Expreview is drawing some wild conclusion that its related to Nvidia’s impeding launch of Fermi based cards and as such they want to prevent the cards from being overclocked. This seems like a little bit of a long shot, especially as the drivers are WHQL certified for use with the current crop of cards. Hopefully Nvidia will sort out this issue as we can imagine that quite a few people will be miffed about it, least not the competitive overlocking crowd."

http://www.semiaccurate.com/2010/01/21/latest-nvidia-drivers-kill-overclocking/


If nvidia wanted people not to overclock Fermi then they would have done precisely that. Blocking all overclocking doesn't make any sense.
 
Back
Top Bottom