I have 3 GPUs.
1 - 1080Ti, 1 - 980 and 1 - Internal GPU on a AMD 7700X
I'm only getting 2 running. The 1080Ti and AMD internal GPU. The 980 is not doing anything. Both work right out of the box.
I can get the 980 to run on 3D Mark so it is posable.
I think BOINC is confuse when have an internal GPU.
I added a command <use_all_gpus>1</use_all_gpus> and still nothing.
BOINC sees all 3 GPUs.

8/29/2023 9:42:19 PM | | Starting BOINC client version 7.22.2 for windows_x86_64
8/29/2023 9:42:19 PM | | log flags: file_xfer, sched_ops, task
8/29/2023 9:42:19 PM | | Libraries: libcurl/8.0.1-DEV Schannel zlib/1.2.13
8/29/2023 9:42:19 PM | | Data directory: E:\ProgramData\BOINC
8/29/2023 9:42:19 PM | | Running under account Sandm
8/29/2023 9:42:20 PM | | CUDA: NVIDIA GPU 0: NVIDIA GeForce GTX 1080 Ti (driver version 537.13, CUDA version 12.2, compute capability 6.1, 11264MB, 11264MB available, 12064 GFLOPS peak)
8/29/2023 9:42:20 PM | | CUDA: NVIDIA GPU 1 (not used): NVIDIA GeForce GTX 980 (driver version 537.13, CUDA version 12.2, compute capability 5.2, 4096MB, 4096MB available, 4979 GFLOPS peak)
8/29/2023 9:42:20 PM | | OpenCL: NVIDIA GPU 0: NVIDIA GeForce GTX 1080 Ti (driver version 537.13, device version OpenCL 3.0 CUDA, 11264MB, 11264MB available, 12064 GFLOPS peak)
8/29/2023 9:42:20 PM | | OpenCL: NVIDIA GPU 1 (ignored by config): NVIDIA GeForce GTX 980 (driver version 537.13, device version OpenCL 3.0 CUDA, 4096MB, 4096MB available, 4979 GFLOPS peak)
8/29/2023 9:42:20 PM | | OpenCL: AMD/ATI GPU 0: AMD Radeon(TM) Graphics (driver version 3570.0 (PAL,LC), device version OpenCL 2.0 AMD-APP (3570.0), 12269MB, 12269MB available, 563 GFLOPS peak)

Just to note, I had both 1080Ti and 980 on a different MoBo with no internal GPU and both ran fine together.
Edit: I just saw that "GPU not used" but why?
Window 11, BOICN 7.22.2[/quote]

---

Software: BOINC v7.24.1 Win 11 Pro, Video Drivers v551.76, CUDA v12.4, V-Box v7.0.6
Hardware: ASRock B650E - AMD Ryzen 7 7700X 8 core - 32GB RAM, EVGA GTX 1080Ti 11GBs, GTX 980 4GBs, 512GB M.2 for BOINC Program and 3TB HD for Data

Well, it says "ignored by config". so that's the place to start looking. Double-check (proof-read) your cc_config.xml file.

• Did you put 'use_all...' in the right section (options)
  
• is there only one instance of that command (keep them in alphabetical order)
  
• Did you restart BOINC after adding that command?
  

and so on.

Well, it says "ignored by config". so that's the place to start looking. Double-check (proof-read) your cc_config.xml file.

• Did you put 'use_all...' in the right section (options)
  
• is there only one instance of that command (keep them in alphabetical order)
  
• Did you restart BOINC after adding that command?
  

and so on.

I just showed you the command I put down.

<use_all_gpus>1</use_all_gpus>

I did put it in alphabetical order.
And I did restart BOINC after.
I already had the command in and it worked before on a different computer.

---

Software: BOINC v7.24.1 Win 11 Pro, Video Drivers v551.76, CUDA v12.4, V-Box v7.0.6
Hardware: ASRock B650E - AMD Ryzen 7 7700X 8 core - 32GB RAM, EVGA GTX 1080Ti 11GBs, GTX 980 4GBs, 512GB M.2 for BOINC Program and 3TB HD for Data

Please post the whole contents of the cc_config.xml file.

