However it is also my daily machine and I am typing this on it. I watch streaming videos for several hours a day with no noticeable problems. I play games for around 4 hours per day and then Boinc is off.

Are you running with the defaults or have to made use of -use sleep?

Sorry, yes forgot to mention the "-use sleep" is the only command I currently use.

---

I have noticed, that the 64 bit installer shows the warning about boinc running, even if it is not.

Thanks, I'll go down and check that out now.

Edit: well, I've learned something new - but not what I expected.

At my first test attempt, I didn't get the warning at all, whether BOINC was running or not. Then I remembered that I had set that machine up to 'allow_multiple_clients': with that disabled, detection behaved as planned (warned that BOINC was running if it was, didn't warn if it wasn't). And having looked at the code, I can see why it might not work with multiple clients allowed - even if only one is running. The installer makes no attempt to enumerate and stop multiple clients - if you use that (somewhat obscure) facility, take care with the installer.

My test was with a 64-bit copy of Windows 7: could you describe the system you see this false detection on, please?

And please can you use a third-party tool, like Task Manager or Process Explorer, to check that BOINC is really stopped when you think it is? You would normally expect to see three BOINC components listed when it is fully up and running:

boinc.exe
boincmgr.exe
boinctray.exe

It's only the first one of those that we're testing: boincmgr and boinctray can stay running, as far as the installer is concerned. Let us know what you see in both 'running' and 'stopped' states.

My test was with a 64-bit copy of Windows 7: could you describe the system you see this false detection on, please?

I redid it with no boinc(related) processes running---fine, no warning.
With just boinc.exe running---warning---correct..

I have another machine running boinc( older version), which i have not considered.
That appears to be fine.
I can log onto it, if necessary, but the link is bad, and i rarely connect to it.

That's OK - I think we can put it down to a random failure to shut down boinc.exe, without spending too much time on it. But now you've alerted everyone who reads this thread to the possibility, I'm sure other people will have tested as well (and they know what to look out for).

If anyone reproduces the problem (consistently), we can follow it up then.

Thanks for looking into it.
I am 90% certain, that boinc was fully shut down, but there are still these 10%...

With the use of -use_sleep the percentage of CPU usage should continue to drop as the work continues to be processed.

The failure of time left to change, might be an issue with the way the program works. Somewhere I seem to remember comments about the non-linear countdown of work units. I don't know if that is what is happening but might explain it.

As to why the work units continue to crunch after you have exited? I think someone had commented that with BOINCtasks, there was a command that needed to be checked to stop all work when exiting. Failing that, I think I remember something like that happening a while back.

Are you using an up to date version of BOINCtasks? Just trying to figure out what is happening.

As to why the work units continue to crunch after you have exited? I think someone had commented that with BOINCtasks, there was a command that needed to be checked to stop all work when exiting. Failing that, I think I remember something like that happening a while back.

Correct.
There is a menu item to stop the client.
If you just exit "BoincTasks", the client remains running.

As to why the work units continue to crunch after you have exited? I think someone had commented that with BOINCtasks, there was a command that needed to be checked to stop all work when exiting. Failing that, I think I remember something like that happening a while back.

Correct.
There is a menu item to stop the client.
If you just exit "BoincTasks", the client remains running.

Both BOINC Manager and BoincTasks have that behaviour, but in both cases, they either stop boinc.exe (and all tasks should stop with it), or they leave everything running.

Vic wrote:

all 4 of the cpu wu's and 1 of 3 gpu's stop, the other 2 gpu wu's stay in Memory and continue

That shouldn't happen with either Manager. It sounds more like the applications themselves failing to notice that BOINC wasn't there any more - something we had problems with a few years ago.

Zoom,

Just a thought.

Do you run ccleaner after your installs?

Sometimes things get left in the registry after updating and that can cause issues.

Just like what we do with clean install of drivers.

Might be worth a shot.

https://www.piriform.com/ccleaner/download


Zalster

With the use of -use_sleep the percentage of CPU usage should continue to drop as the work continues to be processed.

The failure of time left to change, might be an issue with the way the program works. Somewhere I seem to remember comments about the non-linear countdown of work units. I don't know if that is what is happening but might explain it.

As to why the work units continue to crunch after you have exited? I think someone had commented that with BOINCtasks, there was a command that needed to be checked to stop all work when exiting. Failing that, I think I remember something like that happening a while back.

Are you using an up to date version of BOINCtasks? Just trying to figure out what is happening.

. . I get a pop up window when exiting BOINC client confirming to stop running tasks.

When 0.44 was installed, SoG went away, so did the 16 Sog wu's which were replaced with 18 guppis, the 16 were also guppis.

. . I think you made the same mistake I did, when "rolling back" from 0.45 running SoG I did an uninstall, this is why the downloaded "SoG" WUs went away, if I had done what I should have done and simply re-run the 0.45 install but selecting CUDA50 instead of SoG things would have been fine.

. . Another brilliant "D'oh!" moment.

Set your cache to 1 day and just let it run.

You have changed apps so much BOINC has no idea what the average times should be.

It will run high priority until it sorts it out.

Try Brent's idea first.

If it doesn't correct then I'll resubmit my question

I have the cmdline set for: -use_sleep -instance_per_device 3
I've also had the cmdline set for 2 also, makes no difference.

Changing the -instance per device from 3 to 2, exiting & restarting BOINC, and the manager still shows 0.04C + 0.33NV in the Use column?
If that is the case, it indicates it is using some other settings, from somewhere else.

