Cannot start the Guest in VirtualBox

[TimeCoder]

Some of my information:
Machine: MSI GE62-489 (CPU: Intel® Core™ i7-6700HQ @ 2.60GHz × 8 )
Host system: Ubuntu 14.04 64-bit(kernel: 4.4.0-89-generic)
VirtualBox version: 5.1.26 r117224
Guest system: Windows 7 64-bit

When I try to start Guest in VirtualBox, it showed 2 error messages:

First message:

Failed to open a session for the virtual machine Windows 7.

The virtual machine 'Windows 7' has terminated unexpectedly during startup with exit code 1 (0x1).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}

Just like the following figure:

Second message:

Kernel driver not installed (rc=-1908)

The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or 
there is a permission problem with /dev/vboxdrv. Please reinstall 
the kernel module by executing

'/sbin/vboxconfig'

as root.

where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED 
(-1908) - The support driver is not installed. On linux, open returned 
ENOENT.

Just like the following figure:

Then, I do what he told me to do, run the following command in terminal:

$ sudo /sbin/vboxconfig

It shows the following message:

Adding system startup for /etc/init.d/vboxdrv ...
   /etc/rc0.d/K80vboxdrv -> ../init.d/vboxdrv
   /etc/rc1.d/K80vboxdrv -> ../init.d/vboxdrv
   /etc/rc6.d/K80vboxdrv -> ../init.d/vboxdrv
   /etc/rc2.d/S20vboxdrv -> ../init.d/vboxdrv
   /etc/rc3.d/S20vboxdrv -> ../init.d/vboxdrv
   /etc/rc4.d/S20vboxdrv -> ../init.d/vboxdrv
   /etc/rc5.d/S20vboxdrv -> ../init.d/vboxdrv
 Adding system startup for /etc/init.d/vboxballoonctrl-service ...
   /etc/rc0.d/K65vboxballoonctrl-service -> ../init.d/vboxballoonctrl-service
   /etc/rc1.d/K65vboxballoonctrl-service -> ../init.d/vboxballoonctrl-service
   /etc/rc6.d/K65vboxballoonctrl-service -> ../init.d/vboxballoonctrl-service
   /etc/rc2.d/S35vboxballoonctrl-service -> ../init.d/vboxballoonctrl-service
   /etc/rc3.d/S35vboxballoonctrl-service -> ../init.d/vboxballoonctrl-service
   /etc/rc4.d/S35vboxballoonctrl-service -> ../init.d/vboxballoonctrl-service
   /etc/rc5.d/S35vboxballoonctrl-service -> ../init.d/vboxballoonctrl-service
 Adding system startup for /etc/init.d/vboxautostart-service ...
   /etc/rc0.d/K65vboxautostart-service -> ../init.d/vboxautostart-service
   /etc/rc1.d/K65vboxautostart-service -> ../init.d/vboxautostart-service
   /etc/rc6.d/K65vboxautostart-service -> ../init.d/vboxautostart-service
   /etc/rc2.d/S35vboxautostart-service -> ../init.d/vboxautostart-service
   /etc/rc3.d/S35vboxautostart-service -> ../init.d/vboxautostart-service
   /etc/rc4.d/S35vboxautostart-service -> ../init.d/vboxautostart-service
   /etc/rc5.d/S35vboxautostart-service -> ../init.d/vboxautostart-service
 Adding system startup for /etc/init.d/vboxweb-service ...
   /etc/rc0.d/K65vboxweb-service -> ../init.d/vboxweb-service
   /etc/rc1.d/K65vboxweb-service -> ../init.d/vboxweb-service
   /etc/rc6.d/K65vboxweb-service -> ../init.d/vboxweb-service
   /etc/rc2.d/S35vboxweb-service -> ../init.d/vboxweb-service
   /etc/rc3.d/S35vboxweb-service -> ../init.d/vboxweb-service
   /etc/rc4.d/S35vboxweb-service -> ../init.d/vboxweb-service
   /etc/rc5.d/S35vboxweb-service -> ../init.d/vboxweb-service
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why.

There were problems setting up VirtualBox.  To re-start the set-up process, run
  /sbin/vboxconfig
as root.

You can see this line:

vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why.

So I run the following command in terminal:

$ dmesg

It shows about 1000 lines. The whole information it shows is in the attach file. There are some errors and warnings from this information:

[    0.019546] ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20150930/dswload-210)
[    0.027179] ACPI Error: 1 table load failures, 9 successful (20150930/tbxfload-214)
[    0.205608] ACPI Error: [^^^PEG0.PEGP.EASP] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-359)
[    0.205611] ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.EC._REG] (Node ffff88027b0ef4b0), AE_NOT_FOUND (20150930/psparse-542)
[    0.205622] ACPI : EC: Fail in evaluating the _REG object of EC device. Broken bios is suspected.
[    0.221593] ACPI Error: [^^^PEG0.PEGP.EASP] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-359)
[    0.221596] ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.EC._REG] (Node ffff88027b0ef4b0), AE_NOT_FOUND (20150930/psparse-542)
[    2.603310] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-19.ucode failed with error -2
[    2.603334] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-18.ucode failed with error -2
[    2.603347] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-17.ucode failed with error -2
[    3.273673] EXT4-fs (sda7): re-mounted. Opts: errors=remount-ro
[  126.578953] systemd-hostnamed[5793]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname!
[ 1952.203735] systemd-hostnamed[13694]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname!

Now I don't know what to do. The Guest system just cannot start.

Another information:

If I choose kernel 3.19.0-25-generic to come in when I start up my machine, the same VirtualBox can use normally. The Guest system win7 can start normally. But I never succeed to start guest normally with any linux kernel who is newer than 3.19.0-25

So, how to solve this problem? Thank you very much!

[TimeCoder]

The message it shows after I run 'dmesg' in terminal.

[Frank Mehnert]

Please execute

/sbin/rcvboxdrv setup

when you are currently running the 4.4 kernel and please post the resulting output.

[Lucius]

Sorry. It's another problem . (But the same topic) I dont want to make new ticket. There is no reason to write it again I just leave it here, because it is about "Cannot start the Guest in 5.1.26") https://www.virtualbox.org/ticket/12227

[TimeCoder]

Replying to frank:

Please execute

/sbin/rcvboxdrv setup

when you are currently running the 4.4 kernel and please post the resulting output.

vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why.

[aeichner]

Please attach the new output of the dmesg command after the error message.

[trespaser5]

Got this error after upgrade to 5.1.30, after re-install of 5.1.28, everything was ok