virtualbox.org

Host Operating system is newly imaged Windows 10.
To reproduce:

• * download and install VirtualBox 6.1.2 with all defaults
  * start the VirtualBox Manager
  * plug the HP Univeral G2 into the laptop

This will crash the Windows 10 host with a Blue Screen Of Death: "PNP DETECTED FATAL ERROR"

There isn't any VM involved (therefore no VM log). This is only from having the VirtualBox Manager started. This is specific to versions 6.1.0 and 6.1.2. The problem does not happen with 6.0.x.

This has been verified on two different HP Zbook 15u G5 and one HP EliteBook 840 G5, both with the factory BIOS and the latest available BIOS (Jan 17 2020). It has also been verified on two different universal docks G2 both with the factory firmware and with the latest available firmware.

Is there any known workaround?

Thanks

--
Come

I for one will have a problem trying to replicate this, starting at this step:

come_raczy wrote:plug the HP Univeral G2 into the laptop

I don't have one.

However, the docks I have seen when I played IT for a while had drivers and extra USB and Ethernet ports. Could be that Virtualbox's USB or Ethernet drivers aren't happy with the addition of the dock's hardware. (assuming Virtualbox is at the bottom of the BSOD.)

If you always get the BSOD plugging in the dock only when the main Virtualbox window is open and never when the main Virtualbox window is closed, then it sounds like something may be amiss between the dock and Virtualbox. A thorough debug of the BSOD would be required to pinpoint Virtualbox in the lineup.

Also, does the BSOD happen when the main Virtualbox window is opened after the dock is plugged in? In other words, reverse steps 2 & 3?

There is a Virtualbox service running whenever a Virtualbox window, vboxmanage command, or guest is running, and there is a VboxSVC.log in the C:\Users\{you}\.Virtualbox folder. See what that says as a possible clue to the BSOD.

Have you tried installing Virtualbox while the dock is already attached? Maybe Virtualbox could plug into the hardware better. Also try right-click-run-as-admin on the Virtualbox installer, even if you are already admin, while the dock is atrached. RaA sometimes makes an install work better on Windows hosts.

Thanks a lot for the suggestions.

The issue is so reproducible that I am very confident that VirtualBox Manager 6.1.x is at the bottom of the BSOD. It happens if and only if VirtualBox Manager 6.1.x is running and it happens right at the moment where i am docking the laptops into the G2. Undocking works fine. Operations while docked and while undocked are fine.
I have tried installing while docked and while undocked. Also explicitly ran the installer as Admin. All had the same outcome.

I have attached the VBoxSVC log file and the last entries are right after the USB enumeration. These are the last three lines. Would this error 31 be relevant or is is just a normal thing?

00:20.718292 USBPROXY usbLibGetDevices: Starting USB device enumeration
00:00:20.718795 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&209f0815&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 9
00:00:20.872313 USBPROXY usbLibGetDevices: Found 2 USB devices, 0 captured

Edit: These last three lines are actually generated when undocking. No additional line is generated then docking.

How can I generate a full debug trace? What are reasonable debugging tools on windows 10 (I guess that gdb won't cut it)?

Thanks,
--
Come

You might want to post this on the Bugtracker, with the VboxSVC.log and a full complete list of the steps you tried, such as what you've said above.

Thanks for the helpful suggestion.

In case someone has a similar issue and lands on this thread, that would be Bugtracker Ticket #19326.
--
Come

Seems to be a good ticket. Hopefully the devs will see what might be up.

You are running Windows 10 1809. Do you have a chance to test with 1903 or 1909?

Unfortunately I can't. These are corporate assets and that's one of the things that I can't do.

I just stumbled across this thread because I had the same BSOD shortly after installing VirtualBox on Win 10 1903. In my case, I have a StarTech HDMI/USB KVM, and I had switched to the "other" machine. When I switched back to the machine where VB was installed, it was completely frozen. It stayed like that for a few minutes and then crashed to the blue screen. As with the OP, the VB Manager was open at the time. I can not replicate because I have uninstalled VB. I had just installed it today when this happened, so I immediately removed VB, as it was the most recent significant change to the system. I'm guessing that the KVM acts as a USB Hub to switch the keyboard and mouse, so it is a very similar occurrence.

Was there a ticket opened on this that someone could point me to?

Matt

Sorry...I just saw the link to the Bugtracker, and I found the ticket (19326) myself.