nV News Forums

 
 

nV News Forums (http://www.nvnews.net/vbulletin/index.php)
-   NVIDIA Linux (http://www.nvnews.net/vbulletin/forumdisplay.php?f=14)
-   -   How safe is nvidia-settings clock autodetect ? (http://www.nvnews.net/vbulletin/showthread.php?t=141658)

tzp 11-22-09 10:00 AM

How safe is nvidia-settings clock autodetect ?
 
I have a 8500GT and 190.42 on a kernel 2.6.29.1.
The auto-detect clock frequencies in nvidia-settings promoted by card from the default 500,400 to 560,540. This boosted the FPS values in Unigine Sanctuary (from 28 to 35), but when enabled anti-aliasing, the graphics became dodgy after a while, garbage appeared on the screen (in other windows as well) and I saw 100 %CPU load, with kernel load increasing to about 90%.
I saw the garbage on screenalso with glxgears, although not the 100 % CPU load.

So it seems questionable for me how safe is the overclocking recommendation of nvidia-settings.

tzp 11-24-09 07:06 AM

Re: How safe is nvidia-settings clock autodetect ?
 
As nobody reacts, I must make a stronger statement:

The clock recommendation of nvidia-settings is not safe, despite of what is stated in the help.

Can someone from nVidia comment on this ? Aaron ?

jma 11-25-09 02:23 AM

Re: How safe is nvidia-settings clock autodetect ?
 
Quote:

Originally Posted by tzp (Post 2129908)
As nobody reacts, I must make a stronger statement:

The clock recommendation of nvidia-settings is not safe, despite of what is stated in the help.

Can someone from nVidia comment on this ? Aaron ?

TERMS AND CONDITIONS

WARNING: THE SOFTWARE UTILITY YOU ARE ABOUT TO ENABLE MAY CAUSE SYSTEM DAMAGE AND VOID WARRANTIES ...

tzp 11-25-09 02:02 PM

Re: How safe is nvidia-settings clock autodetect ?
 
Quote:

Originally Posted by jma (Post 2130656)
TERMS AND CONDITIONS

WARNING: THE SOFTWARE UTILITY YOU ARE ABOUT TO ENABLE MAY CAUSE SYSTEM DAMAGE AND VOID WARRANTIES ...

I've read that. It's a warning that you should not do overclocking carelessly.
(MAY=may or may not.)

"The Auto Detect button determines the maximum clock setting that is safe on your system at this instant."

That would be the careful way then, one might think.
(Btw, it did not damage my HW (apparently and hopefully) but caused instability.)


All times are GMT -5. The time now is 06:29 AM.

Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.