VirtualBox

Opened 14 years ago

Closed 14 years ago

#5421 closed defect (fixed)

Bluescreen on Windows 7 64Bit when resuming from standby -> fixed in SVN

Reported by: Eckhard Schwabe Owned by:
Component: other Version: VirtualBox 3.0.10
Keywords: Cc:
Guest type: other Host type: other

Description

Hot is: Windows 7 Ultimate 64bit VirtualBox Version: 3.0.10 Windows XP Home as Guest going into Standby, then resuming the host gives a Bluescreen:

KMODE_EXCEPTION_NOT_HANDLED (1e)

Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffffa80086b832a, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: ffffffffffffffff, Parameter 1 of the exception

FAULTING_IP: +0 fffffa80`086b832a f30fc73424 vmxon qword ptr [rsp] EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: ffffffffffffffff READ_ADDRESS: ffffffffffffffff DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x1E PROCESS_NAME: VirtualBox.exe CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff80002d0ea17 to fffff80002ccef00

Attachments (2)

110709-24148-01.dmp (268.6 KB ) - added by Eckhard Schwabe 14 years ago.
Minidump
VBox.log (46.1 KB ) - added by Eckhard Schwabe 14 years ago.
Virtual Box log

Download all attachments as: .zip

Change History (8)

by Eckhard Schwabe, 14 years ago

Attachment: 110709-24148-01.dmp added

Minidump

by Eckhard Schwabe, 14 years ago

Attachment: VBox.log added

Virtual Box log

comment:1 by schmettow, 14 years ago

Similar problem here on a WinXP host with Ubuntu Karmic as a guest (both 32 bit) in Virtualbox 3.0.10. Can be reproduced by:

1) Starting guest machine

2) Pausing guest machine (don't know whether this is required to reproduce)

3) Hibernating host (to disk)

4) Resuming host

5) Resuming guest

6) --> Blue Screen and reboot of host

Not sure whether this problem occurred after upgrading to 3.0.8 or 3.0.10, but it wasn't there with earlier versions of VB.

comment:2 by Sander van Leeuwen, 14 years ago

Unable to reproduce here. I suspect the BIOS is not enabling VT-x properly after resume or hibernate. (which is a bug in the BIOS) Could you try to find if a newer BIOS version fixes the problem?

You can override the VT-x initialization by defining a global enviroment variable:

  • set VBOX_HWVIRTEX_INIT=global

I'll add some additional code to reinit VT-x in the next version.

comment:3 by Sander van Leeuwen, 14 years ago

Could you both also tell me on which machines this occurs? (brand, model, bios revision) Thanks.

comment:4 by Sander van Leeuwen, 14 years ago

Summary: Bluescreen on Windows 7 64Bit when resuming from standbyBluescreen on Windows 7 64Bit when resuming from standby -> fixed in SVN

Fix will appear in the next version. The above workaround should do the trick as well.

comment:5 by Eckhard Schwabe, 14 years ago

  • For now I disabled VT in the VirtualBox Settings
  • Brand Name: Home build with:

Mainboard Intel DP55KG, Bios 3822 (there is a newer one, I will try this)

comment:6 by Frank Mehnert, 14 years ago

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use