virtualbox.org

VBox: 4.3.18r96516
Host: Surface Pro 3 512GB Windows 8.1 with all patches
Guest: Windows 7 Ultimate x64 with all patches

I just finished backing up my VMs and associated files. All was quiet. I clicked on the shortcut to one of my VMs and Windows said sorry -- we have to restart.
The VBox and VM logs and the minidump and system information are attached to a post further down.

Any suggestions would be appreciated.

Here is the information:
==================================================
Dump File : 112514-9203-01.dmp
Crash Time : 11/25/2014 4:14:28 AM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : ffffffff`80000003
Parameter 2 : fffff800`08a7bed4
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000001
Caused By Driver : VBoxDrv.sys
Caused By Address : VBoxDrv.sys+eed4
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address :
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\windows\Minidump\112514-9203-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 9600
Dump File Size : 424,528
==================================================

Of course there is an Edit button for your posts. When you said "Windows has to restart" are you referring to the host or the guest? I believe it's the host, just trying to make sure...

PS. You've been here long enough to know that a lot of people will not go on third-party websites for logs and information, so could you edit your posts and attach all the relevant information locally?

I missed seeing the edit button.

I have attached the referenced file here. (I am used to uploading to OneDrive and linking to it.)

Take a look at a the bug #13295 that was fixed recently, with VBox 4.3.20: VBoxDrv.sys causes BSoD (SYSTEM_SERVICE_EXCEPTION) on Microsoft Windows 8.1 [FIXED IN SVN]

socratis wrote:Take a look at a the bug #13295 that was fixed recently, with VBox 4.3.20: VBoxDrv.sys causes BSoD (SYSTEM_SERVICE_EXCEPTION) on Microsoft Windows 8.1 [FIXED IN SVN]

There are two major differences between what I reported and bug #13295:
1. The VM was not suspended. It was properly shutdown.
2. The bug check I reported occurred after the host had been rebooted. The workaround in the bug report was to reboot the host before restarting the VM.