Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm using PortableVirtualBox for about a year with no problems. But from two weeks now -without upgrading or updating anything on Virtualbox or anything related on my PC- after running any of my VMs for a while then I cannot start any other VM, because VB pops up this error

VirtualBox - Runtime Error
Cannot access the kernel driver!
Make sure the kernel module has been loaded successfully.

If I check the VB kernel driver with ServiWin the driver (VBoxDrv) shows up as "Stopping...", but never stops totally.

  • I tried with NET STOP VBoxDrv (as administrator), but it says that the service is starting or stopping
  • Tried the same running as System with PSEXEC -s, same result.
  • Reinstalled PortableVB and the VB runtimes, no luck
  • Try to kill the program using sc queryex vboxdrv, but the status is STOP_PENDING and the PID is 0, then I cannot find the process to kill
  • Checked memory with Memtest86 disk with MHDD, did a Prime95 torture test to find posible hardware errors: no problems there
  • If I reboot the PC, then I can use VB but the problem strikes again after starting a couple of VMs (or restarting the same VM after using it for a while)

My configuration:

  • PortableVirtualBox (Launcher)
  • VirtualBox 4.0.10.r72479
  • VB USB and network drivers installed
  • Win7 Pro-64 Host
  • AMD Athlon II X3 450 / 8 Gby RAM

Any ideas to fix the initial error or force the VB driver to restart without rebooting?

share|improve this question

This worked for me

sudo apt-get install dkms
sudo apt-get -y install linux-headers-generic linux-headers-lbm-3.5.0-18-generic
sudo /etc/init.d/vboxdrv setup

Remember that the linux-headers-lbm-3.5.0-18-generic may be of a different version than the time of writing

EDIT: Also this post seems to be of help

share|improve this answer

1) Backup your Virtualbox VDI’s

2) Uninstall Virtualbox

3) Remove any remnants of the install, depending on your version you should check both of these locations:

“C:\Program Files\Sun\Virtualbox” – or a directory similar to that under “Sun”.

“C:\Documents and Settings{account username}.VirtualBox\Machines

4) Reinstall Virtualbox and create a new VirtualMachine.

5) When prompted, choose your existing VDI and voila, you should be up and running again

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.