After upgrading to VirtualBox 5.0, on Windows 7 SP1 x64, I'm experiencing frequent BSOD when I attempt to boot a Linux guest VM (Ubuntu 14.04 LTS x64).
It's odd that the BSOD does not happen every time I boot the VM. I'd say it happens 25% of the time. The BSOD always occurs at the same point in the startup sequence, which is basically at the beginning (i.e., before the splash screen with the VirtualBox logo appears -- presumably during or immediately after the POST process).
I'm not particularly familiar with debugging memory dumps on Windows, but without the VirtualBox debugging symbols, here's what I see with WinDbg:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {fffff8a000bc7080, 2, 0, fffff80002edaf5e}
*** ERROR: Module load completed but symbols could not be loaded for VBoxNetLwf.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for VMMR0.r0 -
*** ERROR: Module load completed but symbols could not be loaded for VBoxDrv.sys
PEB is paged out (Peb.Ldr = 000007ff`fffdf018). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 000007ff`fffdf018). Type ".hh dbgerr001" for details
Probably caused by : VBoxNetLwf.sys ( VBoxNetLwf+4492 )
Are the debugging symbols available somewhere? Or better yet, is there an article that explains exactly what information would be helpful to the VirtualBox developers (or other qualified individuals)?Thanks for any ideas!