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

[oklein]

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.

[oklein]

Microsoft Windows 8.1 Pro x64 Minidump

[oklein]

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

[bird]

We hope this is addressed in 4.3.18.

[Mihai Hanor]

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.

[Mihai Hanor]

Possible duplicate: #13502

[Francis]

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!

[Francis]

Windbg bug-check analysis

[Frank Mehnert]

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

[Mihai Hanor]

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

[Frank Mehnert]

I've got the file, thank you.

[sdy7]

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

[sdy7]

minidump zipped

[Francis]

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.

[Frank Mehnert]

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

[Francis]

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

[Francis]

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! :)

[sdy7]

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

[Carsten H.]

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?

[Frank Mehnert]

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

[Carsten H.]

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

[Carsten H.]

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

[sunlover]

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

[Carsten H.]

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

[sunlover]

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

[Carsten H.]

Sorry, here the Startup.log

[sunlover]

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?

[Jasseh]

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?

[Carsten H.]

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.

[Frank Mehnert]

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

[Mihai Hanor]

I think you can close this ticket.

[Frank Mehnert]

Thanks.

[starteleport]

minidump

[starteleport]

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.

[Mihai Hanor]

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

[starteleport]

Aww, sorry :) Thanks for pointing this out.