FYI: I recently posted a couple of messages on the vLHC Communication with VM Hypervisor Failed forum which describe some problems I encountered using the standard BOINC download of BOINC 7.6.9, VirtualBox 4.3.12 for Windows 64-bit on my Windows 10 laptop. The problems went away when I updated to VirtualBox 5.0.10.

Forwarded to the developers.

---

Rom Walton wrote:

I’ve started including 5.0.8 in newer BOINC builds. 5.0.10 is where VirtualBox started claiming compatibility.

I’ll update things so we include 5.0.10 in future BOINC builds.

----- Rom

---

BOINC 7.6.18 is available for testing. The VirtualBox version has 5.0.10 integrated.

- boinc_7.6.18_windows_intelx86_vbox.exe
- boinc_7.6.18_windows_x86_64_vbox.exe

---

I just found this thread, after I had a problem with VirtualBox processes running on normal priority instead of below priority.
The original question was posted on the vLHC@home forum here:http://lhcathome2.cern.ch/vLHCathome/forum_thread.php?id=1744.

Summary: VirtualBox versions after 4.3.12 do not (at least on Windows) support changing the priority of its processes. See here: https://www.virtualbox.org/ticket/13500. This means that while BOINC is running, your computer can noticeably slow down, because the VirtualBoxes are running at normal priority and are competing with normal operations for processor time.

I was running 5.0.12, but downgrading to 4.3.12 solved this problem for me. I think that it is important for users to be able to use their computers while running BOINC, else they might stop donating computer time or switch off BOINC from time to time. For this, it is very important that BOINC can set the VirtualBox processes to below normal priority!

Thus, are you sure it is a good idea to use a newer VirtualBox version, or has this problem been solved somehow? (I would like to know (how) if it is!)

For this, it is very important that BOINC can set the VirtualBox processes to below normal priority!

Oracle made that impossible. They've hardened up the processes and so it's not possible for BOINC to adjust he priority. Since we cannot change that, you'll have to complain about it at Oracle, as they make VirtualBox.

See Jacob Klein's ticket on this: https://www.virtualbox.org/ticket/13500

---

Yes, making it impossible to do trouble-free crunching on Windows 10 with all cores working for a VirtualBox project. If you use an old version, you get errors, and if you use the new version, your computer will noticeably slow down...

Heads up all, I've personally had BOINC running with VirtualBox 5.0.10 on my Windows10 machine and it has been causing blue screen of death (BSOD) errors. (KERNEL_SECURITY_CHECK_FAILURE). I've determined at least in my case, the problem was with BOINC itself, and not VirtualBox.

I went through a complete uninstall of ALL of my drivers and BOINC, and re-installed them one by one with a day and a windows 10 restart in-between each one. The final re-install was BOINC 7.6.9 without VirtualBox (fresh re-install downloaded from this site) and it caused a BSOD *DURING* installation....

For now I've removed BOINC from my machine completely, and so far my machine is not crashing again (1 day worth now...)

Heads up as I said... for me these BSOD errors started on 23rd December.. not a fun way to spend the holiday season....

Heads up all, I've personally had BOINC running with VirtualBox 5.0.10 on my Windows10 machine and it has been causing blue screen of death (BSOD) errors. (KERNEL_SECURITY_CHECK_FAILURE). I've determined at least in my case, the problem was with BOINC itself, and not VirtualBox.

I went through a complete uninstall of ALL of my drivers and BOINC, and re-installed them one by one with a day and a windows 10 restart in-between each one. The final re-install was BOINC 7.6.9 without VirtualBox (fresh re-install downloaded from this site) and it caused a BSOD *DURING* installation....

For now I've removed BOINC from my machine completely, and so far my machine is not crashing again (1 day worth now...)

Heads up as I said... for me these BSOD errors started on 23rd December.. not a fun way to spend the holiday season....

7.6.9 ran just fine on multiple rigs for me with no BSOD's. I'm guessing this is limited to your setup...

