VirtualBox

Opened 10 years ago

Closed 9 years ago

Last modified 9 years ago

#13295 closed defect (fixed)

VBoxDrv.sys causes BSoD (SYSTEM_SERVICE_EXCEPTION) on Microsoft Windows 8.1 [FIXED IN SVN]

Reported by: oklein Owned by:
Component: other Version: VirtualBox 4.3.14
Keywords: Cc:
Guest type: all Host type: Windows

Description

This is my very first bug report ever and English isn't my mother tongue, so please bear with me. I've searched for this problem, but I couldn't find a corresponding ticket that's not closed. I'm really sorry if this problem is known already!

My host is running Microsoft Windows 8.1 Pro x64 and every time I cold boot this (physical) machine the first attempt to wake up a suspended virtual machine will result in a blue screen of death with "SYSTEM_SERVICE_EXCEPTION". After the physical machine has rebooted the virtual machine will resume just fine.

At first I thought this might be caused by faulty RAM, but I've ran MemTest for roughly 6 hours with no errors at all. I re-installed the host OS and installed nothing but updates for Windows and VirtualBox to rule other programs out. Considering the consistency of this error (and the way to reproduce it) makes me believe it's really a bug in VirtualBox itself.

CPU: Intel Core i7-4790K (not overclocked)
RAM: 16GB Corsair Vengeance Pro (not overclocked)
MB: ASUS Z97-AR (tested BIOS versions 1205 and 1304)
SSD: Corsair Force Series GS 240 GB
GFX: 2x AMD Radeon R9 290X

All the latest drivers and OS updates installed. BIOS settings are all reset to their defaults.

Attachments (8)

