#157 VirtualBOX causes BSOD STOP: 0x0000007F 0x00000008

Henry N.

Running Parallels or VMWare to virtualise a virtual machine doesnt result in crashing.

Trying to boot Windows XP on VirtualBOX at the same time as running COLinux causes it to BSOD the host system (Windows Vista)

Its strange but why does VBox BSOD the system whereas Parallels/VMWare can virtualise fine alongside COLinux..

Install VirtualBox
Install COLinux V8
Run COLinux
Create a new Windows VM In Virtualbox
Attempt to Boot the new VM Into Windows setup.


  • Nobody/Anonymous

    The system doesnt generate a Minidump from this crash even though configured to.

    Error is as follows:

    STOP: 0x0000007F (0x00000008, 0x801B1000, 0x00000000, 0x00000000)

    With no further details

  • Henry N.

    Henry N. - 2009-04-28

    > STOP: 0x0000007F (0x00000008, 0x801B1000, 0x00000000, 0x00000000)

    STOP 0x0000007F : UNEXPECTED_KERNEL_MODE_TRAP (sse [1])
    0x00000008 : Double Fault
    0x801B1000 : I found no references for that value.

    [1] http://support.microsoft.com/kb/137539

  • Nobody/Anonymous

    Double fault
    A double fault occurs when an exception occurs while trying to call the handler for a prior exception. Normally, the two exceptions can be handled serially, however there are several exceptions that cannot be handled serially and in this situation the processor signals a double fault. The two primary causes for this are hardware and kernel stack overflows. Hardware problems are usually related to CPU, RAM, or bus. Kernel stack overflows are almost always caused by faulty kernel-mode drivers.

    I can rule out my CPU/RAM since they are relatively new components.. VMWare/Parallels work alongside COLinux just not VirtualBox. I've stress tested this thing for over 72 hours about 2 weeks back since I installed a new CPU cooler..

    So I'm guessing its the Kernel Stack Overflow?

    Any chance you can attempt to reproduce? My Vista is being a pain, its set to do a full mem dump on BSOD but that crash doesnt generate one.

  • Juergen

    Juergen - 2009-04-29

    Some time ago, a had the same problem with randomly getting a kernel stack overflow. The problem was caused by too many enabled network services on a network interface. I had installed VirtualBox, MS Virtual PC, Norton Internet Security, Cisco VPN Client and MS Network Monitor. All these programs installed a network service. After I disabled 2 or 3 of the network services I was not using at that time, I solved the problem with the kernel stack overflow. You have to disable the services it on every network interface.

    Well, a BSOD can also be caused by the virtualization features of the CPU. If I am running a VM in VBox with Intel-VT enabled and then starting only the Virtual PC application, my computer is crashing with a BSOD. On an older CPU with no Intel-VT I never had this problem. On this older CPU, I never had any problems with running VBox VMs and colinux instances concurrently.

    If you do not get a crash dump, this might be caused by the Data-Execution-Prevention in Windows. If this is also enabled for normal applications and not only for windows services, then you will never get a crash dump. Windows is still writing crash dump information to pagefile.sys but it does not generate a crash dump file on next startup. I had the same problem while getting the kernel stack overflow. After disabling DEP for every application Windows created crash dump files again.

  • Technologov

    Technologov - 2009-04-29

    Here is the original bug report:

    Host crash: vboxdrv crashes, when run in VMX mode, together with coLinux



  • Technologov

    Technologov - 2009-04-29

    I have a similar problem with Windows XP host. (32-bit)
    Minidumps are not getting generated. Even if PAE/NX/DEP technologies are turned off completely.

    Nobody: please use some nickname so we could identify you.
    Nobody: please specify VirtualBox version, and if you use VT-x or not (Hardware Virtualization)
    For me, the crash happens only with Hardware Virtualization enabled.


  • Henry N.

    Henry N. - 2009-04-29
    • summary: VirtualBOX causes BSOD --> VirtualBOX causes BSOD STOP: 0x0000007F 0x00000008
  • Henry N.

    Henry N. - 2009-05-20

    Based on idea by Sander Vanleeuwen (http://www.virtualbox.org/ticket/3724#comment:8), have added a check for running VMX. If CPU is unning in VMX mode, coLinux still aborts the guest system, and no longer will crash the host. It's coded in current devel snapshot from SVN revision 1248.

    Sorry, that we currently don't have support for this mode. I'm locking into Intel manuals to find a solution to run in a cooperative way.


  • Henry N.

    Henry N. - 2009-05-20
    • assigned_to: nobody --> henryn
    • status: open --> open-accepted
  • Henry N.

    Henry N. - 2009-05-20
    • status: open-accepted --> closed-accepted
  • Henry N.

    Henry N. - 2009-05-20

    This artifact has been marked as a duplicate of artifact 1959846 with reason:
    Both results from VMX mode. We will follow it in one Artifact only now.


Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks