virtualbox failed to load kernel driver!

[MilacronITDoug]

Hello,
I am running Windows XP as a guest with 1024mb ram assigned on VirtualBox Version 4.3.6-91406, with Windows 7 32-bit on the host machine with 4gb ram and an intel i5 2.53 dual core.
I have installed no guest additions.

I do not have a log file, as I am doing all of this remotely, and am trying to keep from bothering my end user as little as possible. I can retrieve it if necessary.

Virtual box opens just fine, but when you launch the vm, it comes back with Error: virtualbox failed to load kernel driver! when you click abort, you get a second window with: Exit Code 1 E_FAIL (0x80004005)

The VM name is: "Milacron - Windows XP"

Everything is installed in the default directories. c:\program files\oracle\virtualbox

I have played with vboxmanage very little, and to be quite honest, am not familiar enough with it to get anywhere.

This issue just came up this past week, the user has not made any changes to his machine, other than possibly some windows updates. No other software or hardware changes have been made. Cannot isolate the cause of this error.

Any Help would be GREATLY appreciated! Thanks in advance.

[loukingjr]

make sure the KB3004394 update is not installed in the host machine.

[MilacronITDoug]

Kb3004394 is in the update history, but not in the installed updates. also in the update history is KB3024777 which as i read seems to be a fix for KB3004394. still having the same issue.

"Failed to open a session for the virtual machine Milacron - Windows XP.

The virtual machine 'Milacron - Windows XP' has terminated unexpectedly during startup with exit code 1.

Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}"

[socratis]

Take a look at the discussion: Windows 4.3.20 specifically for errors due to security. You might find some newer test builds and/or other helpful hints.

[MilacronITDoug]

Thanks socratis, i have read through that discussion, and none of the issues posted seem to be related to what my user is experiencing.

I have tried a complete uninstall, and reinstall, including replacing the .vdi file with a fresh .vdi file.

First Initial install was on October 1st, user has had no issues until this started the first week of December.

[socratis]

So that means that you tried to downgrade to 4.3.12, right? And the crash is still happening?

[MilacronITDoug]

I have not tried a downgrade, we have 30+ users using this version that are not experiencing any issues. This seems to be an isolated case.

[socratis]

So is the software installed on each machine, I bet you. Chances are that if you read the whole thread I pointed you to, you would see that it is a barrage of software that can make VBox > 4.3.12 crash and burn. From antivirus, to firewalls, to debuggers, to theme-changing applications. You still have NOT posted a VBox.log file which would tell us (in all probability) what the offending software might be. Could you zip one and post it?

[MilacronITDoug]

Yes software is installed locally on each machine, we try to limit software to a minimum, all of our antivirus software is controlled from the server, just the agent gets installed locally, all local firewalls are defaulted, unless the users have altered something. log files are attached, hopefully this will help shed some light on things. sorry for the delay. Thanks again for all your help.

[socratis]

The first thing I noticed was that the VM was up for 22 min, 1hr 40min, 2hr 03min and 1hr 08min (4 logs, 4 runs). That doesn't go together with what you've said so far. So what's going on?

PS. Don't send a PM about things like that. We're a community. Nobody else notices if you send me a PM.

[MilacronITDoug]

As i stated in my first post, the VM was working fine. We installed the virtual box around the first week of October and it ran fine until the 2nd or 3rd week in December, then he came in one morning tried to run the vm, and started receiving this error. So there will be logs of it running, but i have not been able to get it to launch since December. I wouldn't have came to this forum if i felt i hadn't already exhausted my knowledge of possible fixes to the problem. That being said, i am not overly familiar with virtual box, up to this point we install it , and it works. lol

ps, my apologies for the pm, just trying to get a timely response for my user.

[Perryg]

Code: Select all

a60.1a70: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status -22900 (0xffffa68c)) on \Device\HarddiskVolume2\Windows\System32\crypt32.dll
a60.1a70: Error (rc=0):
a60.1a70: supR3HardenedScreenImage/LdrLoadDll: cached rc=Unknown Status -22900 (0xffffa68c) fImage=1 fProtect=0x0 fAccess=0x0 cErrorHits=2 \Device\HarddiskVolume2\Windows\System32\crypt32.dll
a60.1a70: Error (rc=0):
a60.1a70: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Windows\system32\crypt32.dll': rcNt=0xc0000190
a60.1a70: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0xc0000190 'C:\Windows\system32\crypt32.dll'
a60.1a70: Fatal error:
a60.1a70: Error loading 'crypt32.dll': 1790 [C:\Windows\system32\crypt32.dll]
1ac0.1d04: supR3HardenedWinDoReSpawn(2): Quitting: ExitCode=0x1 rcNt=0x0
1e78.1124: supR3HardenedWinDoReSpawn(1): Quitting: ExitCode=0x1 rcNt=0x0

Something changed in the host that is preventing the guest to start properly, probably a Windows update. Can you use the system restore to put it back in time to a point when it did work?
This is assuming that you have not updated VBox in that time frame.

[socratis]

Well, if the VBoxStartup.log is current (timestamp 2014.12.11-11.09) then it shows some signs of problems. From the log:

a60.1a70: supR3HardenedScreenImage/LdrLoadDll: cached rc=Unknown Status -22900 (0xffffa68c) fImage=1 fProtect=0x0 fAccess=0x0 cErrorHits=2 \Device\HarddiskVolume2\Windows\System32\crypt32.dll
a60.1a70: Error (rc=0):
a60.1a70: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Windows\system32\crypt32.dll': rcNt=0xc0000190
a60.1a70: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0xc0000190 'C:\Windows\system32\crypt32.dll'
a60.1a70: Fatal error:
a60.1a70: Error loading 'crypt32.dll': 1790 [C:\Windows\system32\crypt32.dll]

But I'm not sure if that's a correct log file or not. As I said, revert to 4.3.12 until this is fixed, because my gut feeling is that this is due to the security hardening after 4.3.12.

[MilacronITDoug]

Thank you for your help, i downgraded his install, reloaded the .VDI, and everything loaded like normal.
not certain why his pc is the only one having this issue, since we have been using the same version on all of our installs, but it is working none the less.
I greatly Appreciate the advice!!

[Martin]

Looks like this PC was hit by the Windows Update bug which destroyed the Windows file signature database.
Until you can fix this Windows problem you cannot run a Virtualbox newer than 4.3.12 on this PC.