It's been a great run Eric. I joined with a 386dx4 in May of '99, and I've been active since. While I may swap over to another project, rest-assured my computers will ALWAYS be linked to SETI@Home if and when you fire it back up.

I think 442.19 has definitely fixed it!

In my testing of the 442.19 drivers, I had no problems processing VHAR work items, on my main rig (RTX 2080, GTX 980 Ti, GTX 980) using Windows 10.
All 3 GPUs acted correctly.

3. SoG app only
4. Arecibo VHAR tasks only.

Ageless has a good point, I'd be interested in knowing this too..I can see the i5 has CPU work units but your i7 still doesn't, though the GPUs are working fine :) Are you listing them at different locations with different parameters?

Calico,

Just a question. I noticed that there is about a 3 hour gap between your first CPU work unit and the GPU..What happen in between those times? Did you not have the graphic card installed yet or did you change out what you had? Just curiosity for my own sake. Since it's still not working, finish what you have, don't get any new task. After they upload, uninstall Bonic. Then turn of the computer for a little bit (5-10 mins). Restart and download bonic (just incase the previous downloaded installer is corrupt) and install. Let it run for a while (hours) before you try to tinker with it and lets see what it does. Just my 2 cents

I don't believe anyone has asked yet what your setting is for Minimum work buffer. If you've got it set to a high number, say 9 or 10 days, you might want to try reducing it, perhaps down to 1.

I mention that because, in the back of my mind, I have a vague recollection of someone else mentioning that a large work buffer number causes the project to think that your machine will take much longer to process the tasks it receives, and actually ends up sending it fewer tasks to ensure that deadlines will be met. Because your machines haven't established a usable APR for v7 CPU tasks, estimated run times will initially be vastly inflated to begin with. If a large work buffer number adds to those estimates, it's possible that the scheduler thinks that it simply has no tasks available that could possibly be completed by the expected deadline, rather than having no tasks available at all. That might be especially true when you have other projects sharing the CPU.

Well, my question has been partially answered.. I suppose I should have just read the SETI@Home CUDA FAQ:
http://setiathome.berkeley.edu/cuda_faq.php
From that FAQ:
[quote]Q) Does SETI@home run GPU and CPU versions simultaneously?

No. If BOINC determines your CPU is capable of running the CUDA version, only the CUDA version of SETI@home will run. One copy will run on each GPU you have installed. If you want to keep your CPUs occupied at the same time, you can join another BOINC project.
The BOINC developers expect the capability to run CPU and GPU jobs simultaneously for the same application will be added in the next couple months.

And it was. I run both CPU and GPU WU at the same time with no problem.

Well, my question has been partially answered.. I suppose I should have just read the SETI@Home CUDA FAQ:
http://setiathome.berkeley.edu/cuda_faq.php

If I had to guess, I'd say that FAQ is about 5 years out of date! Too bad they didn't put a datestamp on it.

Well, my question has been partially answered.. I suppose I should have just read the SETI@Home CUDA FAQ:
http://setiathome.berkeley.edu/cuda_faq.php
From that FAQ:

Q) Does SETI@home run GPU and CPU versions simultaneously?

No. If BOINC determines your CPU is capable of running the CUDA version, only the CUDA version of SETI@home will run. One copy will run on each GPU you have installed. If you want to keep your CPUs occupied at the same time, you can join another BOINC project.
The BOINC developers expect the capability to run CPU and GPU jobs simultaneously for the same application will be added in the next couple months.

Obviously you are not reading/understanding that page properly at all. :-(

Q) Does SETI@home run GPU and CPU versions simultaneously?

No. If BOINC determines your CPU is capable of running the CUDA version, only the CUDA version of SETI@home will run. One copy will run on each GPU you have installed. If you want to keep your CPUs occupied at the same time, you can join another BOINC project.
The BOINC developers expect the capability to run CPU and GPU jobs simultaneously for the same application will be added in the next couple months.