Hi, my VBox logs are almost empty (I guess due to them being not fully written on BSOD). Here are a couple of bug tickets describing the same issue (with logs and dumps):
https://www.virtualbox.org/ticket/16392 https://www.virtualbox.org/ticket/15268 https://www.virtualbox.org/ticket/15780 and a discussion thread on the forum: https://forums.virtualbox.org/viewtopic.php?f=6&t=79028 The only "workaround" suggested in all these threads is to disable Hyper-V. No hint on whether the problem will be solved in upcoming releases or not. Regards, Mikhail On Wed, Mar 22, 2017 at 4:06 AM Kalogrianitis Socratis <[email protected]> wrote: > > On 22/Μαρ/2017, at 04:50, Ramshankar <[email protected]> > wrote: > > > If VirtualBox causes a BSOD regardless of whether VT-x has been grabbed > by Hyper-V or any other program, it should be considered a bug. > > I'm not sure if you're aware of it or not, but the forums are full of > reports of this exact thing happening in Windows 10, especially after an > update which turns on Hyper-V. The currently going advice is to disable > Hyper-V, which of course stops the BSOD. > _______________________________________________ > vbox-dev mailing list > [email protected] > https://www.virtualbox.org/mailman/listinfo/vbox-dev >
_______________________________________________ vbox-dev mailing list [email protected] https://www.virtualbox.org/mailman/listinfo/vbox-dev
