Questions and Answers :
GPU applications :
Problem with NVIDIA GeForce GTX 960 and (cuda32)Work units
Message board moderation
Author | Message |
---|---|
raydar115 Send message Joined: 6 Oct 02 Posts: 17 Credit: 16,305,128 RAC: 0 |
I just recently installed a video card it is a NVIDIA GeForce GTX 960I read the question and answers for graphics cards it stated that it did not run regular SETI work units or Astropulse.However I have AMD 8 core FX processor and it runs eight SETI work units including the AstropulseWork units and one cuda work unit in my work unit results about 90% of my cuda 32 work units are marked as invalid the other cuda 42,50, and Astropulse cudaWork units don't seem to have any problems I was wondering if anybody had any information or answers for me below is a list of my drivers for my display And my cc_config.xml file Below. Any help figuring this out would be helpful and appreciated. My last question is I was under the impression that I would be running a cuda work unit per core on the video card but it is just running one work unit? Display info Name NVIDIA GeForce GTX 960 PNP Device ID PCI\VEN_10DE&DEV_1401&SUBSYS_29663842&REV_A1\4&204EAC5&0&0010 Adapter Type GeForce GTX 960, NVIDIA compatible Adapter Description NVIDIA GeForce GTX 960 Adapter RAM (2,147,483,648) bytes Installed Drivers nvd3dum.dll,nvwgf2um.dll,nvwgf2um.dll Driver Version 9.18.13.4725 INF File oem29.inf (Section026 section) Color Planes Not Available Color Table Entries 4294967296 Resolution 1024 x 768 x 60 hertz Bits/Pixel 32 Memory Address 0xFD000000-0xFEBFFFFF Memory Address 0xD0000000-0xDFFFFFFF Memory Address 0xCE000000-0xDFFFFFFF I/O Port 0x0000D800-0x0000D87F IRQ Channel IRQ 18 I/O Port 0x000003B0-0x000003BB I/O Port 0x000003C0-0x000003DF Memory Address 0xA0000-0xBFFFF Driver c:\windows\system32\drivers\nvlddmkm.sys (9.18.13.4725, 8.07 MB (8,465,224 bytes), 1/25/2015 6:58 PM) cc_config.xml file info <cc_config> <log_flags> <file_xfer>1</file_xfer> <sched_ops>1</sched_ops> <task>1</task> <android_debug>0</android_debug> <app_msg_receive>0</app_msg_receive> <app_msg_send>0</app_msg_send> <async_file_debug>0</async_file_debug> <benchmark_debug>0</benchmark_debug> <checkpoint_debug>0</checkpoint_debug> <coproc_debug>0</coproc_debug> <cpu_sched>0</cpu_sched> <cpu_sched_debug>0</cpu_sched_debug> <cpu_sched_status>0</cpu_sched_status> <dcf_debug>0</dcf_debug> <disk_usage_debug>0</disk_usage_debug> <file_xfer_debug>0</file_xfer_debug> <gui_rpc_debug>0</gui_rpc_debug> <heartbeat_debug>0</heartbeat_debug> <http_debug>0</http_debug> <http_xfer_debug>0</http_xfer_debug> <mem_usage_debug>0</mem_usage_debug> <network_status_debug>0</network_status_debug> <notice_debug>0</notice_debug> <poll_debug>0</poll_debug> <priority_debug>0</priority_debug> <proxy_debug>0</proxy_debug> <rr_simulation>0</rr_simulation> <rrsim_detail>0</rrsim_detail> <sched_op_debug>0</sched_op_debug> <scrsave_debug>0</scrsave_debug> <slot_debug>0</slot_debug> <state_debug>0</state_debug> <statefile_debug>0</statefile_debug> <suspend_debug>0</suspend_debug> <task_debug>0</task_debug> <time_debug>0</time_debug> <trickle_debug>0</trickle_debug> <unparsed_xml>0</unparsed_xml> <work_fetch_debug>0</work_fetch_debug> </log_flags> <options> <abort_jobs_on_exit>0</abort_jobs_on_exit> <allow_multiple_clients>0</allow_multiple_clients> <allow_remote_gui_rpc>0</allow_remote_gui_rpc> <client_version_check_url>http://boinc.berkeley.edu/download.php?xml=1</client_version_check_url> <client_new_version_text></client_new_version_text> <client_download_url>http://boinc.berkeley.edu/download.php</client_download_url> <disallow_attach>0</disallow_attach> <dont_check_file_sizes>0</dont_check_file_sizes> <dont_contact_ref_site>0</dont_contact_ref_site> <dont_use_vbox>0</dont_use_vbox> <exit_after_finish>0</exit_after_finish> <exit_before_start>0</exit_before_start> <exit_when_idle>0</exit_when_idle> <fetch_minimal_work>0</fetch_minimal_work> <fetch_on_update>0</fetch_on_update> <force_auth>default</force_auth> <http_1_0>0</http_1_0> <http_transfer_timeout>300</http_transfer_timeout> <http_transfer_timeout_bps>10</http_transfer_timeout_bps> <max_event_log_lines>2000</max_event_log_lines> <max_file_xfers>8</max_file_xfers> <max_file_xfers_per_project>2</max_file_xfers_per_project> <max_stderr_file_size>0</max_stderr_file_size> <max_stdout_file_size>0</max_stdout_file_size> <max_tasks_reported>0</max_tasks_reported> <ncpus>-1</ncpus> <network_test_url>http://www.google.com/</network_test_url> <no_alt_platform>0</no_alt_platform> <no_gpus>0</no_gpus> <no_info_fetch>0</no_info_fetch> <no_priority_change>0</no_priority_change> <os_random_only>0</os_random_only> <proxy_info> <socks_server_name></socks_server_name> <socks_server_port>80</socks_server_port> <http_server_name></http_server_name> <http_server_port>80</http_server_port> <socks5_user_name></socks5_user_name> <socks5_user_passwd></socks5_user_passwd> <http_user_name></http_user_name> <http_user_passwd></http_user_passwd> <no_proxy></no_proxy> </proxy_info> <rec_half_life_days>10.000000</rec_half_life_days> <report_results_immediately>0</report_results_immediately> <run_apps_manually>0</run_apps_manually> <save_stats_days>30</save_stats_days> <skip_cpu_benchmarks>0</skip_cpu_benchmarks> <simple_gui_only>0</simple_gui_only> <start_delay>0.000000</start_delay> <stderr_head>0</stderr_head> <suppress_net_info>0</suppress_net_info> <unsigned_apps_ok>0</unsigned_apps_ok> <use_all_gpus>0</use_all_gpus> <use_certs>0</use_certs> <use_certs_only>0</use_certs_only> <vbox_window>0</vbox_window> </options> </cc_config> |
rob smith Send message Joined: 7 Mar 03 Posts: 22199 Credit: 416,307,556 RAC: 380 |
OK, you've got a similar set up to one of my crunchers, so: I've found that the FX8xxx series of processors support GPUs far better when you limit the number of CPU cores to at least one less than the number that are there, so reduce the % of CPU to say 75%, this will have the effect of freeing up two cores, which will be more than made up for by the increase in performance of your GTX960. I too had problems when running the very low CUDA versions, the 9xx family of processors don't appear to support very CUDA versions as well as they might. To fully overcome this you need to run optimised apps, such as those from Lunatics, and only select the CUDA5(0) version for installation. Another thing, learnt by bitter expirience is turn OFF driver updates in your Windows Update options - the MS drivers really are not up to the mark, so ONLY use the drivers you get from Nvidia, and wait a few weeks after they launch a new one as there have been one or two "duff" releases. Someone else can talk you through a much simpler way of managing your system, I' away from my crunchers just now otherwise I would post the setting I use. Bob Smith Member of Seti PIPPS (Pluto is a Planet Protest Society) Somewhere in the (un)known Universe? |
Zalster Send message Joined: 27 May 99 Posts: 5517 Credit: 528,817,460 RAC: 242 |
Jason answered this question in regards to gvtc 970s with new Nividia drivers. They seem to think the newer drivers break cuda 32. They are stating to use cuda 50 only. Install lunatics and go for the cuda 5.x option. |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.