fth0 wrote:If it had an appropriate exception handler installed (e.g. rtR3WinUnhandledXcptFilter), it would have dumped information into the VBox.log file already.
This statement of mine could be slightly wrong: VirtualBox has its
rtR3WinUnhandledXcptFilter installed during most of the
VirtualBoxVM process runtime, but it uses the standard logging mechanisms, and if they are currently locked when the exception occurs,
rtR3WinUnhandledXcptFilter cannot create the log messages. In any case, it calls the Windows default unhandled exception filter afterwards, which then creates the Windows error dialog.
scottgus1 wrote:If fth0 or any other forum guru has an idea
fth0 wrote:Windows usually create crash dump files (e.g. a minidump file), and you can analyze them with WinDBG Preview. Alternatively, the Windows Event Log may contain information about the crash.
To elaborate a bit on my first suggestion:
On the Windows host, install
WinDbg Preview from the
Microsoft Store, which is a (somewhat user friendly) modern version of the (in)famous
WinDbg. Configure the Windows host to create minidump files on user-mode application crashes (see
Collecting User-Mode Dumps for how to do that). Reproduce the VirtualBox crash. Open the minidump file in
WinDbg Preview, which will automatically execute
!analyze -v and hopefully provide a good backtrace of the crash.