Opened 8 years ago
Closed 8 years ago
#16675 closed defect (duplicate)
It causes windows 10 ( Creators update ) to have a BSOD
| Reported by: | angarato_surion | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 5.1.20 |
| Keywords: | Cc: | ||
| Guest type: | all | Host type: | Windows |
Description
It causes windows 10 ( Creators update ) to have a BSOD Error: SYSTEM_SERVICE_EXCEPTION
Attachments (8)
Change History (29)
comment:1 by , 8 years ago
by , 8 years ago
comment:2 by , 8 years ago
i just select one of the virtual machines and when i t goes to boot/start it it causes the bsod
follow-up: 4 comment:3 by , 8 years ago
To be clear: The host shows a BSOD (the computer one which you execute VirtualBox), is that correct?
follow-up: 5 comment:4 by , 8 years ago
Replying to frank:
To be clear: The host shows a BSOD (the computer one which you execute VirtualBox), is that correct?
The host of course .. iwill n't care if it was the os runing in virtualbox..
comment:5 by , 8 years ago
Hi,
I'm using VirtualBox 5.1.18 on Win10 Pro 64 bits host.
Whenever I start a Win10 guest VM, I get a BSOD on the host :
Stop code : IRQL_NOT_LESS_OR_EQUAL
Looking at the crashdump, I get this conclusion from WinDbg (X64) :
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {0, ff, 0, 0}
*** WARNING: Unable to verify timestamp for VBoxDrv.sys
*** ERROR: Module load completed but symbols could not be loaded for VBoxDrv.sys
*** WARNING: Unable to verify timestamp for VMMR0.r0
*** ERROR: Module load completed but symbols could not be loaded for VMMR0.r0
*** WARNING: Unable to verify timestamp for VBoxDDR0.r0
*** ERROR: Module load completed but symbols could not be loaded for VBoxDDR0.r0
Probably caused by : VBoxDrv.sys ( VBoxDrv+1f630 )
Upgrading VirtualBox to version 5.1.20 r114628 (Qt5.6.2) does not change anything. On the other hand, my Linux VMs works perfectly fine.
Could it be the same problem ? Or should I create a new ticket ?
follow-up: 7 comment:6 by , 8 years ago
ghislain, could you please provide entire output of the '!analyze -v' command, including the call stack?
comment:7 by , 8 years ago
Replying to sunlover:
ghislain, could you please provide entire output of the '!analyze -v' command, including the call stack?
Done.
follow-up: 11 comment:8 by , 8 years ago
angarato_surion, thanks for the dumps. In your case this looks like the same problem as in ticket #15780. Try to disable Hyper-V. See comment 6 there: https://www.215389.xyz/ticket/15780#comment:6
follow-up: 10 comment:9 by , 8 years ago
ghislain, the callstack shows a different problem. Please attach a minidump taken with VirtulBox 5.1.20. Thanks!
by , 8 years ago
| Attachment: | callstack_Vbox_5.1.20.txt added |
|---|
WinDbg output with call stack with Vbox 5.1.20
follow-up: 13 comment:10 by , 8 years ago
Replying to sunlover:
ghislain, the callstack shows a different problem. Please attach a minidump taken with VirtulBox 5.1.20. Thanks!
Sorry, I did not pay attention to that. The one I have just attached should have been generated with VirtualBox 5.1.20.
comment:11 by , 8 years ago
Replying to sunlover:
angarato_surion, thanks for the dumps. In your case this looks like the same problem as in ticket #15780. Try to disable Hyper-V. See comment 6 there: https://www.215389.xyz/ticket/15780#comment:6
i boot with hyper-v disabled and crashes
comment:13 by , 8 years ago
Replying to ghislain:
Replying to sunlover:
ghislain, the callstack shows a different problem. Please attach a minidump taken with VirtulBox 5.1.20. Thanks!
Sorry, I did not pay attention to that. The one I have just attached should have been generated with VirtualBox 5.1.20.
Minidump added.
follow-up: 15 comment:14 by , 8 years ago
ghislain, thanks for the minidump. Does the crash happen immediately after you start a Windows 10 VM or after some time? What the guest is doing when the crash happens?
comment:15 by , 8 years ago
Replying to sunlover:
ghislain, thanks for the minidump. Does the crash happen immediately after you start a Windows 10 VM or after some time? What the guest is doing when the crash happens?
It crashes pretty quickly after the logon. The guest is really slow and unusable.
follow-up: 17 comment:16 by , 8 years ago
ghislain, any idea when this crash started to happen? After Windows Creators update? After VirtualBox update? Did the VM work in the past? If yes, which VirtualBox and Windows versions?
I'm asking because the crash happens in a code path which has not been changed recently in VirtualBox and because we do not have similar reports so far.
comment:17 by , 8 years ago
Replying to sunlover:
ghislain, any idea when this crash started to happen? After Windows Creators update? After VirtualBox update? Did the VM work in the past? If yes, which VirtualBox and Windows versions?
I'm asking because the crash happens in a code path which has not been changed recently in VirtualBox and because we do not have similar reports so far.
Having a look at my Windows update history, I have realized that Creators update has not been applied yet to my host so I'm still running Windows 10 Pro 64 bits 1607. My VMs worked perfectly fine (for months) up to the first BSOD around the 17th of April. It first occured without any update, neither on Window, neither on Virtualbox. I can't even check the version of the Windows running on my VM, it crashes before the logon screen.
I have upgraded to version 5.1.22 of VB but still encounter BSOD. No problem running my Linux VMs.
comment:18 by , 8 years ago
ghislain, please run the following command, where VMNAME is the name of your crashing Win10 VM:
VBoxManage setextradata VMNAME "VBoxInternal/Devices/ahci/0/Config/R0Enabled" 0
Then run the VM. If it BSODs again, then please attach the new minidump. And also in any case attach VBox.log of this VM. Thanks!
comment:19 by , 8 years ago
I also got the BSOD, so I took Kernel dump and attached. The "VBoxSVC.log" is empty so I attached another one (may be old)
comment:20 by , 8 years ago
I have disabled Hyper-V and rebooted the host systems. Now I am able to run virtual box without BSOD.
comment:21 by , 8 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
Closing as duplicate of #16801.
Sorry, not enough information. The absolute minimum required information is a VBox.log file of a VM run. I even don't know if your host crashes or your guest. If your hosts crashes then please describe at which time: When you opened the selector, when you started a VM etc. Again, if there is any VBox.log file for a started VM available, please attach it to this ticket.