KMODE_EXCEPTION_NOT_HANDLED

Discussions related to using VirtualBox on Windows hosts.
Post Reply
saberman
Posts: 293
Joined: 21. Dec 2009, 00:32
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Windows XP, 7, 8.1, 10

KMODE_EXCEPTION_NOT_HANDLED

Post by saberman »

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.
Last edited by saberman on 25. Nov 2014, 12:17, edited 1 time in total.
saberman
Posts: 293
Joined: 21. Dec 2009, 00:32
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Windows XP, 7, 8.1, 10

Re: KMODE_EXCEPTION_NOT_HANDLED

Post by saberman »

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
==================================================
Last edited by saberman on 25. Nov 2014, 12:17, edited 1 time in total.
socratis
Site Moderator
Posts: 27329
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: KMODE_EXCEPTION_NOT_HANDLED

Post by socratis »

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?
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
saberman
Posts: 293
Joined: 21. Dec 2009, 00:32
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Windows XP, 7, 8.1, 10

Re: KMODE_EXCEPTION_NOT_HANDLED

Post by saberman »

I missed seeing the edit button.

I have attached the referenced file here. (I am used to uploading to OneDrive and linking to it.)
Attachments
112514-9203-01.zip
File referenced in original post.
(157.71 KiB) Downloaded 19 times
socratis
Site Moderator
Posts: 27329
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: KMODE_EXCEPTION_NOT_HANDLED

Post by socratis »

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]
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
saberman
Posts: 293
Joined: 21. Dec 2009, 00:32
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Windows XP, 7, 8.1, 10

Re: KMODE_EXCEPTION_NOT_HANDLED

Post by saberman »

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.
Post Reply