Virtual Box Error - Can not access the Kernel driver

Posted on 2011-10-11
Last Modified: 2012-05-12
I have Win 7 Ultimate 64 bit OS, Installed Virtual Box version 4.1.4 ... During the Restart, I got Blue-Screen error, due to Network Driver issue, I booted with "Last known good configuration" option and booted.

Then I installed Windows XP 32 bit on VM , the installation went smoothly. But when I tried to start the VM, I am getting the following error.

Failed to open a session for the virtual machine Windows XP 32 Bit.

The virtual machine 'Windows XP 32 Bit' has terminated unexpectedly during startup.

Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {5eaa9319-62fc-4b0a-843c-0cb1940f8a91}

Any help would be much appreciated..
Question by:manu4u
    LVL 5

    Expert Comment

    by:Prashant Shrivastava
    If you have received Blue screen then it won't work anyway. I suggest you to to perform clean boot using the instructions below then remove virtual box and reinstall correct Virtualbox for your machine and try again. (I hope you are suing correct version -VirtualBox 4.1.4 for Windows hosts x86/amd64)

    LVL 7

    Author Comment

    Thanks for the reply Prasanth.

    I am using the correct version of virtual box and I had tried all those you mentioned ....  And to my surprise, last week, I had the same issue with another Laptop and somehow I got it worked perfectly , although the Blue screen came and I ignored the error ....
    LVL 5

    Expert Comment

    by:Prashant Shrivastava
    Have you tried running disk check on your host machine? looks like there is something wrong in there ten. it runs fine if all your drivers are correct.
    LVL 7

    Accepted Solution

    It wasn't any disk check issue. Some Virtual box bug causes it.

    The issue I found out was, I had restarted my machine after installing Virtual box application, it screwed up the Network driver and caused BSOD.

    So, what I did was, I installed Virtual Box, then without restart, I completed my XP Virtual Machine in it and then did a reboot., during the reboot, I selected "Last known good configuration" option and voila, I got the machine back up and running ...  Although this is just a lame way I solved the issue, it served the purpose.
    LVL 7

    Author Closing Comment

    Found the solution myself.

    Featured Post

    Maximize Your Threat Intelligence Reporting

    Reporting is one of the most important and least talked about aspects of a world-class threat intelligence program. Here’s how to do it right.

    Join & Write a Comment

    This is similar to the error described in my previous Article, but with a different source problem and a different solution. When trying to scan and stage the ESXi 6.0 updates using VMware Update Manager, we can get "error code 90"
    Create your own, high-performance VM backup appliance by installing NAKIVO Backup & Replication directly onto a Synology NAS!
    Teach the user how to configure vSphere Replication and how to protect and recover VMs Open vSphere Web Client: Verify vsphere Replication is enabled: Enable vSphere Replication for a virtual machine: Verify replicated VM is created: Recover replica…
    How to install and configure Citrix XenApp 6.5 - Part 1. In this video tutorial we have explained step by step installation of Citrix XenApp 6.5 Server on Windows Server 2008 R2 is explained in this video. We have explained the difference between…

    732 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    18 Experts available now in Live!

    Get 1:1 Help Now