Hi all,
For some reason all of my Einstein tasks have failed with computational error? :compbash:
I now have to wait 1 whole day in order to receive more tasks to complete for the AA which is annoying
I will continue to crunch for POGS with my extra CPU core while waiting for Einstein to update
Has anyone else encountered this before?
Merry Crunching!
Zach
My connection is bad at the moment so I cannot search through the members list to find you. Can you send me a link to one of your tasks that are failing. I am not having any problems for a change but have in the past. Is your driver updated to the latest version ??
Is this you Zach?
https://boincstats.com/en/stats/5/host/detail/12538967
Anonymous.
Using a 750Ti?
I'm not sure why you would be getting computational errors. The only time I see that is if my PC crashes and it messes up the WU's being crunched. I'm also not sure how to look up your Einstein details.
For all the years I've been doing this, it doesn't get any easier :/
Pretty sure this is you?
https://einsteinathome.org/account/219145/computers
Can only see one task with an error at the moment:
"Error in OpenCL context: CL_MEM_OBJECT_ALLOCATION_FAILURE error executing CL_COMMAND_WRITE_BUFFER on GeForce GTX 750 Ti (Device 0)."
Did a quick google, looks like it might be due to running out of GPU memory? 2gb is a fair bit, but are you running more than one task?
I get nothing but compute errors on the Titan V's but the Vega 64 LC's seem quite happy with Einstein@Home... *touch wood*.
Sample error as follows: https://einsteinathome.org/task/759311291
<core_client_version>7.8.3</core_client_version>
<![CDATA[
<message>
The printer is out of paper.
(0x1c) - exit code 28 (0x1c)</message>
<stderr_txt>
I kid you not :rofl:
Yea that's strange one that's for sure. LOL
https://einsteinathome.org/content/task-running-out-paper (https://einsteinathome.org/content/task-running-out-paper)
Have you tried re-downloading fresh drivers from Nvidia? Windows 10 is notorious for over writing good working drivers with their own driver versions during windows updates. For some reason the MS version of the driver doesn't contain the OpenCL component we need for crunching. It's possible the MS driver may contain cuda but not openCL so some projects work while others don't.
Just a thought, all the best..
I had reinstalled display drivers after last Win Update because it already bit me for PrimeGrid, will DDU and do a fresh uninstall tonight to see if anything has gone amiss in the meantime.
Thanks for the reminder :)
Edit: Wasn't a goer with the same 397.67 drivers reinstalled but I noticed they had new ones out. With 397.93 installed everything is AOK.