A disk died in one of my machines, (quad core), so I installed a new one, (SSD), and loaded the machine with Windows 8, (most of my machines run XP). Twice now, when returning to the machine in the morning, the manager task is frozen, nothing changing at all. Task manager shows four science apps running fine. I kill and restart the manager everything looks normal again. The portfolio on that machine is SIMAP, Einstein, Rosetta and POGS, but I doubt that is relevant. Machine runs 24/7.

Obviously, this is not a serious problem, but it might bother some.

First off, the numbering. This is correct. In theory, you will be able to insert 64 Nvidia GPUs, 64 AMD GPUs and 64 Intel GPUs into your computer and have them all have a reasonably unique number. Where you may see just GPU 0, GPU 1, GPU 2 etc. you're not seeing what it says in front of that:
CUDA: NVIDIA GPU 0
OpenCL: NVIDIA GPU 0
OpenCL: AMD/ATI GPU 0
This is also easy when you use the various exclusion/ignore flags in cc_config.xml
<ignore_intel_dev/>, <ignore_nvidia_dev/> and <ignore_ati_dev/> will use that number.
<exclude_gpu/> will require that you point out the brand of GPU and which number.

Now then, Nvidia OpenCL work running on the AMD GPU. It's difficult to see this from just the screen grabs you made as it doesn't show what is happening in the client. It can just as well be that one AMD OpenCL task runs on the built-in GPU and that the Nvidia OpenCL task has defaulted back to the CPU. The image of GPU-Z doesn't show that.

But BOINC has an easy thing for that, it can show which task runs on what hardware, using the <cpu_sched_debug> and <coproc_debug> flags in cc_config.xml
If you update that host to 7.3.15, you can use the built-in diagnostics window to easily set this flag. Best is also --aside from the default <task>, <sched_ops> and <file_xfer> flags-- to only set this <cpu_sched_debug> and the <coproc_debug> flag, so that when you post the output, we can still read it without too much trouble.

The output will be something alike this:

18/04/2014 11:12:16 |  | [cpu_sched_debug] Request CPU reschedule: periodic CPU scheduling
18/04/2014 11:12:16 |  | [cpu_sched_debug] schedule_cpus(): start
18/04/2014 11:12:16 | SETI@home | [cpu_sched_debug] scheduling 06ap09ad.23882.179910.438086664207.12.124_1 (coprocessor job, FIFO) (prio -1.000000)
18/04/2014 11:12:16 | SETI@home | [cpu_sched_debug] reserving 1.000000 of coproc ATI
18/04/2014 11:12:16 |  | [cpu_sched_debug] enforce_run_list(): start
18/04/2014 11:12:16 |  | [cpu_sched_debug] preliminary job list:
18/04/2014 11:12:16 | SETI@home | [cpu_sched_debug] 0: 06ap09ad.23882.179910.438086664207.12.124_1 (MD: no; UTS: yes)
18/04/2014 11:12:16 |  | [cpu_sched_debug] final job list:
18/04/2014 11:12:16 | SETI@home | [cpu_sched_debug] 0: 06ap09ad.23882.179910.438086664207.12.124_1 (MD: no; UTS: yes)
18/04/2014 11:12:16 | SETI@home | [coproc] ATI instance 0; 1.000000 pending for 06ap09ad.23882.179910.438086664207.12.124_1
18/04/2014 11:12:16 | SETI@home | [coproc] ATI instance 0: confirming 1.000000 instance for 06ap09ad.23882.179910.438086664207.12.124_1
18/04/2014 11:12:16 | SETI@home | [cpu_sched_debug] scheduling 06ap09ad.23882.179910.438086664207.12.124_1
18/04/2014 11:12:16 |  | [cpu_sched_debug] using 0.04 out of 2 CPUs
18/04/2014 11:12:16 | SETI@home | [cpu_sched_debug] 06ap09ad.23882.179910.438086664207.12.124_1 sched state 2 next 2 task state 1
18/04/2014 11:12:16 |  | [cpu_sched_debug] enforce_run_list: end

And do that every minute.

Hi Alexander,

I think I found the problem in the GPU detection code and fixed it. The odd thing is this bug has been present since April 15 (BOINC 7.0.63) and I am not aware of anyone else reporting it! This bug affects only systems with two or more different AMD GPUs with both CAL and OpenCL.

I see on the Albert@home thread that you said you are running on a 64-bit Windows 7 system. Is that the one you can test on? I'll see if I can get Rom to make you a test build so we can find out if my change does indeed solve the incorrect GPU listings you are seeing.

Cheers,
--Charlie

I see on the Albert@home thread that you said you are running on a 64-bit Windows 7 system. Is that the one you can test on? I'll see if I can get Rom to make you a test build so we can find out if my change does indeed solve the incorrect GPU listings you are seeing.

Cheers,
--Charlie

I have installed the graphic (open CL) drivers from here:
[snip]
The only strange thing now is, that all gpu's are GPU 0 now.
HTH

I am the BOINC developer who implemented the OpenCL code and I'm trying to understand the problem that caused your Tahiti GPU 0 to be shown a second time under OpenCL GPUs and your Cypress/Hemlock GPU 1 not to be shown under OpenCL GPUs. Please answer the following questions:

[1] What do you mean by Select graphic first?
[2] Which version of BOINC are you running?

You also posted at <http://albert.phys.uwm.edu/forum_thread.php?id=8954&nowrap=true#112649> that

I've tried it right now.

and

The OpenCL lines show twice GPU 0, both times the same card.

[3] What exactly is it that you "tried right now" and
[4] Did you see the same GPU 0 twice before you made that change?

Thank you for your help.

After running BOINC 7 for a couple of months, I have to make one comment on the new design.

I don't like it.

I am subscribed to 7 projects, including Cosmology@Home. My machine has 4 CPU cores and runs 32 bit Windows.

The previous version of BOINC would keep a workunit inventory for most of the projects. I would usually run one Cosmology and 3 workunits from other projects. This worked fine.

The new BOINC tends to download a large batch of workunits for one project and run nothing only that one project until the batch is done. Cosmology work units are huge and one cannot reasonably run 4 Cosmology work units at one time on a 32 bit system. They take too much memory.

So everything works fine, except when the scheduler gets its large batch of Cosmology. For the next few days my machine is very slow doing anything else.

I liked the old way better.

No, nothing like that exists.
The closest thing to what you want is the Superhost idea, but that also doesn't exist yet. It's just an idea. http://boinc.berkeley.edu/trac/wiki/SuperHost

By chance, is there an update for the motherboards BIOS?

----- Rom