Windows 7 XP Mode and Vbox Blue Screens

[NoMiNaL eKrAsH]

I cannot use VBOX with Microsoft's VM implementation and it keeps causing Blue Screens immediately upon launch of a Microsoft VM. For the time being I only use VBOX for BOINC's Test4Theory project and I already have my XP and Server 2003 VM's which run just fine on their own. But if VBOX is already running and I start XP or 2K3 server VM's it crashes VBOX then results in a blue screen when trying to restart VBOX. They used to run together for the most fairly stable as I can recall. Recently they have been failing to run together.

[NoMiNaL eKrAsH]

vbox log

[NoMiNaL eKrAsH]

After running XP and 2K3 vm's the mouse integration disappea5rs behind the desktop and I have no control whatsoever in the VM. The right control key started toggling the mouse integration icon on and off instead of releasing the mouse...and I had to hit the reset button because the mouse would not release from the VM window it became stuck in. It seems after switching to resizeable view these problems started.

Shouldn't oracle attach directly to Microsofts XP-Mode libraries and files for integration features if they are present in Win7 Hosts, because these mouse integration problems don't exist in microsoft's implementation, but I can't use XP-mode anymore because its causing a blue screen when I try to start VBOX.

[Perryg]

You can't run two hardware-V aware virtualizers at the same time. If you could you run the risk of corruption as one would not know what the other was doing.

[BriGuy2020]

I also have the same issue. Consider the following scenario:

1. I am running XP Mode.
   
2. I launch a VirtualBox machine.
   
3. Windows 7 gives me a Blue Screen:

   SYSTEM_SERVICE_EXCEPTION
   STOP: 0X0000003B
   

I think VirtualBox or XP Mode/Virtual PC should check for running instances of other brand virtualizers/VMs before causing an exception in Windows.