Posts by samos

InfoMessage
1) Message boards : Questions and problems : Possible compatibility issue between VB 4.3.12 and Windows 10
Message 66571
Posted 1 Jan 2016 by samos
Not all drivers are tested in this way, so it can happen that some (early) drivers cause trouble on people's computers.


the trouble being that in this case, the newer nvidia v361 driver caused the problems, but the older v359 driver is fine!

still running 359.06 just fine, with GPU WU's processing ok... let's hope nVidia fixes their driver...
2) Message boards : Questions and problems : Possible compatibility issue between VB 4.3.12 and Windows 10
Message 66542
Posted 31 Dec 2015 by samos
hmmm, considering i have an nvidia driver of that exact version, maybe it was that instead...



I've downgraded my nVidia driver to 359.06 using a nVidia GEForce 740M, for my Win10 machine.

I guess all I can say is that for my set up, it is likely that the fault was with the nVidia driver version, but not conclusive, since I've just re-installed boinc successfully (but with BOINC 7.6.22 instead of the previous 7.6.9) and running for only a few minutes so far.

If there's any issues, I'll report back... possibly starting an nVidia-specific thread instead to avoid getting off topic here.
3) Message boards : Questions and problems : Possible compatibility issue between VB 4.3.12 and Windows 10
Message 66518
Posted 30 Dec 2015 by samos
Seems like i've found the culprit: it was the latest Nvidia Graphics Driver 361.43


hmmm, considering i have an nvidia driver of that exact version, maybe it was that instead...

what doesn't add up yet, is that on that nvidia driver version but without boinc running nor installed, windows 10 here has been fine for about 4 days????

maybe i'll wait for a few more nvidia driver versions before trying boinc again, and report back...
4) Message boards : Questions and problems : Possible compatibility issue between VB 4.3.12 and Windows 10
Message 66438
Posted 27 Dec 2015 by samos
Heads up all, I've personally had BOINC running with VirtualBox 5.0.10 on my Windows10 machine and it has been causing blue screen of death (BSOD) errors. (KERNEL_SECURITY_CHECK_FAILURE). I've determined at least in my case, the problem was with BOINC itself, and not VirtualBox.

I went through a complete uninstall of ALL of my drivers and BOINC, and re-installed them one by one with a day and a windows 10 restart in-between each one. The final re-install was BOINC 7.6.9 without VirtualBox (fresh re-install downloaded from this site) and it caused a BSOD *DURING* installation....

For now I've removed BOINC from my machine completely, and so far my machine is not crashing again (1 day worth now...)

Heads up as I said... for me these BSOD errors started on 23rd December.. not a fun way to spend the holiday season....
5) Message boards : BOINC client : My Wish List
Message 64640
Posted 3 Oct 2015 by samos
I'd like to be able to set a 'backoff delay' for BOINC compared to system bootup (say delay in minutes from zero to 60 for example) so that BOINC won't load/startup until x-number of minutes from Windows startup.

I find that due to the heavy load-demands of BOINC and/or projects, it does slow system boot up, when it shouldn't need to. I often snooze it during boot up so that my normal boot up completes before allowing BOINC to resume. In my case, it is the disk usage that delays regular Windows startup, and snoozing BOINC during startup relieves it quite a lot.

Otherwise, a setting so that it will only do the 'heavy loading' once the screensaver activates for example?

[Edit: typo]
6) Message boards : BOINC Manager : CPU usage adjustable in two steps - busy / not busy
Message 64066
Posted 5 Sep 2015 by samos
I agree with you.

It would be nice to able to set these to three different percentages.

On Battery: x%
While in Use: y%
While not in use: z%

And while we are at it, the same for GPU:
On Battery: a%
While in Use: b%
While not in use: c%


Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.