Posts by Matthew Tireman

\n studio-striking\n
1) Message boards : Number crunching : Gt 730 runtime and points (Message 8629)
Posted 19 Oct 2024 by Matthew Tireman
Post:
never mind it's not solved. ( it was sending cuda tasks, but now its only sending opencl which causes the issue)

so if i switch witch display is the main monitor, it switches which GPU is running both tasks.

I think the issue stems from the fact that the basic gpu app is the same for both cards (dntec521-win32-x86-opencl) but running on cuda uses dntec518-win32-x86-cuda31, so the same application refuses to run on two different gpu's and defaults to the one selected as the main display.

This i cant fix unless there is a way to get only cuda tasks for the 1050ti without disabling opencl for the amd.
2) Message boards : Number crunching : Gt 730 runtime and points (Message 8628)
Posted 19 Oct 2024 by Matthew Tireman
Post:
I was disabling it in windows when boinc was running and i wasn't working on i

Also problem solved.

Issues: windows 11
Solution: windows 10 on a different harddrive

Also i replaced the 730 with a 1050ti since i had one (1050ti did same thing in win 11
3) Message boards : Number crunching : Error trying to add profile (Message 8626)
Posted 17 Oct 2024 by Matthew Tireman
Post:
this, and team creation seems to have some issues with site/ReCaptchA tokens or whatever not being updated and site elements being broken in these areas. It's been like this for 2 years and not been fixed. If you retry a ton of times you might get it to work
4) Message boards : Number crunching : Two tasks, one gpu?? (Message 8625)
Posted 17 Oct 2024 by Matthew Tireman
Post:
so after digging files and building an app_info.xml file, I got the amd GPU to do opencl, but I cant get cuda to work as it deletes the files when boinc starts (prob an issue with app_info.xml)

here it is:

<app_info>
<app>
<name>dnetc</name>
<user_friendly_name>Distributed.net Client</user_friendly_name>
</app>
<file_info>
<name>dnetc_wrapper_1.5_windows_x86_64.exe</name>
<executable/>
</file_info>
<file_info>
<name>dnetc521-win64-amd64.exe</name>
<executable/>
</file_info>
<file_info>
<name>dnetc_wrapper_1.5_windows_intelx86__opencl_ati_101.exe</name>
<executable/>
</file_info>
<file_info>
<name>dnetc518-win32-x86-cuda31.exe</name>
<executable/>
</file_info>
<file_info>
<name>dnetc_wrapper_1.3_windows_intelx86__cuda31.exe</name>
<executable/>
</file_info>
<file_info>
<name>dnetc521-win32-x86-opencl.exe</name>
<executable/>
</file_info>
<file_info>
<name>dnetc-cpu-1.4.ini</name>
</file_info>
<file_info>
<name>dnetc-gpu-1.5.ini</name>
</file_info>
<file_info>
<name>dnetc-gpu-1.3.ini</name>
</file_info>
<file_info>
<name>cudart32_31_9.dll</name>
</file_info>
<file_info>
<name>job-win64-521.1.xml</name>
</file_info>
<file_info>
<name>job-cuda31-1.00.xml</name>
</file_info>
<file_info>
<name>job-win32-opencl-521.1.xml</name>
</file_info>
<app_version>
<app_name>dnetc</app_name>
<version_num>105</version_num>
<file_ref>
<file_name>dnetc_wrapper_1.5_windows_x86_64.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>dnetc521-win64-amd64.exe</file_name>
<copy_file/>
</file_ref>
<file_ref>
<file_name>dnetc-cpu-1.4.ini</file_name>
<open_name>dnetc.ini</open_name>
<copy_file/>
</file_ref>
<file_ref>
<file_name>job-win64-521.1.xml</file_name>
<open_name>job.xml</open_name>
<copy_file/>
</file_ref>
</app_version>
<app_version>
<app_name>dnetc</app_name>
<version_num>105</version_num>
<avg_ncpus>0.01</avg_ncpus>
<max_ncpus>0.01</max_ncpus>
<plan_class>opencl_ati_101</plan_class>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>dnetc_wrapper_1.5_windows_intelx86__opencl_ati_101.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>dnetc521-win32-x86-opencl.exe</file_name>
<copy_file/>
</file_ref>
<file_ref>
<file_name>dnetc-gpu-1.5.ini</file_name>
<open_name>dnetc.ini</open_name>
<copy_file/>
</file_ref>
<file_ref>
<file_name>job-win32-opencl-521.1.xml</file_name>
<open_name>job.xml</open_name>
<copy_file/>
</file_ref>
</app_version>
<app_version>
<app_name>dnetc</app_name>
<version_num>103</version_num>
<avg_ncpus>0.20</avg_ncpus>
<max_ncpus>0.20</max_ncpus>
<plan_class>cuda31</plan_class>
<coproc>
<type>NVIDIA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>dnetc_wrapper_1.5_windows_intelx86__cuda31.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>dnetc518-win32-x86-cuda31.exe</file_name>
<copy_file/>
</file_ref>
<file_ref>
<file_name>dnetc-gpu-1.3.ini</file_name>
<open_name>dnetc.ini</open_name>
<copy_file/>
</file_ref>
<file_ref>
<file_name>job-cuda31-1.00.xml</file_name>
<open_name>job.xml</open_name>
<copy_file/>
</file_ref>
</app_version>
</app_info>

