So if I try this again in the future I may have to do a bit of research as to which of those in my signature actually have work that can use CPU only.

Or, as in the case of Seti, just select the CPU for work procesing & don't enable it for the GPU.

I think my cache settings were more than ample and last time I tried that Seti, for one, didn't send any work for several months.
Do they actually ever have non-GPU projects now?

Yes, both apps in SETI (MB and AP) run on CPU or GPU. And the WUs are the same for CPU and GPU, they become a GPU or CPU task when assigned to the host.
Besides SETI I also crunch form Einstein and their main apps (the searches for gravitational waves) only run on CPU... they use GPU for pulsar findings.

Perhaps two graphics cards are needed in order to get this working as it should be doing?

In the end you probably will use both cards for crunching if you have more than one such card installed in your system.

If you're so frustrated with GPU computing, why not just go with CPU computing instead? No need to throw in the towel when there's an alternative.

Very sorry to see you go Ex_Brit, hope you will come back.

Chris

<cc_config>
<log_flags>
</log_flags>
<options>
<ignore_cuda_dev>0</ignore_cuda_dev>
</options>
</cc_config>

7.0.31 Development version (MAY BE UNSTABLE - USE ONLY FOR TESTING)

Hmm, that's interesting. I use TThrottle to throttle back both the GPU and CPU should certain temperatures be exceeded. Do you think that might be something nto do with that?

The basic math of the elapsed time cutoff is 10x the estimated runtime. I doubt TThrottle is reducing processing rate that much unless you have a serious overheating problem. There are hints in the stderr details that those tasks were only about 1/3 done when they were killed, too. If that's right the tasks were slowed by a factor around 30x.

                                                                    Joe