VirtualBox suddently stopped working. Cannot run any machine

[MadNoblex]

Hello, I'm using VirtualBox to run Linux hosts (Ubuntu, CentOS) on my Windows machine.
Without any reasonable reason, today I am not able to run any host, receiving this error:

The virtual machine 'Odoo 8 sito Gustop' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\Alex\VirtualBox VMs\Odoo 8 sito Gustop\Logs\VBoxHardening.log'.
(More info in the attached screenshot and log)

Error Screenshot

Cattura.PNG (16.64 KiB) Viewed 1680 times

Logs.rar

Log Files

(88.71 KiB) Downloaded 1 time

Codice 'uscita:
E_FAIL (0x80004005)
Componente:
MachineWrap
Interfaccia:
IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}

I was using VirtualBox 4.3.29, and since the error suggested to reinstall, I updated it into 5.0.10
Any advice?
Thank you

ADDITIONAL INFO:
I went into my Oracle/VirtualBox/driver folder and installed all the .inf file I found and it dind't fix the problem
I am running a Windows 8.1 x64 machine

[michaln]

There's no "5.0" release as such. There's 5.0.0, 5.0.2 etc., now 5.0.10. Which one did you try? 4.3.34 should work as well.

[MadNoblex]

I am with 5.0.10 r104061
I updated VirtualBox AFTER the error showed up.

[michaln]

I assume you read the error message. So what did 'sc query vboxdrv' say, and did rebooting make any difference?

[MadNoblex]

The reboot didn't help.

Sorry I forgot to post the sc.exe report

sc.exe query vboxdrv

Cattura.PNG (11.01 KiB) Viewed 1672 times

which translated basically means:
SERVICE NAME: vboxdrv
TYPE: 1 KERNEL_DRIVER
STATE: 1 STOPPED
WIN32_EXIT_CODE: 1077 (0X435)
SERVICE_EXIT_CODE: 0 (0x0)
CONTROL_POINT: 0x0
WAIT_SUGGEST(?): 0x0

[michaln]

What does 'sc start vboxdrv' do? May require an elevated prompt.

[MadNoblex]

I'm already with a cmd with administrator rights.
Standing at Microsoft doc page (I am seeing this sc.exe for the first time as well):

SC Communicates with the Service Controller and installed services. SC.exe retrieves and sets control information about services. You can use SC.exe for testing and debugging service programs. Service properties stored in the registry can be set to control how service applications are started at boot time and run as background processes. SC.exe parameters can configure a specific service, retrieve the current status of a service, as well as stop and start a service. You can create batch files that call various SC.exe commands to automate the startup or shutdown sequence of services. SC.exe provides capabilities similar to Services in the Administrative Tools item in Control Panel.

sc query

Obtains and displays information about the specified service, driver, type of service, or type of driver.
ServerName : Specifies the name of the remote server on which the service is located. The name must use the UNC format ("\\myserver"). To run SC.exe locally, ignore this parameter.

ServiceName : Specifies the service name returned by the getkeyname operation. This query parameter is not used in conjunction with other query parameters (other than ServerName).

type= { driver | service | all } : Specifies what to enumerate. The default type is service.

type= { own | share | interact | kernel | filesys | rec | adapt } : Specifies the type of services or type of drivers to enumerate.

state= { active | inactive | all } : Specifies the started state of the service for which to enumerate. The default state is active.

bufsize= BufferSize : Specifies the size (in bytes) of the enumeration buffer. The default size is 1024 bytes. Increase the size of the enumeration buffer when the display resulting from a query exceeds 1024 bytes.

ri= ResumeIndex : Specifies the index number at which to begin or resume the enumeration. The default is 0. Use this parameter in conjunction with the bufsize= parameter when more information is returned by a query than the default buffer can display.

group= GroupName : Specifies the service group to enumerate. The default is all groups.

/? : Displays help at the command prompt.

I am still a bit confused about what could have caused this error (since i turned off the PC yesterday while it was full working and I used it again this morning) and I have no idea on how to solve it. In the mean time I am trying to downgrade to a 4.3.xx version and see what happens