---

Since a few days, I'm having the same problem. When attempting to start the BOINC client, I immediately get a BSOD stating "Kernel_Security_Check_Failure" as reason. Running client 7.6.9 on Win10. This only occurs on my HP Envy Laptop, the same config on my Alienware PC just runs fine (up to now...)
Cheers

Causes of KERNEL_SECURITY_CHECK_FAILURE Blue Screen Errors

* Incorrectly configured, old, or corrupted device drivers. (very common)
* Corruption in Windows registry from a recent software change (install or uninstall).
* Virus or malware infection that has corrupted Windows system files or Windows Operating System-related program files.
* Driver conflict after installing new hardware.
* Damaged or removed system files after you’ve installed software or drivers related to Windows Operating System.
* Error 0x139 blue screen caused by a damaged hard disk.
* KERNEL_SECURITY_CHECK_FAILURE STOP error due to memory (RAM) corruption.

KERNEL_SECURITY_CHECK_FAILURE blue screen errors can be caused by a variety of hardware, firmware, driver, or software issues.

Putting kernel_security_check_failure windows 10 into Google gives a scarily amount of people having this problem, with everything imaginable. It's not BOINC causing the error, but Windows 10.

---

Seems like i've found the culprit: it was the latest Nvidia Graphics Driver 361.43. From the Device Manager, i re-installed the previous driver, and no more BSOD when starting the Boinc Client....
Cheers R

Seems like i've found the culprit: it was the latest Nvidia Graphics Driver 361.43

hmmm, considering i have an nvidia driver of that exact version, maybe it was that instead...

what doesn't add up yet, is that on that nvidia driver version but without boinc running nor installed, windows 10 here has been fine for about 4 days????

maybe i'll wait for a few more nvidia driver versions before trying boinc again, and report back...

hmmm, considering i have an nvidia driver of that exact version, maybe it was that instead...

I've downgraded my nVidia driver to 359.06 using a nVidia GEForce 740M, for my Win10 machine.

I guess all I can say is that for my set up, it is likely that the fault was with the nVidia driver version, but not conclusive, since I've just re-installed boinc successfully (but with BOINC 7.6.22 instead of the previous 7.6.9) and running for only a few minutes so far.

If there's any issues, I'll report back... possibly starting an nVidia-specific thread instead to avoid getting off topic here.

what doesn't add up yet, is that on that nvidia driver version but without boinc running nor installed, windows 10 here has been fine for about 4 days????

When BOINC starts up it will detect any Nvidia, Intel or AMD/ATI GPU that is capable of doing calculations for science.

For this detection to work, drivers are needed that hold the required components (CUDA, OpenCL) and that can work together with the operating system in a sturdy way. Not all drivers are tested in this way, so it can happen that some (early) drivers cause trouble on people's computers. This being one of them.

---

Not all drivers are tested in this way, so it can happen that some (early) drivers cause trouble on people's computers.

the trouble being that in this case, the newer nvidia v361 driver caused the problems, but the older v359 driver is fine!

still running 359.06 just fine, with GPU WU's processing ok... let's hope nVidia fixes their driver...

FYI: I recently posted a couple of messages on the vLHC Communication with VM Hypervisor Failed forum which describe some problems I encountered using the standard BOINC download of BOINC 7.6.9, VirtualBox 4.3.12 for Windows 64-bit on my Windows 10 laptop. The problems went away when I updated to VirtualBox 5.0.10.

VBox 4.3.12 is the version that isn't hardened and allows dll injections. It's the version that I had to use to get a stripped down Win 7 x64 version to run VBox. Stepping up to 4.3.14 and the unable to start VDD errors from VBox return.

So maybe they knew something about WinX that they hardened against and it's no surprise 4.3.12 fails? Oracle laid out many reasons for hardening their processes on the forums and the topic was debated hotly for months.
But WinX is a telemetry gathering resource for MS and I think in part this was a political/business decision and not just security reasoning.