Computation Errors after updating BOINC & VirtualBox

Jarried Pille
Jarried Pille
Joined: 6 Jul 06
Posts: 1
Credit: 28414106
RAC: 0
Topic 222044

Hi,

I've been crunching data for Einstein@ successfully for quite some time using my main rig:

Win10 Pro x64 1909

Intel Core i5-2320

16GB RAM

Sapphire RX580 Nitro+ 8GB

BOINC 7.16.5 (x64)

VirtualBox 6.0.14

 

Tonight I saw a notice that there was a new version of BOINC and associated compatible version of VirtualBox included. I pulled the trigger and all seemed well until it started running some new Einstein@ tasks. The task(s) start, my computer will momentarily stop responding to input, then returns to normal, then my monitor goes black as if it has lost input, and then returns to normal yet again. I check BOINC and I see computation error for each of these new tasks every time it tries to run one. I checked the log and it mentions that "Output file......absent" for each of the failed tasks. Updating BOINC and VirtualBox were the only things that I did. Any ideas?

https://einsteinathome.org/host/12798901/tasks/6/0

Thanks,

Jarried

Richie
Richie
Joined: 7 Mar 14
Posts: 656
Credit: 1702989778
RAC: 0

VirtualBox that is bundled

Hi! VirtualBox that is bundled with Boinc is always some old version already when that bundle is released. It's better to install plain Boinc and download the installer for VirtualBox directly from https://www.virtualbox.org/

Gary Roberts
Gary Roberts
Moderator
Joined: 9 Feb 05
Posts: 5872
Credit: 117826395085
RAC: 34727766

Jarried Pille wrote:... I

Jarried Pille wrote:
... I checked the log and it mentions that "Output file......absent" for each of the failed tasks. Updating BOINC and VirtualBox were the only things that I did. Any ideas?

Unfortunately, the event log is what BOINC sees and uses and not what the app writes into.  In this case the app quit (crashed) very quickly and BOINC went looking for output results.  Because of the crash, there are none - so BOINC just reports that there were none.

The two important things to check are, firstly the startup messages in the event log to see what BOINC detected regarding your hardware.  BOINC will report on your hardware, GPU details, how much RAM, OpenCL capability, etc.  You should check that all those details look correct.

The app reports its progress in a separate file and that is sent back to the project even if the app crashes.  You provided a link to your tasks list - thanks very much for that.  By clicking on the Task ID link for a failed task you get to see what the app reported.  Scroll down below the "stderr output" heading looking for the first "Error".  I did that for one of your tasks and such a line contained the following (I left out unimportant stuff, but check for yourself):-

OpenCL CreateCommandQueue failed: CL_OUT_OF_HOST_MEMORY

If BOINC is properly detecting your 8GB card there should be plenty of available memory but you should check that carefully to see what BOINC said.  Did Windows happen to update drivers on you at the same time?

Unless you happen to need VirtualBox for other projects, maybe you should try Richie's advice.  See if things work with the standard BOINC and then install separately if you need it.  I don't use Windows at all so I can't quote specific advice.

Cheers,
Gary.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.