System crashed when start guest

[shtents]

Hello,
Host: Windows 7 64bit sp1
Hardware: Sony vgn-z21vrn
Antivirus: Microsoft Security Essentials + Windows Firewall
VirtualBox: 4.3 and 5 both has problem
Guest: Any
Logfile from VirtualBox is empty.

Then try to start VM receive BSOD and reboot.
Windows Host MiniDump analisis below.

Any ideas?
Thanks!



Crash Dump Analysis provided by OSR Open Systems Resources, Inc. ()
Online Crash Dump Analysis Service
See for more information
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.19045.amd64fre.win7sp1_gdr.151019-1254
Machine Name:
Kernel base = 0xfffff800`02c58000 PsLoadedModuleList = 0xfffff800`02e9f730
Debug session time: Sun Jan 10 15:54:51.077 2016 (UTC - 5:00)
System Uptime: 0 days 0:01:54.560
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

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

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
nt!RtlImageNtHeaderEx+3f
fffff800`02cac5af 66390a cmp word ptr [rdx],cx

CONTEXT: fffff8800ad5bd20 -- (.cxr 0xfffff8800ad5bd20)
rax=0000000000000100 rbx=fffff88003a44a98 rcx=0000000000005a4d
rdx=0000000060000000 rsi=0000000000000000 rdi=fffff8a0002ad950
rip=fffff80002cac5af rsp=fffff8800ad5c708 rbp=fffff80002e80bb8
r8=0000000000000000 r9=fffff8800ad5c748 r10=0000000000000000
r11=0000000000000000 r12=0000000060000000 r13=fffff8800ad5c998
r14=0000000000000e90 r15=fffffa80059de6f8
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
nt!RtlImageNtHeaderEx+0x3f:
fffff800`02cac5af 66390a cmp word ptr [rdx],cx ds00000000`60000000=????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: VirtualBox.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80002cac5af

STACK_TEXT:
fffff880`0ad5c708 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!RtlImageNtHeaderEx+0x3f


FOLLOWUP_IP:
nt!RtlImageNtHeaderEx+3f
fffff800`02cac5af 66390a cmp word ptr [rdx],cx

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!RtlImageNtHeaderEx+3f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 5625815c

STACK_COMMAND: .cxr 0xfffff8800ad5bd20 ; kb

FAILURE_BUCKET_ID: X64_0x3B_nt!RtlImageNtHeaderEx+3f

BUCKET_ID: X64_0x3B_nt!RtlImageNtHeaderEx+3f

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

[mpack]

VirtualBox: 4.3 and 5 both has problem

There has never been a VirtualBox 4.3, or a VirtualBox 5. Please be precise about version numbers. I also doubt that log can be empty.

Please pick one guest and post a VM log file. With the VM fully shut down, right click it in GUI. Select "Show Log" and save "VBox.log" (ONLY) to a zip file. Include the file "VBoxHardening.log" in the zip. Attach the zip here.

[shtents]

5.0.12
and
4.3.34
Is it correct ?

VBoxHardening is empty.
VBox is empty.

[shtents]

I found this log with some errors.

[shtents]

And log from 5.0.12 version

VirtualBox COM Server 5.0.12 r104815 win.amd64 (Dec 18 2015 16:07:28) release log
00:00:00.000000 main Log opened 2016-01-11T08:50:00.127697200Z
00:00:00.000000 main Build Type: release
00:00:00.000000 main OS Product: Windows 7
00:00:00.000000 main OS Release: 6.1.7601
00:00:00.000000 main OS Service Pack: 1
00:00:00.078000 main DMI Product Name: VGN-Z21VRN_X
00:00:00.093600 main DMI Product Version: RP
00:00:00.093600 main Host RAM: 4026MB total, 2574MB available
00:00:00.093600 main Executable: C:\Program Files\Oracle\VirtualBox\VBoxSVC.exe
00:00:00.093600 main Process ID: 2496
00:00:00.093600 main Package type: WINDOWS_64BITS_GENERIC
00:00:00.093600 Home directory: 'C:\Users\shtents/.VirtualBox'
00:00:00.093600 Loading settings file "C:\Users\shtents/.VirtualBox\VirtualBox.xml" with version "1.12-windows"
00:00:00.421200 usbLibDevCfgDrGet: DeviceIoControl 1 fail winEr (31)
00:00:00.842401 HostDnsMonitor: old information
00:00:00.842401 no server entries
00:00:00.842401 no search string entries
00:00:00.842401 no domain set
00:00:00.842401 HostDnsMonitor: new information
00:00:00.842401 server 1: 77.88.8.8
00:00:00.842401 server 2: 8.8.8.8
00:00:00.842401 no search string entries
00:00:00.842401 no domain set
00:00:00.842401 HostDnsMonitorProxy::notify
00:00:00.920401 SUPR0QueryVTCaps -> VERR_VMX_MSR_ALL_VMX_DISABLED
00:00:00.920401 VD: VDInit finished
00:00:00.920401 Loading settings file "D:\VirtualBoxes\Mint17\Mint17.vbox" with version "1.15-windows"
00:00:00.982801 Loading settings file "D:\VirtualBoxes\test\test.vbox" with version "1.15-windows"
00:00:01.372802 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Unknown exception
00:00:01.372802 F:\tinderbox\win-5.0\out\win.amd64\release\obj\VBoxAPIWrap\MediumWrap.cpp[2245] (long __cdecl MediumWrap::GetEncryptionSettings(unsigned short **,unsigned short **))}, preserve=false aResultDetail=0
00:00:01.388402 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Unknown exception
00:00:01.388402 F:\tinderbox\win-5.0\out\win.amd64\release\obj\VBoxAPIWrap\MediumWrap.cpp[2245] (long __cdecl MediumWrap::GetEncryptionSettings(unsigned short **,unsigned short **))}, preserve=false aResultDetail=0

[mpack]

I'm afraid that without logs there is basically nothing I can tell you about this problem. I'm not even convinced that it's a VirtualBox problem - it looks like a buggy host driver crashing, so if I was you I'd check the system event monitor etc looking for clues.