Do you have a app_config.xml file in the C:\ProgramData\BOINC\projects\setiathome.berkeley.edu
folder?


EDIT- which application are you presently using? These settings are for when running SoG.

---

Grant
Darwin NT

Of the three wu's I'm working on 2 are having trouble(I'm trying 0.45 again with 0.5/0.1 as suggested), the time left does not shrink at all, processing slows to a crawl, when I stop boinc, all 4 of the cpu wu's and 1 of 3 gpu's stop, the other 2 gpu wu's stay in Memory and continue, plus the cpu% keep dropping.

Might be an idea to start again.
Set BOINC not to start at login/bootup.
Exit BOINC.
Re-boot.

Once re-booted, use Task Manager to check that BOINC (and the applications) are no longer running.

Re-run the 0.45 installer- select SoG or CUDA50.

Check how many GPU WUs are being processed, without an app_config.xml it should just be one per GPU.
The GPU WU will most likely be high priority, and when they start the 2 that have the over long completion times will also be High Priority.
Once they are done, everything should then settle back down again and you can re-enable BOINC to start with the system/logon again.


If you want to run multiple WUs on the GPU i'd suggest using app_config.xml to do so as all you have to do is "Select options, Read config files" (on the manager) for the settings to take effect.
And they don't get wiped when you re-run the installer.


1 WU, no CPU cores reserved (the default).

<app_config>
 <app>
  <name>setiathome_v8</name>
  <gpu_versions>
  <gpu_usage>1.00</gpu_usage>
  <cpu_usage>0.04</cpu_usage>
  </gpu_versions>
 </app>
</app_config>

2 WUs, 2 CPU cores reserved.

<app_config>
 <app>
  <name>setiathome_v8</name>
  <gpu_versions>
  <gpu_usage>0.50</gpu_usage>
  <cpu_usage>1.00</cpu_usage>
  </gpu_versions>
 </app>
</app_config>

3 WUs, 3 CPU cores reserved

<app_config>
 <app>
  <name>setiathome_v8</name>
  <gpu_versions>
  <gpu_usage>0.33</gpu_usage>
  <cpu_usage>1.00</cpu_usage>
  </gpu_versions>
 </app>
</app_config>

---

Grant
Darwin NT

I am using the low perfGPU version.Just one task on the GPU.
A number of times it just stops: boinc task appears to be running,elapsed time is increasing, but GPU load zero and no cpu usage either.
When shutting down boinc completely,the gpu process keeps running, well, it is not shut down. I have to kill it manually.
I am still in the process to increase the -period_iterations_num to a point, where every tasks finishes.

As the title says. Beta test only, try at your own risk.

I think we should dig out the old "Advanced Users only" tag for this one - I'm not sure whether it will fly or not.

This installer has been updated for NVidia only so far - DO NOT USE IT if you are currently running stock applications for ATI/AMD or intel GPUs.

This is basically the v0.44 installer (64-bit only, to start with), with the following changes....

Beta2 now available, in both 64-bit and 32-bit versions. Pick the right one, or test out my new dialogs...

Now includes new r3430 ATI and intel_gpu versions, with extra app_version entries to correspond with the new stock applications deployed on 19 May.

ReadMes not yet updated: we polish those up last, to take account of feedback received from testers.

Now updated again with Beta3 (both 64-bit and 32-bit).

Only change is to incorporate r3472 of the SoG application - see release notes in the SETI@home v8.12 Windows GPU applications support thread (and please post comments on the SoG application there, not here).

I have to drive across to the other side of the country tomorrow morning, so I'll leave Beta2 in place until people report successful downloads and installations. Please check carefully that you download the version you wanted to test. (I'm getting error messages myself when I try to download just now)

Download url is: https://onedrive.live.com/redir?resid=8D83BF774A4A86F5!979&authkey=!AK7t-36P9nAec2Y&ithint=folder%2cexe

Now updated again with Beta3 (both 64-bit and 32-bit).

Only change is to incorporate r3472 of the SoG application - see release notes in the SETI@home v8.12 Windows GPU applications support thread (and please post comments on the SoG application there, not here).

I have to drive across to the other side of the country tomorrow morning, so I'll leave Beta2 in place until people report successful downloads and installations. Please check carefully that you download the version you wanted to test. (I'm getting error messages myself when I try to download just now)

Download url is: https://onedrive.live.com/redir?resid=8D83BF774A4A86F5!979&authkey=!AK7t-36P9nAec2Y&ithint=folder%2cexe

. . FWIIW I just downloaded Beta3 AOK, will try from the other machine and test the install on that rig.

Now updated again with Beta3 (both 64-bit and 32-bit).

Only change is to incorporate r3472 of the SoG application - see release notes in the SETI@home v8.12 Windows GPU applications support thread (and please post comments on the SoG application there, not here).

I have to drive across to the other side of the country tomorrow morning, so I'll leave Beta2 in place until people report successful downloads and installations. Please check carefully that you download the version you wanted to test. (I'm getting error messages myself when I try to download just now)

Download url is: https://onedrive.live.com/redir?resid=8D83BF774A4A86F5!979&authkey=!AK7t-36P9nAec2Y&ithint=folder%2cexe

. . OK, I have downloaded AOK on machine 2 and installed with equal success. Now running on all cylinders.

. . OK, I have downloaded AOK on machine 2 and installed with equal success. Now running on all cylinders.

Thanks, Stephen. I've withdrawn Beta2 to avoid confusion.