My cruncher has produced ~70 terminated WUs in quick succession with the following STDERR output;

Stderr output
<core_client_version>7.4.23</core_client_version>
<![CDATA[
<message>
process exited with code 212 (0xd4, -44)
</message>
<stderr_txt>

</stderr_txt>
]]>

Here's the BOINC start-up messages showing it's starting state;

1: 16-Nov-2014 09:58:24 (low) [] Starting BOINC client version 7.4.23 for x86_64-pc-linux-gnu
2: 16-Nov-2014 09:58:24 (low) [] log flags: file_xfer, sched_ops, task
3: 16-Nov-2014 09:58:24 (low) [] Libraries: libcurl/7.35.0 OpenSSL/1.0.1f zlib/1.2.8 libidn/1.28 librtmp/2.3
4: 16-Nov-2014 09:58:24 (low) [] Data directory: /var/lib/boinc-client
5: 16-Nov-2014 09:58:24 (low) [] CUDA: NVIDIA GPU 0: GeForce GTX 650 Ti BOOST (driver version 331.38, CUDA version 6.0, compute capability 3.0, 1023MB, 996MB available, 1746 GFLOPS peak)
6: 16-Nov-2014 09:58:24 (low) [] Host name: stippy
7: 16-Nov-2014 09:58:24 (low) [] Processor: 2 GenuineIntel Intel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz [Family 6 Model 15 Stepping 11]
8: 16-Nov-2014 09:58:24 (low) [] Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm lahf_lm dtherm tpr_shadow vnmi flexpriority
9: 16-Nov-2014 09:58:24 (low) [] OS: Linux: 3.13.0-39-generic

Any idea on how to resolve this and what is error 212?

Thanks,
Steve

Interesting update on my failed GPUGRID WUs. I stopped WUs for GPUGRID and loaded Einstein@Home. So far, the machine is crunching E@H GPU WUs with no errors while the GPUGRID WUs were failing immediately. Anyone else having issues?
Steve

Same problem here. Probably it is related to Nvidia 331.38 driver. They were going to drop support for it. We should update to newest drivers but the drivers in the repos have problems with CUDA and Boinc.

CPU tasks are crunching but when I restart Boinc all the progress is lost...

I'm not experienced with Linux, but you should check the "Important news for Linux crunchers" thread.
You are right about that your drivers need to be updated.

I had and stopped crunching for Gpugrid. But after some days checked and it got CUDA42 jobs and crunched them succesfully. Now tasks are said to be cuda42 but ends with an error, probably they are cuda60 internally and need the driver update.

I thought the new drivers weren't required until 2015? My cruncher has been completing CUDA 42 WUs successfully until today. I've tried unsuccessfully for several hours to upgrade drivers to higher then 331 with no luck and was hoping to run CUDA 42 WUs through the end of 2014. For the time being I've stopped accepting work for this project until someone can find a solution to the CUDA 42 WUs terminating with errors. I'm fairly certain that it's a project issue as the cruncher is completing E@H GPU WUs successfully.
Thanks,
Steve

I don't check in often so I upgraded my box earlier this month.