VirtualBox

Ticket #493 (closed defect: fixed)

Opened 7 years ago

Last modified 4 years ago

Disabled AMD SVM crashes host -> fixed in 1.4.2/SVN

Reported by: gmueller Owned by:
Priority: critical Component: other
Version: VirtualBox 1.4.0 Keywords: Bluescreen
Cc: Guest type: other
Host type: other

Description

When starting a virtualmachine, even a new one (just created) I get a bluescreen. System is Windows XP Prof (32bit) on AMD 64 X2 Dual, Core Processor 4600+, 1,87 GB RAM ATI Radeon 1150 on Board

Bluescreen show only:

BugCheck 1000008E, {c0000005, 88b6303b, af35acd4, 0}

WinDbg gives following information:

0: kd> !analyze -v *

  • *
  • Bugcheck Analysis *
  • *

*

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: c0000005, The exception code that was not handled Arg2: 88b6303b, The address that the exception occurred at Arg3: af35acd4, Trap Frame Arg4: 00000000

Debugging Details:


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in "0x%08lx" verweist auf Speicher in "0x%08lx". Der Vorgang "%s" konnte nicht auf dem Speicher durchgef hrt werden.

FAULTING_IP: +ffffffff88b6303b 88b6303b 0f30 wrmsr

TRAP_FRAME: af35acd4 -- (.trap 0xffffffffaf35acd4) ErrCode = 00000000 eax=00001800 ebx=00200046 ecx=c0000080 edx=00000000 esi=88b99000 edi=00000000 eip=88b6303b esp=af35ad48 ebp=af35ad50 iopl=0 nv up di ng nz ac pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210096 88b6303b 0f30 wrmsr Resetting default scope

CUSTOMER_CRASH_COUNT: 6

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: VirtualBox.exe

LAST_CONTROL_TRANSFER: from 88b633aa to 88b6303b

STACK_TEXT: WARNING: Frame IP not in any known module. Following frames may be wrong. af35ad50 88b633aa c0000080 00001800 00000000 0x88b6303b af35ad94 88b603ce c0000080 64726962 88b60530 0x88b633aa af35adac 896b18c3 88b99000 00200097 00010004 0x88b603ce af35adb0 88b99000 00200097 00010004 00000023 0x896b18c3 af35adb4 00200097 00010004 00000023 00000023 0x88b99000 af35adb8 00010004 00000023 00000023 0000003b 0x200097 af35adbc 00000000 00000023 0000003b 0105409c 0x10004

STACK_COMMAND: .trap 0xffffffffaf35acd4 ; kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: BAD_STACK

Followup: MachineOwner


Change History

comment:1 Changed 7 years ago by gmueller

I forgot to say:

In case I get no bluescreen, virtual machine works properly. I can get a bluescreen on a fresh booted windows. Maybe I can start a virtual machine many times without bluescreen. Maybe virual machine crashes at first attempt to start. Crash occurs when changing resolution after first splashscreen with innotek logo.

comment:2 Changed 7 years ago by sandervl73

  • Priority changed from major to critical

comment:3 follow-up: ↓ 4 Changed 7 years ago by sandervl73

I've just fixed this problem. If you wish to try a new build, then let me know. Thanks for reporting it.

comment:4 in reply to: ↑ 3 Changed 7 years ago by gmueller

Replying to sandervl73:

I've just fixed this problem. If you wish to try a new build, then let me know. Thanks for reporting it.

Where can I get a new build? I want to try out.

comment:5 follow-up: ↓ 6 Changed 7 years ago by sandervl73

You can go to the BIOS and turn on hardware virtualization (AMD-V or SVM). That should work as a temporary workaround.

comment:6 in reply to: ↑ 5 Changed 7 years ago by gmueller

Replying to sandervl73:

You can go to the BIOS and turn on hardware virtualization (AMD-V or SVM). That should work as a temporary workaround.

Sorry, don't know where to tune! Hardware is HP Compaq dc5750 MT, ATI-BIOS-Version is 008.050.065.000, ATI Radeon Xpress 1150 Series, driver version 8.261.4-060722a-035058C-HP.

comment:7 follow-up: ↓ 8 Changed 7 years ago by sandervl73

Reboot your system and go to the BIOS settings. Then there must be some CPU page with a setting for virtualization. I can give you a new version, but it's easier if you just use the workaround.

comment:8 in reply to: ↑ 7 Changed 7 years ago by gmueller

Replying to sandervl73:

Reboot your system and go to the BIOS settings. Then there must be some CPU page with a setting for virtualization. I can give you a new version, but it's easier if you just use the workaround.

Thanks, it's working now, I have found the "dip-switch". It was hard to find under menu item "Security->OS Security->Virtualization Technology Enable"! HELP: No Help available for this feature:-(HP-Bios is always strange.)

comment:9 Changed 7 years ago by sandervl73

  • Summary changed from Virtualbox crashes randomly giving bluescreen to Disabled AMD SVM crashes host -> fixed in 1.4.2

comment:10 Changed 7 years ago by sandervl73

  • Summary changed from Disabled AMD SVM crashes host -> fixed in 1.4.2 to Disabled AMD SVM crashes host -> fixed in 1.4.2/SVN

comment:11 Changed 7 years ago by 1979mark

Did anybody know when the new Version 1.4.2/SVN will be launched?

comment:12 Changed 7 years ago by michael

Unless anything unexpected happens, version 1.5.0 will be released in a week or two.

comment:13 Changed 7 years ago by sandervl73

  • Status changed from new to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use