Segmentation fault

[terry]

I don't know what prompted it, unfortunately. A couple minutes earlier I had attached a USB external storage device to the VM (which seemed to be handled by the guest OS without incident), then I told Windows 10 to check for updates. While it was doing that the VM window disappeared and I found a crash file. That VM session had been running for a while and been through at least one sleep–wake cycle of the host machine and the accompanying wireless network disconnections and reconnections.

I restarted the VM, and tried to reproduce by attaching the same USB device and telling Windows to check for updates again, but the crash did not repeat.

VirtualBox version: 5.1.10 r112026 Host OS: macOS 10.12.1 Guest OS: Windows 10 Pro Insider Preview version 1607 build 14965.1001

[terry]

Crash file automatically generated by host macOS

[terry]

VBox.log left behind (sanitized: username, external IPs, domain)

[Frank Mehnert]

The crash happens in 'com.apple.GeForceGLDriver' so it's most likely 3D-related. I assume that starting the guest with '3D' disabled will workaround the problem.

[terry]

Thanks for the suggestion. If it recurs, I'll keep that in mind. I noticed after creating the ticket, however, that my guest additions were one version behind (5.1.8) VBox at the time. (For some reason at some point it stopped reliably warning me when it needed updating.)