<cc_config>
<log_flags>
<file_xfer>1</file_xfer>
<sched_ops>1</sched_ops>
<task>1</task>
<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>
<idle_detection_debug>0</idle_detection_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_gui_rpc_get>0</allow_gui_rpc_get>
<allow_multiple_clients>0</allow_multiple_clients>
<allow_remote_gui_rpc>0</allow_remote_gui_rpc>
<disallow_attach>0</disallow_attach>
<dont_check_file_sizes>0</dont_check_file_sizes>
<dont_contact_ref_site>0</dont_contact_ref_site>
<lower_client_priority>0</lower_client_priority>
<dont_suspend_nci>0</dont_suspend_nci>
<dont_use_vbox>0</dont_use_vbox>
<dont_use_wsl>0</dont_use_wsl>
<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>2</max_file_xfers>
<max_file_xfers_per_project>2</max_file_xfers_per_project>
<max_stderr_file_size>0.000000</max_stderr_file_size>
<max_stdout_file_size>0.000000</max_stdout_file_size>
<max_tasks_reported>0</max_tasks_reported>
<ncpus>-1</ncpus>
<no_alt_platform>0</no_alt_platform>
<no_gpus>0</no_gpus>
<no_info_fetch>0</no_info_fetch>
<no_opencl>0</no_opencl>
<no_priority_change>0</no_priority_change>
<no_rdp_check>0</no_rdp_check>
<os_random_only>0</os_random_only>
<process_priority>-1</process_priority>
<process_priority_special>-1</process_priority_special>
<use_all_gpus>1</use_all_gpus>
<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>
<socks5_remote_dns>0</socks5_remote_dns>
<http_user_name></http_user_name>
<http_user_passwd></http_user_passwd>
<no_proxy></no_proxy>
<no_autodetect>0</no_autodetect>
</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>

---

Software: BOINC v7.24.1 Win 11 Pro, Video Drivers v551.76, CUDA v12.4, V-Box v7.0.6
Hardware: ASRock B650E - AMD Ryzen 7 7700X 8 core - 32GB RAM, EVGA GTX 1080Ti 11GBs, GTX 980 4GBs, 512GB M.2 for BOINC Program and 3TB HD for Data

I've got it.
1. I put the command in wrong location.
2. I didn't see the command that was already there.

1. Why is it not on by default.
2. It should be in the option menu or somewhere to select it.

It's running all 3 GPUS.

---

Software: BOINC v7.24.1 Win 11 Pro, Video Drivers v551.76, CUDA v12.4, V-Box v7.0.6
Hardware: ASRock B650E - AMD Ryzen 7 7700X 8 core - 32GB RAM, EVGA GTX 1080Ti 11GBs, GTX 980 4GBs, 512GB M.2 for BOINC Program and 3TB HD for Data

I'm glad to hear that you've got all three of your GPUs running smoothly now. The issue likely arose due to the placement of the

<use_all_gpus>

command in your cc_config.xml file and its presence in the file.

By default, BOINC doesn't enable all GPUs to ensure compatibility with a wide range of systems. Enabling all GPUs from the start can sometimes lead to stability issues on specific configurations. This cautious approach is intended to prevent potential problems for users who might not be aware of the consequences.

While it's a valid point that many users would prefer GPU configuration options to be accessible through the BOINC Manager's user interface, BOINC also caters to advanced users who like to manually configure settings through the cc_config.xml file.

A helpful tip for future reference: Always check the placement of configuration commands and review your existing settings in the cc_config.xml file if you encounter similar issues.

Lastly, it's worth emphasizing that keeping your GPU drivers up-to-date is crucial for optimal performance and stability. You can usually download the latest GPU drivers from your manufacturer's website or from this page https://softwaretested.com/drivers/.

A helpful tip for future reference: Always check the placement of configuration commands and review your existing settings in the cc_config.xml file if you encounter similar issues.

Another helpful tip is to use Options | Event Log options... to make a minor change to your Event Log settings. [I add 'cpu_sched' and 'sched_op_debug' tags, which print useful information without bloating the number of messages too severely].

When you save the changes, BOINC writes a complete fresh cc_config.xml file, in alphabetical order. It includes any user options already in use, and default values for all other possible choices. You never have to add your own tags after that, just find the existing one in the list.

The mistake in this case was to add the new "use all..." tag in the 'p' section, just above "proxy_info", rather than to carry on reading to 'u', below the proxy section. The formatting of the file at that point is unhelpful, but just plough on through. The effect in this case was that the second (default) value countermanded the earlier (optional) choice.