I'm not quite sure what to do wite the cudart dll file yet but it seems to be required in some sort of way.
5) Message boards : Number crunching : Two tasks, one gpu?? (Message 8624)
Posted 16 Oct 2024 by Matthew Tireman
Post:
So In one of my systems, I have a 7800xt as my main, and I decided to throw in an old GT 730 to do some computing since it had nowhere else to be except as a doorstop. Both cards receive open CL tasks but for some reason, both the NVIDIA and AMD tasks run on the 7800xt simultaneously. (I was able to test this by suspending all AMD tasks, and yet the AMD was still pinned at 100% usage running the NVIDIA openCL tasks but the GT 730 was not. The tasks still succeed but the gt730 is being useless and the extra tasks are bogging down the 7800xt. I've reinstalled all drivers. I used Display Driver Uninstaller and installed the latest drivers. I even tried downgrading to Boinc 7.24. I also did the BOINC config file thing to use all GPUs. I have an idea but don't know if it will work or how to execute it:

Force the GT 730 to only get Cuda tasks using appinfo.xml, but I don't know how to get the AMD OpenCL files or Nvidia Cuda files since I only have the ATI14 and Nvidia openCL ones win another thread.
6) Message boards : Number crunching : Gt 730 runtime and points (Message 8623)
Posted 14 Oct 2024 by Matthew Tireman
Post:
Diddnt work
7) Message boards : Number crunching : Gt 730 runtime and points (Message 8622)
Posted 14 Oct 2024 by Matthew Tireman
Post:
I had temporarily disabled the 730 for the night thats why you didn't see it, but ive tried updating drivers already. Im going to do the ccconfig thing now
8) Message boards : Number crunching : Gt 730 runtime and points (Message 8620)
Posted 14 Oct 2024 by Matthew Tireman
Post:
Alright can i just force the gt 730 to run cuda somehow?
9) Message boards : Number crunching : Gt 730 runtime and points (Message 8619)
Posted 14 Oct 2024 by Matthew Tireman
Post:
After suspending all my amd tasks, it appears that my amd and nvida tasks are both simultaneously running on the 7800xt
10) Message boards : Number crunching : Gt 730 runtime and points (Message 8618)
Posted 14 Oct 2024 by Matthew Tireman
Post:
My gt730 in my 1327991 computer is getting full 6144 credit with tasks only running for 200- 500 seconds while my gtx770m in 1328828 gets 1500 credit for 1500-2000 seconds of compute time. Im not a professional at moo but the gt 730 is much slower yet gets credit like my 7800xt????
11) Message boards : Number crunching : Hot spot temp 110°C (Message 8617)
Posted 11 Oct 2024 by Matthew Tireman
Post:
rma replaced the gpu and its all good now. no more overheating
12) Questions and Answers : Android : Error while computing on relatively modern Samsung devices. (Message 8615)
Posted 8 Oct 2024 by Matthew Tireman
Post:
Nvm solved it. after going through other threads for a bit. it seems anything android 10+ may not work with moo wrapper as for right now.
13) Message boards : Number crunching : Hot spot temp 110°C (Message 8614)
Posted 7 Oct 2024 by Matthew Tireman
Post:
After some time, the issue ended up persisting with other applications and ended up being an issue with my GPU, it was still under warranty so I'm getting it RMA'd with Sapphire. I'll test it when it comes back to see if it's resolved. For under-volting, I had to under-volt it way too much to get it to not overheat on the hot spot and it was unstable.
14) Questions and Answers : Android : Error while computing on relatively modern Samsung devices. (Message 8613)
Posted 4 Oct 2024 by Matthew Tireman
Post:
I've had all moo wrapper tasks error out on all 3 of my modern Samsung devices:

Samsung Galaxy S24+
Samsung Galaxy Tab (A8 2020 I think) (named Samsung tablet in my computers)
Samsung Galaxy Watch 5 (no joke)

other projects run fine on all devices except the S24+ but that seems to happen on all new Android devices with BOINC projects, but the A8 and Watch 5 are older and don't work with Moo! so I don't know.

I believe I have my computers public so you can check the Samsung tablet, Arm v8 (Samsung, 2 cores), and Arm v8 (Samsung 8 cores)
15) Questions and Answers : Web site : Profile creation and Recaptcha error (Message 8612)
Posted 3 Oct 2024 by Matthew Tireman
Post:
I'm having the same exact issue when trying to create a team. I have no clue why
16) Message boards : Number crunching : Hot spot temp 110°C (Message 8591)
Posted 17 Apr 2024 by Matthew Tireman
Post:
For some reason, distributed's opencl ati tasks causes my gpu to only reach about 60-67*
°C, but the hotspot reaches 105-110°C, which i believe is causing my sudden system shutdowns. Yet other games, stresstests, and even other projects don't do this, and the hotspot only reaches 80-87°C with core temps 65°C and the system remains powerd on and the gpu util is maxxed out.
17) Message boards : Number crunching : Hot spot temp 110°C(ignore) (Message 8590)
Posted 17 Apr 2024 by Matthew Tireman
Post:
Ignore this it got posted twice for some reason
18) Questions and Answers : Windows : Extreme GPU hotspot temps (Message 8589)
Posted 17 Apr 2024 by Matthew Tireman
Post:
Update, the hotspot reaches 110 and the system crashes. Other project dont do this and max i saw on the hotspot for those was 83*c
19) Questions and Answers : Windows : Extreme GPU hotspot temps (Message 8588)
Posted 17 Apr 2024 by Matthew Tireman
Post:
For some reason, distributed's opencl ati taks causes my gpy to only reach about 60-67*C, but the hotspot reaches 105*C, which i believe is causing my sudden system shutdowns. Yet other games, stresstests, and even other projects don't do this, and the hotspot only reaches 80*C and the system remains powerd on and the gpu util is maxxed out.
20) Message boards : Number crunching : Amd/ATI tasks (Message 8568)
Posted 3 Feb 2024 by Matthew Tireman
Post:
Yea, i had to turn off auto driver update due to the latest driver being broken, should be fixed now


Next 20


 
Copyright © 2011-2025 Moo! Wrapper Project