Nvidia 197.13 WHQL Released !

Just saw them posted. Hopefully they fixed of the 'Nvidia driver stopped responding' messages.

http://www.nvidia.com/Download/index5.aspx?lang=en-us

 

Those issues has been there for years.. I dont see why it would be completely gone in this release.. Its different who experience it, i once had to format to make the nvidia driver stop responding.

 

yes if you are getting that error then you are royally screwed to be honest. are these drivers available for mobile official release. If not then i am not dl'ing it.

 

Can we get a new mobile driver please? It's been far too long.

 

Why all the excitement about WHQL Desktop Drivers?

Sure, you can use a modified .inf but that's not the point right.

 

Those issues are related to overclocking .. it's the same on ATI cards and will never go away with driver updates.

 

Not nessesarily..

 

From my past experiences , it is. What could be the other cause for it ? Overheating is certain not one of them as the card was crashing down @ 60 with higher clocks .. lowering the clocks stopped it from crashing

 

The issue with 196.75 has to do with an issue regarding fan control. People were reporting GPU fans completely stopping after a game was started. It has nothing to do with overclocking.

edit: when you overclock a GPU and it crashes it means it is unstable at that clock speed (core, mem, shader, etc.), it doesn't mean faulty driver, because you always need to test stability at new speeds before firing up a full fledged game. You can crash a GPU using any driver if you overclock it too much. Some people go ahead and do volt mods to pump more voltage into the GPU to push it into faster speeds, which is very similar to CPU overclocking and whatnot.

 

I wasn't talking about that particular driver , but a driver issue in general when OCing which some been having and others not.

 

Ahh, heh, I thought I may have mis-understood the topic.

But yeah, I'm not sure if particular drivers are more OC friendly, although IMO and in my experiences it's more GPU-bottlenecked. My GTX 260s, for example, stable at 650mhz core, 1450mhz memory, 1150mhz shader, but if I try for 1500mhz memory then it will start to show artifacts in-game and if i have it at 1550mhz then it will 'crash' to desktop with the display driver has stopped responding. This has happened with multiple versions of nvidia drivers that i've had and so the ceiling for my particular GPUs seemed to be 1450mhz.

Also I think we need to always keep in mind the rule of YMMV (you mileage may vary) in the world of overclocking. Just like CPUs, each unit may have some variations in overclocking potential. People do quite a bit of research into different batches of CPUs (ie, i7 920 C0 vs i7 920 D0) and certain ones are known as "golden batches" where quite a few overclock very well on low voltages. For example my i7 930 that I grabbed (basically a new i7 920 batch with stock clock upped by 200mhz) is stable 24/7 at 4.2Ghz and 1.30 volts, whereas my previous core i7 920 (a C0 revision) only managed 3.8ghz 24/7 stable at 1.30volts.

 

What can happen is that you're running the clocks faster than the actual processing can happen at whatever voltage it's running at, so even though it's not heating up it's getting bad data going through the card and then crashing. Heat is not the only limitation on overclocking.

 

For the record the error message I was getting was not because of over clocking as the videocard wasn't overclocked. I was getting that message randomly on both a desktop and laptop when using the 196.21 drivers.

Like I said i'm hoping they addressed that but we'll see.

 

Yeah I know , the reason I came up with all that is because the OP is hoping they would fixed the driver crashing issue (whichever one he was referring to).. it was just a heads up kind of way

EDIT : There you go , things are clearer now