Page 1 of 1

Native Win7 bluescreens booting in VBox

Posted: 11. Apr 2011, 04:28
by cumthsc
I followed the instructions for booting a native Win7 installation inside VirtualBox, but when I start the virtual machine, it bluescreens :( . The error codes are:
Stop: 0x0000007B (0xFFFF880009A9928 0XFFFFFFFFC0000034 0X0000000000000000 0X0000000000000000
The machine is a Dell E6410. Any idea what setting I'm missing? Booting on the bare metal still works fine.

TIA.

Re: Native Win7 bluescreens booting in VBox

Posted: 11. Apr 2011, 06:15
by stefan.becker
Post VBOX Version.

The exact and full guest configuration.

And the log file.

And your hardware.

Re: Native Win7 bluescreens booting in VBox

Posted: 11. Apr 2011, 17:34
by cumthsc
VirtualBox-4.0-4.0.4_70112_fedora14-1.x86_64

Host is Fedora 14 (with nVidia proprietary graphics driver). Guest is the original Dell installed Win7.

Log and vmdk files attached. I don't seem to be able to attach the vbox file (even if I change the extension). Hope I have what you need here. Let me know what else.
$ file serenity-Win7-raw-pt.vmdk 
serenity-Win7-raw-pt.vmdk: x86 boot sector; partition 1: ID=0xde, starthead 1, startsector 63, 80262 sectors; partition 2: ID=0x83, starthead 25, startsector 81920, 1536000 sectors; partition 3: ID=0x7, active, starthead 181, startsector 1617920, 270974976 sectors; partition 4: ID=0xf, starthead 254, startsector 272592896, 704180224 sectors, code offset 0xc0, OEM-ID "      ?", Bytes/sector 190, sectors/cluster 124, reserved sectors 191, FATs 6, root entries 185, sectors 64514 (volumes <=32 MB) , Media descriptor 0xf3, sectors/FAT 20644, heads 6, hidden sectors 309755, sectors 2147991229 (volumes > 32 MB) , physical drive 0x7e, dos < 4.0 BootSector (0x0)
Hardware is Dell Latitude E6410, Intel i7.
$ lspci
00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 02)
00:01.0 PCI bridge: Intel Corporation Core Processor PCI Express x16 Root Port (rev 02)
00:19.0 Ethernet controller: Intel Corporation 82577LM Gigabit Network Connection (rev 05)
00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05)
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05)
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 05)
00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 05)
00:1c.2 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 3 (rev 05)
00:1c.3 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 4 (rev 05)
00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a5)
00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller (rev 05)
00:1f.2 RAID bus controller: Intel Corporation Mobile 82801 SATA RAID Controller (rev 05)
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 05)
00:1f.6 Signal processing controller: Intel Corporation 5 Series/3400 Series Chipset Thermal Subsystem (rev 05)
01:00.0 VGA compatible controller: nVidia Corporation GT218 [NVS 3100M] (rev a2)
01:00.1 Audio device: nVidia Corporation High Definition Audio Controller (rev a1)
03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6200 (rev 35)
04:00.0 SD Host controller: Ricoh Co Ltd Device e822 (rev 03)
04:00.4 FireWire (IEEE 1394): Ricoh Co Ltd Device e832 (rev 03)
3f:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 02)
3f:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 02)
3f:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 02)
3f:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 02)
3f:02.2 Host bridge: Intel Corporation Core Processor Reserved (rev 02)
3f:02.3 Host bridge: Intel Corporation Core Processor Reserved (rev 02)

Re: Native Win7 bluescreens booting in VBox

Posted: 11. Apr 2011, 19:51
by stefan.becker
Is 3D enabled in the guest settings? If yes, try without 3D.

Re: Native Win7 bluescreens booting in VBox

Posted: 11. Apr 2011, 21:46
by cumthsc
Booting without 3D acceleration did not solve the problem. But thanks for the suggestion.

What next?

Re: Native Win7 bluescreens booting in VBox

Posted: 12. Apr 2011, 19:28
by stefan.becker
Must it be the native one? Better make an own install in a vdi file.

Else what you can try is to change the disk controller settings (ide (piix3/4, ich6) or sata.

This is mostly the reason that windows does not boot, if installed on another hardware or vm.

Re: Native Win7 bluescreens booting in VBox

Posted: 29. May 2011, 19:42
by cumthsc
Sorry, it's been a while since I've had a chance to play with this.

The disk is on a SATA AHCI controller. There are no options for that that I can change. The physical controller is SATA as well.

The CD is on an IDE controller. I tried PIIX3/4 and ICH6 and nothing had any effect.

Is it safe to delete the SATA disk and recreate it as an IDE one? The HOWTO suggests that performance might be an issue using IDE instead of SATA.

I note when booting in safe mode that the last module loaded was CLASSPNP.SYS, if that tells you anything.

Thanks for your help so far.

Re: Native Win7 bluescreens booting in VBox

Posted: 29. May 2011, 20:46
by cumthsc
Well, I moved the hard disk to the IDE controller and tried all the options. No success, unfortunately.