thanks

So far The Studio Driver Version 441.12 is doing well and seeing better performance over the The Studio Driver Version 431.86.
https://moowrap.net/hosts_user.php?sort=expavg_credit&rev=0&show_all=0&userid=115955

Seeing this now on my Other RTX Rig so I am going back to Driver 431.86
I might even go back to Driver 430.86 on the RTX Rigs.
Normal runtime watts show 310 under Driver 441.12 and under Driver 431.86 shows 380 Watts.
I will let SETI run over night and see how it goes, I hope this is not another BOINC Project that still have issues with the RTX Graphics Card.

ProDigit
I was about to ask how the new drivers are doing.
On Boinc, I've also seen the 1350Mhz lock on the newer 440.31 Linux drivers.
The 1350 Mhz lock seems to have something to do with overclocking.
While older drivers would tune down the overclocking the higher you went (overclock +30Mhz would do +30Mhz, overclock +100Mhz would actually end up doing ~+75Mhz), these drivers, as soon as an error happens, go into limp mode.
To undo, you'd have to lower the OC, and pause the GPU load. Then restart the load with a lower OC.
It's a good way to see if you overclocked too high for FAH but for Boinc it's actually quite annoying, as Boinc doesn't tax the GPU 100%. It has a lot of dips, where the load decreases, and thus the GPU speed increases.
I've seen peaks of on my lower end RTX cards of up to 2070Mhz, when the load dropped. No wonder they freeze.
This new way of overclocking means, I can no longer overclock precisely, and the drivers are more wonky.
All it takes is a small dip in the load, or spike in the GPU frequency, and limp mode is on.

I spent my entire day today looking at the numbers, and I'm definitely not fond of this newer driver issue!
It means I'll have to reconfigure all my overclocking settings (right when I just had them perfect).

Are you running SETI?
BTW, My testing is Without Overclocking the GPU or GPU Memory.
Lowering the OC made No Difference when running SETI or Lowering the Voltage on the GPU.
With this same Driver I did not see this issue with the Graphics Card locking @ 1350MHz on any other BOINC GPU Projects nor Folding.
I test new Drivers the first time with the Default Settings on the Graphics Cards.

I've seen this under Folding and Boinc.
I'm not running seti, but a few other projects that run GPUs.

Linux driver 440.31
RTX 2080/2080Ti/2070/2060.
I've only had this happen to 2 of my cards, one being the 2080Ti. 
 
I will revert to older drivers as well.

So far Driver 431.86 is doing well on my 10 Series Cards and on the my RTX Cards.
39x is also a good driver and is my backup driver now.
 
I might give 441.28 2019.11.18 https://www.nvidia.com/Download/driverResults.aspx/154342/en-us a test run after it cools back down
At lest I will test this Driver on SETI to see if it at least works. Windows 10 Only that is.
 
NVIDIA Studio Drivers provide artists, creators and 3D developers the best performance and reliability when working with creative applications. To achieve the highest level of reliability, Studio Drivers undergo extensive testing against multi-app creator workflows and multiple revisions of the top creative applications from Adobe to Autodesk and beyond.

Applications

Provides optimal support for the upcoming releases of top renderers including Chaos Group’s V-Ray GPU Next and Blender 2.81 which support RTX-accelerated ray tracing.

• NVIDIA Studio Driver Release Notes (v441.28)
• Control Panel User's Guide

NVIDIA TITAN Series:
NVIDIA TITAN RTX, NVIDIA TITAN V, NVIDIA TITAN Xp, NVIDIA TITAN X (Pascal)
GeForce RTX 20 Series:
GeForce RTX 2080 Ti, GeForce RTX 2080 SUPER, GeForce RTX 2080, GeForce RTX 2070 SUPER, GeForce RTX 2070, GeForce RTX 2060 SUPER, GeForce RTX 2060
GeForce 16 Series:
GeForce GTX 1660 SUPER, GeForce GTX 1660 Ti, GeForce GTX 1660, GeForce GTX 1650
GeForce 10 Series:
GeForce GTX 1080 Ti, GeForce GTX 1080, GeForce GTX 1070 Ti, GeForce GTX 1070, GeForce GTX 1060, GeForce GTX 1050 Ti, GeForce GTX 1050

