Change History

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.

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.