VirtualBox

Opened 17 years ago

Closed 9 years ago

#582 closed defect (obsolete)

Bluescreen with Gigabyte Mainboards (Intel cpu) -> UPDATE your BIOS

Reported by: ihng Owned by:
Component: other Version: VirtualBox 1.4.0
Keywords: bluescreen gigabyte Cc:
Guest type: other Host type: other

Description

Many User in the forum report an error in cooperation with gigabyte mainboards. Wirtualbox seems to generate an error on all gigabyte mainboards. For example, if i want to install windows xp in virtualbox with an asus mainboard it works, but if i use a new mainboard from gigabyte i get bluescreens and can't install windows xp under virtualbox.

Change History (19)

comment:1 by Sander van Leeuwen, 17 years ago

Resolution: duplicate
Status: newclosed

Most likely a bios issue if you have an AMD cpu who's SVM capability is turned off by the BIOS itself. This has already been fixed.

comment:2 by Sander van Leeuwen, 17 years ago

Check ticket 493

comment:3 by ihng, 17 years ago

Resolution: duplicate
Status: closedreopened

i'm using an intel core 2 duo 6850 on the gigabyte p35-dq6 - no amd cpu and no svm?!

comment:4 by Sander van Leeuwen, 17 years ago

Which host OS are you using? Blue screen implies Windows, but I'd like to be sure. When do you get this blue screen? Right at the beginning, later on during install? Can you run any other guests (e.g. Linux)?

The gigabyte reports I've seen so far are all with AMD cpus.

comment:5 by Sander van Leeuwen, 17 years ago

priority: majorcritical

comment:6 by Sander van Leeuwen, 17 years ago

Summary: Bluescreen with Gigabyte MainboardsBluescreen with Gigabyte Mainboards (Intel cpu)

comment:7 by ihng, 17 years ago

host is windows xp professional sp2 ...if i want to install windows xp in virtualbox i get the bluescreen ...if start the installation once more and once more and once more...it is possible but not sure that i come to the end ...this costs a lot of time and then the bluescreen comes if i want to start windows xp in virtualbox.

the error message: STOP: 0x0000007F (0x00000000, 0x00000000, 0x00000000, 0x00000000)

the same hardware on an asus mainboard works, get the error since i have this new gigabyte board.

comment:8 by Sander van Leeuwen, 17 years ago

Are you able to turn off VMX/hardware virtualization in the gigabyte bios? If so, try it.

comment:9 by Sander van Leeuwen, 17 years ago

Also, does your system crash the second you try to launch a VM or after some time only?

comment:10 by ihng, 17 years ago

disable vmm in bios = same problem

system crashs different times within windows installation and if i have a lot of time and do it till the installation is complete i get the error if i want to start the vm!

comment:11 by Sander van Leeuwen, 17 years ago

That's really strange. Have you tried turning off network, audio and usb for the VM? Maybe there's a host driver in your system that blows up.

comment:12 by ihng, 17 years ago

updating today from bios.F4 to the new bios.F5 and it works :)

comment:13 by Sander van Leeuwen, 17 years ago

Summary: Bluescreen with Gigabyte Mainboards (Intel cpu)Bluescreen with Gigabyte Mainboards (Intel cpu) -> UPDATE your BIOS

comment:14 by Sander van Leeuwen, 17 years ago

priority: criticalmajor

comment:15 by asrita, 16 years ago

I see the same error with XP host on Dell laptop when starting a VM. Error message: STOP: 0x0000007F (0x00000000, 0x00000000, 0x00000000, 0x00000000)

After several retries, the guest OS (Windows 2003 server) boots and works normally. I had the same issue even when installing the guest. But, there is no guarantee how long or if ever the guest will boot if I shut it down. Any resolution or work around?

comment:16 by asrita, 16 years ago

Forgot to mention that I'm using version 1.6

comment:17 by Sander van Leeuwen, 16 years ago

Try again with 1.6.2.

comment:18 by Alexei Zakharov, 16 years ago

I also experience a blue-screen issue with my new Gigabyte motherboard (ga-ex38-dq6). I have Vista Home Basic (32bit) as host and Debian (etch) as guest. Everything runs fine until I put system to sleep with running (or paused) VirtualBox session. After resuming it shows blue screen after I try to touch anything in VirtualBox. However, it looks like the bug disappears if I disable hardware virtualization in VirtualBox's settings. Upgrading to the most recent BIOS version does not help. I use version 1.6.2.

comment:19 by Frank Mehnert, 9 years ago

Resolution: obsolete
Status: reopenedclosed
Note: See TracTickets for help on using tickets.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette