I've been trying to get my GTX295 to work two tasks at the same time and have tried many config. I'm now running BOINC on WinXP 32-bit with driver version 182.50. SLI is off and PhysX is enabled.

BOINC can now run two CUDA WUs but it's really only one WU get processed by GTX295 and you can see that remaining time is decreasing. The other WU would remain at 0.0% like it's not running at all. Was there anything I missed?

I saw this problem with 6.6.20 and did not figure out what was happening ... so I went back to 6.5.0 ... we were trying to figure this out and I was hoping to get enough up so I could tackle looking at this again ... today was a bust so I will shoot for tomorrow ...

At first we thought it might be some bad tasks from the project. But, NOW, the possibilities of BOINC not handling multiple GPUs correctly may be easier to prove...

Try 6.5.0 to see if that gets the tasks going again ... or to the last version you had installed that worked well ... if it was higher than 6.5.0 then maybe we can point to the place where the bug got introduced.

My "best" suspicion is that BOINC is trying to run the tasks all one core. Can you check your temps before you make a change and see if one or more of your cores is not running?

I had this problem several times up to now - independent of the BOINC version.

Restarting BOINC was the solution.
Do you want to try it?

---

I saw this problem with 6.6.20 and did not figure out what was happening ... so I went back to 6.5.0 ... we were trying to figure this out and I was hoping to get enough up so I could tackle looking at this again ... today was a bust so I will shoot for tomorrow ...

At first we thought it might be some bad tasks from the project. But, NOW, the possibilities of BOINC not handling multiple GPUs correctly may be easier to prove...

Try 6.5.0 to see if that gets the tasks going again ... or to the last version you had installed that worked well ... if it was higher than 6.5.0 then maybe we can point to the place where the bug got introduced.

My "best" suspicion is that BOINC is trying to run the tasks all one core. Can you check your temps before you make a change and see if one or more of your cores is not running?

I'm switching to version 6.4.7 and will see if it works. Couldn't find version 6.5.0 anywhere. If not work, maybe I should try version 6.6.21?

6.5.0

I have been running 6.5.0 for atleast a couple months now, no problems, no reason to change...

to find all the versions go to http://boinc.berkeley.edu/dl

I am running BOINC 6.6.20 on Vista 64 and have two simultaneous WUs processing correctly. I only ever had problems when I first started a few days ago and did not have SLI off and PhysX on. Let me know of any other settings I can give you details on that may help you back to runing the max.

Steve

This may be a subtle and nasty bug. Some of the tasks on my system ran,or appeared to run correctly. Others took up to four times the normal time to run to completion. This may or may not be related to having up to 4 GPU processing elements in the system.

So, what *I* saw was a somewhat random walk of tasks with my normal 4 in work some of them would seem to run right, others incorrectly. Which is why I was looking for a GPU monitoring tool. I was wondering if BOINC is not using the right "pointer" to control the tasks in-flight.

As far as I can gather poor old Rom is using a dual core probably with a low end GPU to do development. What that means is that issues like the one I am describing on the mailing lists (and others) dealing with the CPU scheduler that start to show up on 4 core systems and is quite noticible on 8 CPU systems, well, he can't see them at all ...

Thanks all for the comments, I'm giving BOINC v6.5.0 a try and I'll check out how it works out. Does NVIDIA driver has any roles in this problem? If so, which driver version is I should try to switch to? I'm using latest stable driver v182.50, is it a good version?

Thanks all for the comments, I'm giving BOINC v6.5.0 a try and I'll check out how it works out. Does NVIDIA driver has any roles in this problem? If so, which driver version is I should try to switch to? I'm using latest stable driver v182.50, is it a good version?

On XP Pro 32-Bit that combination is what I have settled in on ... there is another earlier driver that is almost as good (180.22?, I can go look for it if you need it - though this one caused BSOD when I used the nvidia control panel).