virtualbox.org

Below is the memory dump from the error after parsing through WinDebug. This error occurs when starting more than one VirtualBox VM...sometimes it is the 2nd VM, sometimes the 3rd but any more than one and down it goes.

Hardware is HP 580 G7 server, 128GB Ram, 1.3TB drive space, multiple nics (HP NC375i and NC382T), Quad Intel Xeon E7-4850's.

Any help would be appreciated.

Code: Select all

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


Loading Dump File [C:\Users\stuadda\Desktop\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                      
Executable search path is: 
Windows 8 Kernel Version 9600 MP (80 procs) Free x64
Product: Server, suite: TerminalServer SingleUserTS
Built by: 9600.17736.amd64fre.winblue_r9.150322-1500
Machine Name:
Kernel base = 0xfffff803`6a085000 PsLoadedModuleList = 0xfffff803`6a35e850
Debug session time: Tue Jun 30 10:10:53.508 2015 (UTC - 4:00)
System Uptime: 0 days 1:23:00.009
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00007ff6`9e46f018).  Type ".hh dbgerr001" for details
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c000001d, fffff8013088d57c, ffffd00028f34e20, 0}

*** ERROR: Symbol file could not be found.  Defaulted to export symbols for VMMR0.r0 - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for VBoxDrv.sys - 
Probably caused by : VMMR0.r0 ( VMMR0!VMXR0Enter+c )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c000001d, Exception code that caused the bugcheck
Arg2: fffff8013088d57c, Address of the instruction which caused the bugcheck
Arg3: ffffd00028f34e20, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

FAULTING_IP: 
VMMR0!VMXR0Enter+c
fffff801`3088d57c 0fc7742410      vmptrld qword ptr [rsp+10h]

CONTEXT:  ffffd00028f34e20 -- (.cxr 0xffffd00028f34e20;r)
rax=00000000bee3c000 rbx=fffff8013096b380 rcx=ffffd0002b207000
rdx=ffffd0002b222000 rsi=ffffd0002b207000 rdi=ffffd0002b222000
rip=fffff8013088d57c rsp=ffffd00028f35858 rbp=ffffd00028f35c00
 r8=fffff8013096b380  r9=ffffd0002b207000 r10=ffff800000000000
r11=fffff8036a1e1470 r12=0000000000000003 r13=0000000000228307
r14=ffffe000eea1c1a0 r15=0000000000228307
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
VMMR0!VMXR0Enter+0xc:
fffff801`3088d57c 0fc7742410      vmptrld qword ptr [rsp+10h] ss:0018:ffffd000`28f35868=00000000bee3c000
Last set context:
rax=00000000bee3c000 rbx=fffff8013096b380 rcx=ffffd0002b207000
rdx=ffffd0002b222000 rsi=ffffd0002b207000 rdi=ffffd0002b222000
rip=fffff8013088d57c rsp=ffffd00028f35858 rbp=ffffd00028f35c00
 r8=fffff8013096b380  r9=ffffd0002b207000 r10=ffff800000000000
r11=fffff8036a1e1470 r12=0000000000000003 r13=0000000000228307
r14=ffffe000eea1c1a0 r15=0000000000228307
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
VMMR0!VMXR0Enter+0xc:
fffff801`3088d57c 0fc7742410      vmptrld qword ptr [rsp+10h] ss:0018:ffffd000`28f35868=00000000bee3c000
Resetting default scope

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  VirtualBox.exe

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

LAST_CONTROL_TRANSFER:  from fffff80130885250 to fffff8013088d57c

STACK_TEXT:  
ffffd000`28f35858 fffff801`30885250 : ffffd000`2b222000 00000000`bee3c000 00000487`9ccc98be ffffe400`53fec830 : VMMR0!VMXR0Enter+0xc
ffffd000`28f35860 fffff801`30899ef3 : ffffd000`2b222000 00000000`00000000 00000000`00000000 00000000`00000080 : VMMR0!GVMMR0CreateVMReq+0xe00
ffffd000`28f35890 fffff801`2d0ec70f : 00000000`ffffffff 00000000`000007b4 ffffe400`53fec830 0000001e`0012019f : VMMR0!VMMR0EntryFast+0xf3
ffffd000`28f358f0 fffff801`2d0fb45b : ffffe000`ed0ec900 ffffd000`28f35cc0 00000000`00000000 ffffe000`ed0a8b38 : VBoxDrv+0x170f
ffffd000`28f35920 fffff803`6a4aa27c : ffffe000`eea1c050 00000000`00000000 00000000`00000000 fffff803`00000000 : VBoxDrv!SUPR0GetKernelFeatures+0x230b
ffffd000`28f359c0 fffff803`6a4a9d22 : 00000000`fffffb83 00007ffd`a3bd0000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x54c
ffffd000`28f35b60 fffff803`6a1e14b3 : 00000000`00000000 00000000`033ab000 ffffe000`ec605c00 ffffd000`28f35cc0 : nt!NtDeviceIoControlFile+0x56
ffffd000`28f35bd0 00007ffd`b818123a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0509f568 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`b818123a


FOLLOWUP_IP: 
VMMR0!VMXR0Enter+c
fffff801`3088d57c 0fc7742410      vmptrld qword ptr [rsp+10h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  VMMR0!VMXR0Enter+c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: VMMR0

IMAGE_NAME:  VMMR0.r0

DEBUG_FLR_IMAGE_TIMESTAMP:  55070694

STACK_COMMAND:  .cxr 0xffffd00028f34e20 ; kb

BUCKET_ID_FUNC_OFFSET:  c

FAILURE_BUCKET_ID:  0x3B_VMMR0!VMXR0Enter

BUCKET_ID:  0x3B_VMMR0!VMXR0Enter

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x3b_vmmr0!vmxr0enter

FAILURE_ID_HASH:  {545b206b-b31b-98cb-02a0-6bcbb5a4472b}

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

While I can't answer on what went wrong exactly, could you confirm you don't have Hyper-V installed on that server, or any other virtualization software or programs like Android/Windows Phone SDK or invasive antivirus/attack prevention program?

noteirak wrote:While I can't answer on what went wrong exactly, could you confirm you don't have Hyper-V installed on that server, or any other virtualization software or programs like Android/Windows Phone SDK or invasive antivirus/attack prevention program?

No Hyper-V installed, no invasive antivirus at all right now. It's an isolated system,

virtualbox.org

BSOD on Windows 2012 Server w/ multiple VM's starting

BSOD on Windows 2012 Server w/ multiple VM's starting

Re: BSOD on Windows 2012 Server w/ multiple VM's starting

Re: BSOD on Windows 2012 Server w/ multiple VM's starting