random BSOD on Win7 x64

[theetete]

Got several random BSOD on my WIN7 Dell Laptop while having Vbox running.

[amedvedev]

The dumps that you sent doesn't point directly to VirtualBox. So could you run memtest86 to exclude hardware problem at first? Also the collected dumps doesn't contain enough valuable information. Could you collect a full kernel memory dump for us as defined here - ​https://support.microsoft.com/en-us/kb/969028 ?

[theetete]

Hi, I was thinking of VB because of these lines :

FAULTING_IP: 
VMMR0+9633
fffff880`0e82a633 4b8784fe68030000 xchg    rax,qword ptr [r14+r15*8+368h]
MM_INTERNAL_CODE:  7
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  VirtualBox.exe
CURRENT_IRQL:  0

0: kd> lmvm VMMR0
start             end                 module name
fffff880`0e821000 fffff880`0e947000   VMMR0    T (no symbols)           
    Loaded symbol image file: VMMR0.r0
    Image path: \??\C:\Program Files\Oracle\VirtualBox\VMMR0.r0
    Image name: VMMR0.r0
    Timestamp:        Tue Jan 19 17:40:45 2016 (569E670D)
    CheckSum:         0012BDDC
    ImageSize:        00126000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

I don't have the full dump anymore, I will try to upload one later if it happens again. All memtest tests passed.

[amedvedev]

Maybe you see other dump? If you have other dumps, please, attach them here. In the "03116-6208001.dmp" the faulting address is in ntkrnl.exe. In the "031116-11232-01.dmp" the faulting address doesn't belong to any module and a stack of backtrace is broken. Also it could be useful if you attach VirtualBox and VM logs too.