Cool GTX
thanks bcav

I added BOINC to the Title, this way my Thread should be ok and not locked.

Vlada011
Someone use studio driver for gaming? No?

No as per most Forum Members and MODS but I see no reason not to other than NVIDIA Recommends using the Other Driver per a Thread on their Forum. 
Here  is the Thread for Gamers Nvidia 441.28 Studio Drivers released 11-18-2019 if you want to ask them.
I have this Thread under BOINC or Crunching@EVGA because that is what I am using it for and testing with.
 

I currently have no issues under 430.64 for linux.
Odd note: 430.64 drivers were released 1 day after driver 440.31.
An earlier driver released after a newer driver..

Solo for the moment being, unless there are substantial benefits to join a team.
I haven't given SETI a try, but I haven't ran into the Mhz lockup recently (I'll call it limp-mode).
I've also only ran Folding at home for the moment, since the temperatures allow me to run the server at it's fullest potential right now (temperatures below 50C)
 
On Boinc, I'm currently testing out 2x GT 1030s, and will be doing further testing on RTX hardware later on.
I'll keep you posted.

bcavnaugh
This issues was tested only under Windows 10 1903 and only SETI seems to cause this odd 1350 MHz Lockup with Newer Drivers only on RTX Graphics Cards.

The 1350Mhz lockup was also present under Linux, running FAH, on overclocked GPUs. Since I've lowered the overclocking, I haven't bumped into any issues anymore.

ProDigit

bcavnaugh
This issues was tested only under Windows 10 1903 and only SETI seems to cause this odd 1350 MHz Lockup with Newer Drivers only on RTX Graphics Cards.

The 1350Mhz lockup was also present under Linux, running FAH, on overclocked GPUs. Since I've lowered the overclocking, I haven't bumped into any issues anymore.

To note this was happing only with the NVIDIA Studio Drivers and with the Default Settings for the Graphics Card with No Overclocking on them as well as down clocking them to the lowest settings under PX1.
Also this happened only on the BOINC Project SETI and not on any other BOINC Project to include Folding.
Linux is in its on league and I am glad you got your issue fixed by down clocking or lowering your overclocking on your Graphics Cards and using different drivers.
I only test BOINC and NVIDIA Drivers under Windows 10.
I only run BOINC Client on my Linux Hosts and I do not have the Folding Client installed on them so I do not test Folding on them.
You might find some better Linux answers and help with Folding issues under this Thread F@H On Linux under Folding@EVGA
We keep them separate to reduce the difference between Folding and Crunching issues that come up as well as Windows and Linux issues.
Not all BOINC Projects run under Windows and Linux as Linux have some CPU Applications that will not run under Windows.
BOINC also has CPU VM Applications that use Oracle VM VirtualBox and I only run them under Windows and not under Linux.
But you can install it on most Linux OS
https://www.virtualbox.org/wiki/Linux_Downloads
Please choose the appropriate package for your Linux distribution.
VirtualBox 6.0.14 for Linux

•  Ubuntu 18.04 / 18.10 / 19.04
•  Ubuntu 16.04
•  Ubuntu 14.04 / 14.10 / 15.04
•  Debian 10
•  Debian 9
•  Debian 8
•  openSUSE 15.0
•  openSUSE 13.2 / Leap 42
•  Fedora 29 / 30
•  Fedora 26 / 27 / 28
•  Oracle Linux 8 / Red Hat Enterprise Linux 8 / CentOS 8
•  Oracle Linux 7 / Red Hat Enterprise Linux 7 / CentOS 7
•  Oracle Linux 6 / Red Hat Enterprise Linux 6 / CentOS 6
•  All distributions (built on EL6 and therefore not requiring recent system libraries)

 

ProDigit
Perhaps the following information may be of use:
I did notice that some projects don't fully utilize the GPU.
When looking at the wattage, I noticed that the 1350Mhz lockup mostly happened (or it could be coincidence), on those projects.
When the GPU power threshold surpasses 50%, and the card isn't under full load, scenarios happen where the GPU is cool enough to run at full boost speeds for prolonged times.
 
THere may be a possibility this is linked to the GPU frequency lockup issues.

Most BOINC GPU Applications run between 40% - 90% it all depends on which Project you are running.
No BOINC GPU Application is the same and why some of us run 2 or 3 tasks per GPU so there is a need to know what Project you are speaking of.
Also why we use app_config.xml for some of Projects. There are some that run @ 1350 MHz and show little wattage or % usage and is normal.
Some also BOINC GPU Application use more CPU resources then others.
 
This is a good example of why you should Join a Team, they will help you get started.
 

ProDigit

bcavnaugh
Seeing Issues Running SETI under an RTX Graphics Card.
Seems kill the GPU @ 1350 MHz This is NOT the so called 1350 MHz BUG that others have posted this is Driver Based Issue and Not the Graphics Card.

I've noted another possibility of the 1350Mhz bug,
Check your GPU load.
If it's below 50% on a project, your GPU will run at 'half speed' (or near to half speed).

I've found this to be true on Einstein@home projects.
I've written my config settings to load up to 3 Einstein tasks per GPU, and get a 112-140Watts (of 170Watts) load most of the time.
Though sometimes it does dip back to the 40-65Watts, so I'm not sure how effective it really is.
..Edit: it still shows only 1 GPU project on the Nvidia GPU active; I guess the config settings they mention in their manual, don't really work.
Adding multiple projects per GPU, allows the GPU to run at it's full boost speed if the load is above 50% (85Watts in my case).
..Or, it's all coincidence, and Boinc is finally getting bigger GPU projects....
 
Just thought it's yet another possible reason for the 1350 GPU lock (this lock also doesn't allow you to use overclocking settings to increase the boost clock speed).