081714-22734-01.dmp (274.6 KB ) - added by oklein 10 years ago.
Microsoft Windows 8.1 Pro x64 Minidump
VBox.log (91.1 KB ) - added by oklein 10 years ago.
Most recent VBox.log (only gets created when there's no BSoD)
Windbg-Bugcheck-Analysis.txt (8.9 KB ) - added by Francis 9 years ago.
Windbg bug-check analysis
111314-19093-01.zip (31.7 KB ) - added by sdy7 9 years ago.
minidump zipped
VBoxSVC.log (2.3 KB ) - added by Carsten H. 9 years ago.
VBoxStart log, the second launch today worked without any problems.
VBox.2.log (54.6 KB ) - added by Carsten H. 9 years ago.
VBox.log of today (19. Nov. 2014)
VBoxStartup.log (306.7 KB ) - added by Carsten H. 9 years ago.
Sorry, here the Startup.log
120714-13500-01.dmp (127.1 KB ) - added by starteleport 9 years ago.
minidump

Download all attachments as: .zip

Change History (36)

by oklein, 10 years ago

Attachment: 081714-22734-01.dmp added

Microsoft Windows 8.1 Pro x64 Minidump

by oklein, 10 years ago

Attachment: VBox.log added

Most recent VBox.log (only gets created when there's no BSoD)

comment:1 by bird, 9 years ago

Resolution: fixed
Status: newclosed
Summary: VBoxDrv.sys causes BSoD (SYSTEM_SERVICE_EXCEPTION) on Microsoft Windows 8.1VBoxDrv.sys causes BSoD (SYSTEM_SERVICE_EXCEPTION) on Microsoft Windows 8.1 [FIXED IN SVN]

We hope this is addressed in 4.3.18.

comment:2 by Mihai Hanor, 9 years ago

The VBoxDrv assert is not fixed. I have encountered it today, for the first time, with VirtualBox 4.3.18 and Windows 8.1 x64 as host OS. I've double-clicked a VM shortcut, to start it, but the host OS was halted in a split of a second. I have an automatic kernel dump available. If you need it, I can upload it somewhere.

Last edited 9 years ago by Mihai Hanor (previous) (diff)

comment:3 by Mihai Hanor, 9 years ago

Resolution: fixed
Status: closedreopened

comment:4 by Mihai Hanor, 9 years ago

Possible duplicate: #13502

comment:5 by Francis, 9 years ago

I'm hesitant to add a "me too" here, but I appear to be hitting this rather annoying bug in current stable (4.3.18-r96516). From a quick comparison of attachment #1 and my own (full) crash dump, I'd hazard a guess that is not actually fixed. I'll attach the bug-check analysis output from WinDbg in a moment.

I'd really like to see this fixed, so if there's anything further I can provide to help, please just ask. Thanks!

by Francis, 9 years ago

Windbg bug-check analysis

comment:6 by Frank Mehnert, 9 years ago

mhanor, could you make the kernel dump available for us? Thank you?

comment:7 by Mihai Hanor, 9 years ago

Please check your e-mail. Also, I have encountered this issue only once.

Last edited 9 years ago by Mihai Hanor (previous) (diff)

comment:8 by Frank Mehnert, 9 years ago

I've got the file, thank you.

comment:9 by sdy7, 9 years ago

I got it too. Same way, where it happens when double clicking a vm instance icon. I have encountered several times. Version 4.3.18 host: Windows 8.1 x64. Please let me know if other info is needed. Minidump attached: 111314-19093-01.zip

Last edited 9 years ago by sdy7 (previous) (diff)

by sdy7, 9 years ago

Attachment: 111314-19093-01.zip added

minidump zipped

comment:10 by Francis, 9 years ago

In case it's helpful, I can reproduce this reliably with the following steps:

  1. Open VBox GUI and start a VM (an empty VM with only a Linux-based live ISO suffices).
  2. Shutdown VM and repeat using VBoxHeadless.

Ten, or less iterations reliably results in a BSOD here.

comment:11 by Frank Mehnert, 9 years ago

We think we found and fixed this problem. Could you install this test build and confirm that the problem is gone? Thank you!

comment:12 by Francis, 9 years ago

Excellent, much appreciated! I'll give it a spin ASAP and report back.

comment:13 by Francis, 9 years ago

I left a cheap and dirty reproducer running over night and things are looking good, not a single crash. You guys are awesome, thank you!

I'm guessing you're all Oracle employees, so an unofficial beer fund might be frowned upon, but if I'm wrong, please let me know. It's the least I could do to say thanks! :)

comment:14 by sdy7, 9 years ago

Cheers Frank! So far the BSOD seems to have gone away with 4.3.19 test build you provided.

comment:15 by Carsten H., 9 years ago

My host is also running Microsoft Windows 8.1 Pro x64. When I start my VirtualBox machine, the error "SYSTEM_SERVICE_EXCEPTION (VBOXDRV.SYS)" occurs, the host system crashes.

As described in this ticket, I installed the test build VirtualBox4.3.19-96923-Win.exe. Now the host system no longer crashes after starting the VirtualBox machine, but it appears the following error:

VirtualBob - Error In suplibOsInit
VERR_ACCESS_DENIED (rc=-38)
Make sure the kernel module has been loaded successfully.

What can I do?

comment:16 by Frank Mehnert, 9 years ago

azh65, please could you attach the VBoxStartup.log file of such a VM session?

by Carsten H., 9 years ago

Attachment: VBoxSVC.log added

VBoxStart log, the second launch today worked without any problems.

comment:17 by Carsten H., 9 years ago

Here is a further specification:
Today again the same error.

By the way:
I have created a link for the machine on the desktop from the VirtualBox Manager. Using this link I started this machine- several times with the above error.
Now I have opened the VirtualBox Manager and this machine boots from the Manager without error ...

comment:18 by sunlover, 9 years ago

azh65, please attach the VBoxStartup.log. It is located in the Users/.../VirtualBox VMs/VMNAME/Logs directory.

by Carsten H., 9 years ago

Attachment: VBox.2.log added

VBox.log of today (19. Nov. 2014)

comment:19 by sunlover, 9 years ago

azh65, thanks but we need the file with name VBoxStartup.log. So far you attached VBoxSVC.log and VBox.2.log files.

by Carsten H., 9 years ago

Attachment: VBoxStartup.log added

Sorry, here the Startup.log

comment:20 by sunlover, 9 years ago

Thanks. These files (VBoxSVC.log, VBox.2.log and VBoxStartup.log) were taken after a successful start of the virtual machine, right?

If yes, then please reproduce the error again and then immediately get VBoxSVC.log, VBox.log and VBoxStartup.log

BTW, this problem (VERR_ACCESS_DENIED (rc=-38)) is something different and not related to this ticket. Could you please create a new ticket and attach the requested logs to it?

comment:21 by Jasseh, 9 years ago

I started having these same BSOD errors last week.

I had thought they were caused by Windows updates as they started Wednesday last week but after a system restore to remove the updates they continued to occur.

I updated several pieces of software, including VirtualBox and this seemed like it had solved the problem but the BSOD has just occurred again after attempting to launch one of my VMs through a link on the desktop (rather than VBox Manager).

Should I install the test version referenced above?

comment:22 by Carsten H., 9 years ago

Thank you for comment, sunlover.
I have initiated Ticket #13632 with newest log files after reproduce error.

BTW, Virtualbox has not written the VBoxStartup.log at the error. The timestamp is from the day before.

comment:23 by Frank Mehnert, 9 years ago

Could you try if VBox 4.3.20 solves your problems by any chance?

comment:24 by Mihai Hanor, 9 years ago

I think you can close this ticket.

comment:25 by Frank Mehnert, 9 years ago

Resolution: fixed
Status: reopenedclosed

Thanks.

by starteleport, 9 years ago

Attachment: 120714-13500-01.dmp added

minidump

comment:26 by starteleport, 9 years ago

I believe I can still reproduce this even on latest test version. BSOD is every single time I try to resume my Ubuntu VM.

UPD. I wish I could attach VBoxStartup.log, but there's only 4K of zeroes.

Last edited 9 years ago by starteleport (previous) (diff)

comment:27 by Mihai Hanor, 9 years ago

Your problem is different than the one reported here. Read this

comment:28 by starteleport, 9 years ago

Aww, sorry :) Thanks for pointing this out.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use