VirtualBox

Opened 8 years ago

Closed 7 years ago

#15609 closed defect (worksforme)

VirtualBox 5.1.0-108711 Installation + Windows 10x64 & Skylake = BSOD 0x00000124

Reported by: palarnik Owned by:
Component: installer Version: VirtualBox 5.1.0
Keywords: Cc:
Guest type: other Host type: other

Description (last modified by Frank Mehnert)

Microsoft (R) Windows Debugger Version 10.0.10586.567 AMD64 Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\071416-6250-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 10586.306.amd64fre.th2_release_sec.160422-1850
Machine Name:
Kernel base = 0xfffff801`c2008000 PsLoadedModuleList = 0xfffff801`c22e6cd0
Debug session time: Thu Jul 14 06:44:56.182 2016 (UTC + 6:00)
System Uptime: 1 days 19:30:53.808
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, ffffe001bba64028, be000000, 1001136}

Probably caused by : GenuineIntel

Followup:     MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffe001bba64028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000001001136, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10586.306.amd64fre.th2_release_sec.160422-1850

SYSTEM_MANUFACTURER:  Gigabyte Technology Co., Ltd.

SYSTEM_PRODUCT_NAME:  To be filled by O.E.M.

SYSTEM_SKU:  To be filled by O.E.M.

SYSTEM_VERSION:  To be filled by O.E.M.

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  F4

BIOS_DATE:  03/16/2016

BASEBOARD_MANUFACTURER:  Gigabyte Technology Co., Ltd.

BASEBOARD_PRODUCT:  H110M-S2H-CF

BASEBOARD_VERSION:  x.x

DUMP_TYPE:  2

DUMP_FILE_ATTRIBUTES: 0xc
  Insufficient Dumpfile Size
  Kernel Generated Triage Dump

BUGCHECK_P1: 0

BUGCHECK_P2: ffffe001bba64028

BUGCHECK_P3: be000000

BUGCHECK_P4: 1001136

BUGCHECK_STR:  0x124_GenuineIntel

CPU_COUNT: 4

CPU_MHZ: e70

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CPU_MICROCODE: 6,5e,3,0 (F,M,S,R)  SIG: 74'00000000 (cache) 74'00000000 (init)

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  msiexec.exe

CURRENT_IRQL:  f

ANALYSIS_SESSION_HOST:  DESKTOP-C4S3A5F

ANALYSIS_SESSION_TIME:  07-14-2016 07:22:07.0901

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

STACK_TEXT:  
fffff801`c3ca2a38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx


STACK_COMMAND:  kb

THREAD_SHA1_HASH_MOD_FUNC:  81a83ae0317433a47fcc36991983df3b6e638b71

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  6e16edd8c7dd677734fdbcd2397a2e35e9fae964

THREAD_SHA1_HASH_MOD:  76cd06466d098060a9eb26e5fd2a25cb1f3fe0a3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  

FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE

PRIMARY_PROBLEM_CLASS:  0x124_GenuineIntel_PROCESSOR_CACHE

TARGET_TIME:  2016-07-14T00:44:56.000Z

OSBUILD:  10586

OSSERVICEPACK:  0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2016-04-23 10:04:21

BUILDDATESTAMP_STR:  160422-1850

BUILDLAB_STR:  th2_release_sec

BUILDOSVER_STR:  10.0.10586.306.amd64fre.th2_release_sec.160422-1850

ANALYSIS_SESSION_ELAPSED_TIME: 30d

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x124_genuineintel_processor_cache

FAILURE_ID_HASH:  {4c8f3f5e-1af5-ed8b-df14-d42663b1dfa7}

Followup:     MachineOwner
---------

It looks like it https://www.virtualbox.org/ticket/15542

Attachments (3)

071416-6250-01.dmp (136.7 KB ) - added by palarnik 8 years ago.
071416-6343-01.dmp (158.9 KB ) - added by palarnik 8 years ago.
VBoxInstallLog.txt (438.9 KB ) - added by palarnik 8 years ago.
Full install log ends with bsod

Download all attachments as: .zip

Change History (11)

by palarnik, 8 years ago

Attachment: 071416-6250-01.dmp added

by palarnik, 8 years ago

Attachment: 071416-6343-01.dmp added

comment:1 by palarnik, 8 years ago

And dump from 5.0.4-102546

by palarnik, 8 years ago

Attachment: VBoxInstallLog.txt added

Full install log ends with bsod

comment:2 by Frank Mehnert, 8 years ago

Description: modified (diff)

comment:3 by Frank Mehnert, 8 years ago

Which VirtualBox versions are these dumps taken from?

in reply to:  3 comment:4 by palarnik, 8 years ago

Replying to frank:

Which VirtualBox versions are these dumps taken from?

071416-6250-01.dmp -> 5.1.0-108711, 071416-6343-01.dmp -> 5.0.4-102546

comment:5 by palarnik, 8 years ago

Actually 071416-6343-01.dmp it 5.0.4-102546 installation (if I remember it right) without usb support, networking and python support, just want to see will be different. And there is a difference, the installation is completed, and I had to click "Finish" but then again BSOD. I getting bsod with no matter from version virtualbox, it crashes on VirtualBox 4.3.32 too.

comment:6 by palarnik, 8 years ago

I think this is a problem Windows 10, 02.08.2016 goes Anniversary Update. I do a clean install and see what will happen with the latest version VirtualBox.

comment:7 by palarnik, 8 years ago

Clean install fix the problem,ticket can be closed. Thanks you for your patience.

comment:8 by Frank Mehnert, 7 years ago

Resolution: worksforme
Status: newclosed

Thanks for the information.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use