I am Good, thank you
After making a Change in the app_config.xml File you must re-read it and exit the BOINC Client Software and sometimes restart the Host to make the change to Tasks that have already been downloaded. This Settings is not really needed "<max_concurrent>3</max_concurrent>"
The Setting "<name>Einstein@Home</name>" will not work and you should see the correct name in your BOINC Log.
A simple app_config.xml File setting for Einstein. https://forums.evga.com/FindPost/2693812
 
<app_config>
<app>
<name>hsgamma_FGRPB1G</name>
<gpu_versions>
<gpu_usage>1.0</gpu_usage>
<cpu_usage>0.2</cpu_usage>
</gpu_versions>
</app>
<app>
<name>hsgamma_BRP4G</name>
<gpu_versions>
<gpu_usage>1.0</gpu_usage>
<cpu_usage>0.2</cpu_usage>
</gpu_versions>
</app>
</app_config>
 
<gpu_usage>1.0</gpu_usage> = 1 Task Per GPU
<gpu_usage>0.5</gpu_usage> = 2 Tasks Per GPU
<gpu_usage>0.3</gpu_usage> = 3 Task Per GPU *on some Projects.
 
As far as the cc_config.xml file the below is all you really need if even used.
<cc_config>
 <options>
 <report_results_immediately>1</report_results_immediately>
 </options>
</cc_config>
 
Some GPU Project will also not really use this "<cpu_usage>0.2</cpu_usage>" and will still use the Thread or Core one per task.
 
The Clock is not the issue the Tasks Stop Running is the issue other BOINC Projects run fine when the Clock Locks at 1350HMz.
Not many Team Members have Forum Account over on https://boinc.berkeley.edu/forum_index.php
Team Crunching@EVGA uses the EVGA Forum for 99% of the time for information on BOINC and the Project Settings and so on.
 
But this is now taking this Thread Off Topic and you should create your own Thread about Einstein and or the app_config.xml File settings.