Page 1 of 1
Host blue screen when starting VM
Posted: 14. Feb 2013, 18:06
by BobDubya
I'm hoping to find a solution to this as it's getting really annoying.
My host PC is running Windows 7 Enterprise SP1 - 64bit
The OS on the guest VM is Windows XP SP3
I'm running Virtualbox 4.2.6
Occasionally upon starting a VM through Virtualbox I'll have the whole host PC go into a blue screen of death. After restarting the PC I can restart the VM with no issues.
Does anybody know why I'm seeing this? I used to run Virtualbox on my old PC (Vista 32-bit) and it was bulletproof.
Thanks,
Bob
Re: Host blue screen when starting VM
Posted: 14. Feb 2013, 18:31
by Perryg
Re: Host blue screen when starting VM
Posted: 14. Feb 2013, 19:29
by BobDubya
Virtualbox v4.2.6 r82870. Guest Additions are installed (v4.2.6)
Host: Windows 7 Enterprise SP1 - 64 Bit - 8GB RAM
Guest: Windows XP Professional SP3 - 32 bit - 192MB RAM
The guest log file was empty, so no help there. It hit BSOD almost instantly after clicking the Start button on the VBox control panel.
Re: Host blue screen when starting VM
Posted: 21. Feb 2013, 11:43
by jdelahayes
Hello,
I'm having the same problem.
I try to downgrade from 4.2.6 to 4.2.4 but I still have the problem.
My configuration :
Virtualbox 4.2.4r81684
Windows 7 pro SP1 64 bits
4Go of RAM
Intel Core i7-2677M 1.80 Ghz (Intel® VT-x with Extended Page Tables (EPT))
Gest OS : Centos 6.2
Windows minidump content :
Code: Select all
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fb40000128, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc0000056, error status (normally i/o status code)
Arg3: 000000004fb90884, current process (virtual address for lock type 3, or PTE)
Arg4: fffff68000025000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
Debugging Details:
------------------
OVERLAPPED_MODULE: Address regions for 'VBoxNetFlt' and 'spsys.sys' overlap
ERROR_CODE: (NTSTATUS) 0xc0000056 - Une op ration autre que "fermer" a t demand e pour un objet fichier en instance de suppression.
BUGCHECK_STR: 0x7a_c0000056
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: SyncBackSE.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff8000334f812 to fffff800032dcc40
STACK_TEXT:
fffff880`03794118 fffff800`0334f812 : 00000000`0000007a fffff6fb`40000128 ffffffff`c0000056 00000000`4fb90884 : nt!KeBugCheckEx
fffff880`03794120 fffff800`03303a0f : fffffa80`0b5cf010 fffff880`03794290 fffffa80`0a4d29b8 fffffa80`0b5cf010 : nt! ?? ::FNODOBFM::`string'+0x36c1a
fffff880`03794200 fffff800`032ea37a : 00000000`00000000 00000000`00000008 ffffffff`ffffffff 00000000`00000000 : nt!MiIssueHardFault+0x28b
fffff880`037942d0 fffff800`032bebfa : 00000000`00000000 fffff680`00025000 80000000`00002000 fffffa80`03d63040 : nt!MmAccessFault+0x146a
fffff880`03794430 fffff800`032f64a4 : fffff680`00025000 fffff6fb`7da00000 fffffa80`0a4d2620 fffffa80`03d63040 : nt!MiMakeSystemAddressValid+0xea
fffff880`03794490 fffff800`032f664b : 00000000`00000080 fffff680`00025df8 00000000`04bba000 00000000`00000000 : nt!MiMakePdeExistAndMakeValid+0x94
fffff880`037944c0 fffff800`035d7d84 : ffffffff`00000000 fffffa80`00000000 fffffa80`0a4d2620 00000000`00000004 : nt!MiCommitExistingVad+0x14b
fffff880`03794560 fffff800`032dbed3 : ffffffff`ffffffff fffff880`03794940 00000000`00000000 fffff880`03794968 : nt!NtAllocateVirtualMemory+0x3f4
fffff880`03794700 fffff800`032d8490 : fffff800`0359fc05 00000000`00000000 00000000`00400100 fffff880`03794974 : nt!KiSystemServiceCopyEnd+0x13
fffff880`03794908 fffff800`0359fc05 : 00000000`00000000 00000000`00400100 fffff880`03794974 00000000`00000004 : nt!KiServiceLinkage
fffff880`03794910 fffff800`035cc8e5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!RtlpWow64CreateUserStack+0x1e5
fffff880`037949f0 fffff800`035cc13a : fffffa80`0a4d2620 fffff880`03795858 fffffa80`03c58a00 fffff880`03795440 : nt!PspAllocateThread+0x674
fffff880`03794c10 fffff800`035d0049 : fffffa80`00000004 00000000`00000000 00000000`00000001 fffff880`03795440 : nt!PspCreateThread+0x1d2
fffff880`03794e90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtCreateThreadEx+0x25d
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+36c1a
fffff800`0334f812 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+36c1a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 50e79935
FAILURE_BUCKET_ID: X64_0x7a_c0000056_nt!_??_::FNODOBFM::_string_+36c1a
BUCKET_ID: X64_0x7a_c0000056_nt!_??_::FNODOBFM::_string_+36c1a
Followup: MachineOwner
Thanks for your help !
Johann