VB crashes when logging into host via LogMeIn.com

[Dan7Miller]

Host: Win7/64bit, 16GB RAM, 9GB free Guest: WinXP_SP3/32bit, 2GB RAM, 1.4GB free I run the guest in Seamless mode. VB: Version 4.3.6, Guest Additions installed

I use an online service called LogMeIn.com to connect to my host machine from work. This had been working until about two VB updates back (about two months ago), but now when I connect to the host, although everything appears to be running properly at the time, when I get home I find that VirtualBox has crashed, leaving just a blank screen with a Windows error window. Once I close the error box, my host system is still running fine, and the VB Manager is still running, but the Guest OS and VB window for it are gone.

I am enclosing the VB log file for today's event with this message. There are no available minidump files on the host machine, I will check for a minidump on the guest after I file this report (I didn't want to confuse the log file contents).

[Dan7Miller]

Log file for today's crash

[Dan7Miller]

I just checked the Guest OS, and it does not have any minidump files on it either.

[Frank Mehnert]

Please activate application dumps on your Windows host, see ​here.

[Dan7Miller]

Windows dump file for this event

[Dan7Miller]

AHA!! I just realized that I was looking in the wrong location for the Win7 dump file; your link pointed me in the right location. I am attaching the Windows dump file now, named VBox.crash.dump.010714.zip. Thanks for your link.

[Dan7Miller]

One final data point for this issue: I left the guest OS running today, but in normal windowed mode (rather than seamless mode). I logged in from work several times today, and even ran programs on the quest as well as host machines, and had *no* problems at all; when I got home, VB and the guest machine were running fine.

So this confirms that the problem is specifically with Seamless Mode. I hope this is useful data for you.

[aeichner]

Please reopen if still relevant with a recent VirtualBox release.