VM start failure - error code : 0xc0000005

[toto42titi]

I'm on a company computer and I can't start my VMs anymore. It was working great for 2 months. I have limited access and can't reinstall windows. All the other programs are working fine. I don't know what to do.
Here is the error message :

Code: Select all

Échec de l'ouverture de session pour la machine virtuelle debian.

The virtual machine 'debian_vault_mysql' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005).  More details may be available in 'D:\vbox_vm\debian\Logs\VBoxHardening.log'.

Code d'erreur : E_FAIL (0x80004005)
Composant : MachineWrap
Interface : IMachine {5047460a-265d-4538-b23e-ddba5fb84976}

Edit:  the logs are now in the attachment. Sorry and thank you

[socratis]

Can you edit you message and replace the verbatim copy/paste of the VBoxHardening.log with a ZIPPED version of it, which you can attach? It helps you, it helps us, it helps the server, it helps save a (virtual) tree or two...



You seem to have a hardening problem:

36e0.2ed0: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0xc0000005 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 62 ms, CloseEvents);

Please read really carefully the following FAQ: Diagnosing VirtualBox Hardening Issues for some generic guidelines/ideas. Remember, these are guidelines, not the exact solution, you have to use your judgement as to which program might be responsible.

I would start with either updating, or completely uninstalling (not simply disabling), or adding an exception to TrendMicro:

36e0.2ed0: supR3HardenedWinFindAdversaries: 0x8
36e0.2ed0: \SystemRoot\System32\drivers\tmcomm.sys:
36e0.2ed0:     ProductName:     Trend Micro Eyes

[toto42titi]

Hello ! thank you for your reply. I'm doing this right now.

Edit:  updating Trend Micro didn't work

[dbouras]

Make sure that VBoxSDS (the service implementing the COM server for the VirtualBox API) is running.

I had the same issue: VirtualBoxVM crashing with 0xc0000005 and absolutely no other clue in the logs. After seven weeks of searching right and left I finally traced it down to incorrect configuration for VBoxSDS. It's still a mystery why and how its startup type was changed to "Manual" from "Automatic". The result was that, after a reboot, it didn't start up again. This prevented VirtualBoxVM from starting, until I figured it out just today.

I hope this helps.
All the best,
Dimitri

[dbouras]

False alarm.

There's something weird going on with VBoxSDS but configuration is not it. "Manual" is correct as it starts "on demand" -- it doesn't need to be running all the time. The only hypothesis that makes sense at this point is that the issue is related to DCOM and interaction between VBoxSDS and VirtualBoxVM.

Check my thread if you're interested in what I've tried so far.