LHC@home

Hi,
I just started using BOINC a few days ago (vers. 7.8.3 (x64)). I have two laptops, both running Win 10. On the first one, I initially thought everything was working fine. However, yesterday I tried installing BOINC on the second laptop. Again everything seemed to install without error. I logged in using the same account details as the first. But after connecting with the same project (LHC@home) BOINC only ever shows "No work available to process". I looked at the event log, and it doesn't show anything unusual - no errors. I looked at my project task list. The first laptop is the only one that appears to have completed work successfully. The second laptop shows a list of tasks, but all display the comment "Error while computing".

I have tried uninstalling using the Windows control panel, but clearly a full uninstall is not being completed, leaving some residual files somewhere, because when I reinstall, it automatically completes the login with my previous details and preferences. And I get the same issues.

I posted this info on the BOINC message board and one of the members pointed out that although my first laptop was running tasks, they were all SixTrack tasks. I checked the VirtualBox for both and found that both are displaying repeated errors like the one below.

Runtime error opening 'C:\ProgramData\BOINC\slots\0\boinc_26c29e8c79bd585e\boinc_26c29e8c79bd585e.vbox' for reading: -103 (Path not found.).
F:\tinderbox\win-5.2\src\VBox\Main\src-server\MachineImpl.cpp[741] (long __cdecl Machine::i_registeredInit(void)).
Result Code:
E_FAIL (0x80004005)
Component:
MachineWrap
Interface:
IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}

Both laptops are HP with i7 processors running Win 10.

Any ideas?

Thanks,
Craig.

Welcome Craig to the project and to the message board.

Your first laptop was lucky, cause at that moment there were still SixTrack tasks available.
There are no left in the queue https://lhcathome.cern.ch/lhcathome/server_status.php
That laptop got also some VM-tasks, but they all failed like your second connected laptop.
There must be something wrong with your VBox setup. Because both machines are running Win10, the first thing comes in my mind is Hyper-V running on your machines and that's conflicting with VirtualBox.
An extensive checklist from User Yeti you'll find here

Hi, Craig.

SixTrack produces valid results as it is a windows native app.

Other subprojects need VirtualBox as hypervisor and there are a few pitfalls to work around.
One of them is that it seems you didn't activate VTx in your computer's BIOS (Error Code: ERR_CPU_VM_EXTENSIONS_DISABLED).
The best would be that you work through Yeti's checklist.

<edit>
Just a few seconds CP.
;-)
</edit>

Thanks to all who helped. I think I've got it working on both laptops now. Issue was that that the virtual doo-da was disabled in BIOS. Enabled and re-installed the software on both and now seems fine.

Thank you!
Craig.