Page 1 of 1

vbox bsod on win10

Posted: 23. Feb 2017, 01:49
by markl17
i cant start ubuntu on win10pro insider preview produses BSOD
here is last lines of the log

Code: Select all

2974          netIfGetBoundAdapters: could not find either 'oracle_VBoxNetLwf' or 'sun_VBoxNetFlt' components (0x1)
00:00:00.334954          HostDnsMonitor: old information
00:00:00.334954            no server entries
00:00:00.334954            no domain set
00:00:00.334954            no search string entries
00:00:00.334954          HostDnsMonitor: new information
00:00:00.334954            server 1: 192.168.1.1
00:00:00.334954            domain: home
00:00:00.334954            no search string entries
00:00:00.334954          HostDnsMonitorProxy::notify
00:00:00.335955          VD: VDInit finished
00:00:00.341958          Loading settings file "C:\Users\mark\VirtualBox VMs\test\test.vbox" with version "1.16-windows"
00:00:00.347117          Loading settings file "C:\Users\mark\VirtualBox VMs\vagrant_default_1487792015818_5460\vagrant_default_1487792015818_5460.vbox" with version "1.12-windows"
00:00:00.348118          VirtualBox: object created
00:01:32.263450          netIfGetBoundAdapters: could not find either 'oracle_VBoxNetLwf' or 'sun_VBoxNetFlt' components (0x1)
00:01:32.286485          netIfGetBoundAdapters: could not find either 'oracle_VBoxNetLwf' or 'sun_VBoxNetFlt' components (0x1)
00:02:35.968760          ERROR [COM]: aRC=VBOX_E_OBJECT_NOT_FOUND (0x80bb0001) aIID={edba9d10-45d8-b440-1712-46ac0c9bc4c5} aComponent={ExtPackManagerWrap} aText={No extension pack by the name 'Oracle VM VirtualBox Extension Pack' was found}, preserve=false aResultDetail=0

Re: vbox bsod on win10

Posted: 23. Feb 2017, 07:37
by socratis
markl17 wrote:on win10pro insider preview produses BSOD
A couple of things.

First, you are on the insider preview and as such, I'm moving your post from "Windows Hosts" to "Windows pre-releases". BTW, you should be definitely be posting more detailed information version. "Insider preview" is not enough.

Second, there have been BSOD reports with Win10 (standard, not insider) if Hyper-V is enabled on the host. Try to disable it and see if that fixes it.

Third, partial logs are not that useful. If asked for a VBox.log, be sure to ZIP and attach the complete log next time.