WinXP SP3 and blue screen of death

IUnknown · Post by **IUnknown** » 6. Jul 2008, 15:03

I use Ubuntu 8.04 amd64 + VirtualBox 1.6.2. I installed fresh version of Windows XP SP3 and it works fine. But every time for some reasons (I do not know why) I see "blue screen of death" (I can't read text because It appears for a short time) and my virtual machine reboots. Can you help me with this problem? Thanks.
P.S. For WinXP_SP2 the same problem.

Post by **TerryE** » 6. Jul 2008, 15:51

Search the XP forums. There's a registry setting which prevents automatic restart. Also settable through System Propreties->Startup and Recovery.

Can you boot in Safe Mode?

IUnknown · Post by **IUnknown** » 6. Jul 2008, 16:08

I disabled auto reboot and now I am waiting the BSOD.

Post by **stefan.becker** » 6. Jul 2008, 16:23

If Problems still exists:

Give Infos. Tell the exact and complete Guest Settings (ACPI, APIC, VT etc).

IUnknown · Post by **IUnknown** » 13. Jul 2008, 00:08

My BSOD

IUnknown · Post by **IUnknown** » 13. Jul 2008, 07:22

My settings:
ACPI - enabled
IO APIC - disabled
VT-x/AMD-V - disabled
PAE/NX - disabled
IDE controller type - PIIX4
Hard disk - enabled IDE
CD/DVD-ROM - enabled
Floppy - disabled
Audio - disabled
Network - enabled NAT
Serial port - disabled
USB/USB2.0 - enabled
Share folders - added one
Remote display - disabled

Post by **TerryE** » 13. Jul 2008, 13:57

I believe that this is an NT kernel panic caused by a driver going "out of band". Basically, there are strict rules on how long an individual drivers can mask interrupts and lock certain resources within certain constraints. This is so that other drivers can do what they need to do within adequate response limits. This is what "realtime" programming is all about: if a driver needs to respond to a interrupt in 10mSec then 20mSec or even 11mSec isn't good enough. Something has gone wrong. And this could lead to all sorts of subtle problems (such as your HDD being corrupted). Rather than let this happen, the NT kernel pulls the plug and shuts down (the BSOD).

So:

You need to review all of your drivers and resident programmes that can use Ring 0. It is almost certainly an interaction between some.
These can include virus scanners, HDD encryption, usb device drivers, other "systray" applications and services.
I would remove all that are no longer appropriate in a VM.
I would also (temporarily) disable as many others as possible (e.g. your PDA or scanner drivers)
Clearly one of the main "drivers" involved here is the VBox VMM itself. This may have timing issues. Which kernel are you using (uname -r)?
Also make sure that you are using the VBox host install and VBox GA at the same version (e.g. 1.6.2 PUEL or Ubuntu 1.5.6 OSE or whatever). Don't mix and match.

So for no straight answers. This is the best that I can suggest.

IUnknown · Post by **IUnknown** » 27. Jul 2008, 11:00

Problem appeared again

. I thought that It was pirate Alcohol100% virtual drive driver, but It was not. VBox host install and VBox GA have the same versions (1.6.2 and 1.6.2.31466). My kernel 2.6.24-19-generic.
I do not know what to do.

vwtimc · Post by **vwtimc** » 31. Jul 2008, 13:12

I get a similar issue with creating new cloned VDI's...

I have an image that works perfectly XP sp2 on and xp sp2 box, (VirtualBox 1.6.2).
1. I shut it down
2. VBoxManage CloneVDI XXX YYY
3. Create a new VM with the cloned VDI attached and I get the same BSOD whilst booting the new machine.

I have currently taken to file copying the VDI and moving the older one to disk.

Cheers

Tim

virtualbox.org

WinXP SP3 and blue screen of death

WinXP SP3 and blue screen of death

BSOD with a cloned image