Fatal error (blue screen of death) when starting VM

Discussions related to using VirtualBox on Windows hosts.

Fatal error (blue screen of death) when starting VM

Postby HLR » 15. May 2021, 19:07

Hello,

I've only recently started using VirtualBox and have been running it for about a month without issues. I've installed VirtualBox 6.1 (checked for updates and it said I'm running the most recent version) on Windows 10 (10.0.1.19042) and have set up a Linux VM with Pop!_OS. All of a sudden, I'm running into a fatal error every time I try to start Pop!_OS in VirtualBox. I can open VB, but when I try to start my VM, it crashes my PC (blue screen, fatal error, PC restarts). Running VB as an administrator makes no difference (a suggestion I saw somewhere). I'm not sure how to resolve this. This set up is essential for me to get working, and I'm not sure why this is happening suddenly. Any help would be appreciated. If there are log files I should be looking at, or anything I should be trying, please suggest away.

EDIT: If it helps, both Hyper-V and Microsoft Defender Application Guard are already turned off on my Windows PC (I double checked that when I was looking for a solution, but were already already off on my machine, so that's not causing the issue). I also checked my Windows update history. There was an Intel - net - 22.40.0.7 update around the same time, plus a Microsoft Defender and Security Intelligence update. Nothing else updated more recently than two weeks ago.
HLR
 
Posts: 5
Joined: 15. May 2021, 19:00

Re: Fatal error (blue screen of death) when starting VM

Postby scottgus1 » 15. May 2021, 20:16

HLR wrote:when I try to start my VM, it crashes my PC (blue screen, fatal error, PC restarts)


try uninstalling Virtualbox, reboot, then reinstall Virtualbox using right-click Run As Administrator, even if your account is already an admin.

If that does not stop the BSODs, download Nirsoft BlueScreenView (free) https://www.nirsoft.net/utils/blue_screen_view.html and see if you can determine the BSOD code and source crashing file.
scottgus1
Site Moderator
 
Posts: 12447
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Fatal error (blue screen of death) when starting VM

Postby HLR » 28. May 2021, 16:56

Unfortunately, uninstalling and reinstalling VirtualBox did not solve the issue. I'm still getting to BSOD everything time I try to start my Pop!_OS VM from VirtualBox. I finally caught the error listed on the screen, which is the "PNP_DETECTED_FATAL_ERROR". Looking back at driver updates and such, there doesn't seem to be any PnP devices that had driver updates at the time this issue started happening (and no new devices have been introduced). In term of PnP devices, I have an external monitor, camera, mouse, keyboard, and mic plugged in (always plugged in). Nothing changed in my setup since I first started using VirtualBox.

I should note that this is a work computer, so I can't download any third-party software that isn't approved (such as the Nirsoft application suggested). Since it's a remote company, there's no onsite IT in my home, either. :) The only suggestion I received from IT about this is to use something like VMWare instead of VirtualBox, or a second laptop dedicated just to Linux (which defeats the point of having a single device attached to a single external monitor/keyboard/mouse/camera that allows me to easily switch back and forth between the two OSes. I'd love to be able to get VirtualBox working again, though. It was great for the month or so it actually worked, before it started crashing my PC everything time I tried to start the Linux VM.
HLR
 
Posts: 5
Joined: 15. May 2021, 19:00

Re: Fatal error (blue screen of death) when starting VM

Postby scottgus1 » 28. May 2021, 18:40

OK, I guess there's nothing that can be done if your work's IT won't let you troubleshoot. Though you did get authorization to use Virtualbox, which is a lot deeper than a BSOD diagnoser. Ask IT what to do to diagnose the BSOD, is all I can suggest. Usually, knowing that the PC has IT overlords from work is a good thing to put in the first post, so we know the full story of what we're dealing with.

Virtualbox doesn't normally cause BSODs, as my reading of the forum for several years shows. It does happen, but very often because of something else on the PC besides Virtualbox, or an OS bit-flip somewhere that a complete reinstall of the host OS and progs fixes. The IT dept probably have their fingers in the pie and something they want on the PC interferes with Virtualbox. Probably nothing we can do about that, unless your boss is willing to go to bat for you with IT to get them to enable your Virtualbox.

Alternatives IT may like better could be to forget Virtualbox and bring your existing VM into Hyper-V or WSL2.
scottgus1
Site Moderator
 
Posts: 12447
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Fatal error (blue screen of death) when starting VM

Postby fth0 » 28. May 2021, 20:09

FWIW, googling "site:forums.virtualbox.org PNP_DETECTED_FATAL_ERROR" yields a few cases where USB devices played a role. For a test, detach all USB devices, reboot the host, and see if the problem persists.
fth0
Volunteer
 
Posts: 2153
Joined: 14. Feb 2019, 03:06
Location: Germany
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...

Re: Fatal error (blue screen of death) when starting VM

Postby HLR » 28. May 2021, 22:18

Thanks for the follow up, @scottgus1 and @fth0. I was able to get permission for the bluescreen tool after all (it had to pass a security review first). It's pointing to the VBoxUSBMon.sys driver as causing the issue. Since I need to use my USB devices, are there any workarounds for this that either of you are aware of? I'm finding posts of other people having similar issues, but no solutions. FYI, these USB devices are always plugged in (it's not a matter of crashing when devices are plugged in or unplugged after things are running).

Note that I have just updated Windows (now on build 19043.1023) and reinstalled VirtualBox to try to resolve the issue, but the error persists.
HLR
 
Posts: 5
Joined: 15. May 2021, 19:00

Re: Fatal error (blue screen of death) when starting VM

Postby scottgus1 » 28. May 2021, 22:53

if you are sure you will never want to use USB in your VMs, you can un/re-install Virtualbox without the optional USB system. That should remove VBoxUSBMon.sys

Alternatively, remove all USB devices but the mouse and keyboard, see if Virtualbox will run sans BSOD. If it does, add one other device, try again. Continue adding devices one at a time until the BSOD returns. If you can pin down one device that must be present for the Virtualbox BSOD, then maybe just that decice can be unplugged when running a VM.
scottgus1
Site Moderator
 
Posts: 12447
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Fatal error (blue screen of death) when starting VM

Postby fth0 » 28. May 2021, 23:10

HLR wrote:Since I need to use my USB devices

That's why I wrote "For a test, ...". It could be interesting to know which USB device contributes to the problem.

In addition to that, please provide a zip file containing everything in C:\Users\<username>\.VirtualBox\.

Keeping the following option for later, if necessary:
Depending on the Windows host's configuration, you'll either find one or several minidump files in C:\Windows\Minidump, or one file named C:\Windows\MEMORY.DMP, or both. Can you provide such a file, corresponding to a host crash? Note that you probably cannot attach it to a posting here, because it will exceed the 128 kB limit of the VirtualBox forums.
fth0
Volunteer
 
Posts: 2153
Joined: 14. Feb 2019, 03:06
Location: Germany
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...

Re: Fatal error (blue screen of death) when starting VM

Postby HLR » 4. Jun 2021, 16:44

My apologies for the delayed reply. It took a little while before I was able to test things out again. So, I started by unplugging all USB devices and the Linux VM worked fine (no BSOD). I then proceeded to plug in one USB device at a time. Keyboard and mouse were fine, but the issue was the USB hub (where my external camera is plugged in -- with my current setup, I can't use the built-in camera, so I have an external camera mounted on my external monitor). When I plugged that in the hub (it's a USB-C device), there was a "failed to read USB card reader" error (the hub does have a card reader as well as several USB slots). However, even with that error now coming up every time I start up the VM, it's no longer crashing, and I can still use the camera on the Windows host.

So, if I do see the BSOD again when starting up the VM, I know the culprit. While I can't use the VM without the external keyboard and mouse (without completely overhauling my work setup), I can live without the external camera most of the time.

Thanks for all your help!
HLR
 
Posts: 5
Joined: 15. May 2021, 19:00

Re: Fatal error (blue screen of death) when starting VM

Postby scottgus1 » 4. Jun 2021, 18:45

Excellent, thanks for reports your findings!
scottgus1
Site Moderator
 
Posts: 12447
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Fatal error (blue screen of death) when starting VM

Postby HLR » 4. Jun 2021, 21:45

Oh, and if it's useful at all, I did go through the log files. The VBboxSVC.log file is the only one that included any information about this. I'll just paste the info here, rather than uploading all the files.

Code: Select all   Expand viewCollapse view
00:00:00.003975 main     VirtualBox COM Server 6.1.22 r144080 win.amd64 (Apr 28 2021 17:23:11) release log
00:00:00.003979 main     Log opened 2021-06-04T14:11:04.872650200Z
00:00:00.003979 main     Build Type: release
00:00:00.003995 main     OS Product: Windows 10
00:00:00.003996 main     OS Release: 10.0.19043
00:00:00.003997 main     OS Service Pack:
00:00:00.024109 main     DMI Product Name: 20M9CTO1WW
00:00:00.035845 main     DMI Product Version: ThinkPad P52
00:00:00.035870 main     Firmware type: UEFI
00:00:00.036537 main     Secure Boot: Enabled
00:00:00.036549 main     Host RAM: 65243MB (63.7GB) total, 56121MB (54.8GB) available
00:00:00.036557 main     Executable: C:\Program Files\Oracle\VirtualBox\VBoxSVC.exe
00:00:00.036558 main     Process ID: 16628
00:00:00.036559 main     Package type: WINDOWS_64BITS_GENERIC
00:00:00.156896          VirtualBox: object creation starts
00:00:00.157691          Home directory: 'C:\Users\[redacted]\.VirtualBox'
00:00:00.157901          Installed Drivers:
00:00:00.169362            C:\WINDOWS\system32\DRIVERS\VBoxNetLwf.sys (Version: 6.1.22.44080)
00:00:00.170637            C:\WINDOWS\system32\DRIVERS\VBoxUSBMon.sys (Version: 6.1.22.44080)
00:00:00.171345            C:\WINDOWS\system32\DRIVERS\VBoxDrv.sys (Version: 6.1.22.44080)
00:00:00.172502            C:\WINDOWS\system32\DRIVERS\VBoxNetAdp6.sys (Version: 6.1.22.44080)
00:00:00.197605          Loading settings file "C:\Users\[redacted]\.VirtualBox\VirtualBox.xml" with version "1.12-windows"
00:00:00.203839          usbLibGetDevices: Starting USB device enumeration
00:00:00.204211          Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 8
00:00:00.204381          Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 9
00:00:00.205948          Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 11
00:00:00.206068          Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 12
00:00:00.206193          Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 14
00:00:00.211071          usbLibGetDevices: Found 6 USB devices, 0 captured
00:00:00.211650          USB: Unknown USB device detected (idVendor: 0x04f2, idProduct: 0xb614)
00:00:00.211887          USB: Unknown USB device detected (idVendor: 0x04f2, idProduct: 0xb615)
00:00:00.212224          USB: Unknown USB device detected (idVendor: 0x06cb, idProduct: 0x009a)
00:00:00.212316          USB: Unknown USB device detected (idVendor: 0x8087, idProduct: 0x0aaa)
00:00:00.450959          HostDnsMonitor: initializing
00:00:00.459093          HostDnsMonitor: updating information
00:00:00.459157          HostDnsMonitor: old information
00:00:00.459158            no server entries
00:00:00.459158            no domain set
00:00:00.459159            no search string entries
00:00:00.459159          HostDnsMonitor: new information
00:00:00.459160            server 1: 216.104.96.22
00:00:00.459160            server 2: 216.104.98.222
00:00:00.459161            no domain set
00:00:00.459161            no search string entries
00:00:00.519722          VD: VDInit finished with VINF_SUCCESS
00:00:00.535992          Loading settings file "C:\Users\[redacted]\VirtualBox VMs\Pop OS\Pop OS.vbox" with version "1.16-windows"
00:00:00.540586          VirtualBox: object created
00:00:02.717297          Saving settings file "C:\Users\[redacted]\.VirtualBox\VirtualBox.xml" with version "1.12-windows"
00:00:02.749788          Saving settings file "C:\Users\[redacted]\.VirtualBox\VirtualBox.xml" with version "1.12-windows"
00:00:06.912339          Launched VM: 72761152 pid: 8920 (0x22d8) frontend: GUI/Qt name: Pop OS
00:00:15.343190          ERROR [COM]: aRC=VBOX_E_OBJECT_NOT_FOUND (0x80bb0001) aIID={70401eef-c8e9-466b-9660-45cb3e9979e4} aComponent={ExtPackManagerWrap} aText={No extension pack by the name 'Oracle VM VirtualBox Extension Pack' was found}, preserve=false aResultDetail=0
00:00:15.946779          ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={85632c68-b5bb-4316-a900-5eb28d3413df} aComponent={SessionMachine} aText={Saved screenshot data is not available (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=-37
00:00:18.035932          Added USB filter (ID=1, type=4) for device FFFFFFFF:FFFFFFFF rev FFFFFFFF, c/s/p FFFFFFFF/FFFFFFFF/FFFFFFFF, Manufacturer=`<null>' Product=`<null>' Serial=`<null>'
00:01:33.808197 USBPROXY usbLibGetDevices: Starting USB device enumeration
00:01:33.808536 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 8
00:01:33.808658 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 9
00:01:33.809978 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 11
00:01:33.810149 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 12
00:01:33.810308 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 14
00:01:33.810725 USBPROXY usbLibGetDevices: Found 6 USB devices, 0 captured
00:01:56.286251 USBPROXY usbLibGetDevices: Starting USB device enumeration
00:01:56.289545 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 8
00:01:56.289748 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 9
00:01:56.291488 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 11
00:01:56.291683 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 12
00:01:56.291863 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 14
00:01:56.292343 USBPROXY usbLibGetDevices: Found 7 USB devices, 0 captured
00:02:13.103704 USBPROXY usbLibGetDevices: Starting USB device enumeration
00:02:13.111126 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 9
00:02:13.112099 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 11
00:02:13.115809 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 14
00:02:13.115976 USBPROXY usbLibGetDevices: Found 8 USB devices, 0 captured
00:03:07.740888 USBPROXY usbLibGetDevices: Starting USB device enumeration
00:03:07.744347 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 8
00:03:07.744406 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 9
00:03:07.745541 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 11
00:03:07.745629 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 12
00:03:07.745727 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 14
00:03:07.747071 USBPROXY usbLibVuDevicePopulate: Found VBoxUSB on `\\?\usb#vid_80ee&pid_cafe#000000001532#{00873fdf-cafe-80ee-aa5e-00c04fb1720b}' (rc=0)
00:03:07.747179 USBPROXY usbLibGetDevices: Found 9 USB devices, 1 captured
00:03:07.748438 USBPROXY Added USB filter (ID=2, type=1) for device 05E3:0749 rev 1532, c/s/p 00/00/00, Manufacturer=`Generic' Product=`USB3.0 Card Reader' Serial=`000000001532'
00:03:08.374409 USBPROXY usbLibGetDevices: Starting USB device enumeration
00:03:08.377980 USBPROXY usbLibDevGetHubPortDevices: No DriverKey on hub USB#VID_05E3&PID_0610#5&122ba5a1&0&7#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 1
00:03:08.377991 USBPROXY usbLibDevCfgDrGet: IOCTL_USB_GET_DESCRIPTOR_FROM_NODE_CONNECTION #1 failed (dwErr=433) on hub USB#VID_05E3&PID_0610#5&122ba5a1&0&7#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 1
00:03:08.378045 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 8
00:03:08.378086 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 9
00:03:08.379176 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 11
00:03:08.379222 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 12
00:03:08.379267 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 14
00:03:08.893296 USBPROXY usbLibGetDevices: Found 10 USB devices, 0 captured
00:03:08.893344 USBPROXY USB: Unknown USB device detected (idVendor: 0x0000, idProduct: 0x0000)
00:03:13.136358 USBPROXY usbLibGetDevices: Starting USB device enumeration
00:03:13.136513 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 2
00:03:13.141638 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 8
00:03:13.141707 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 9
00:03:13.142874 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 11
00:03:13.142948 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 12
00:03:13.143018 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 14
00:03:13.144808 USBPROXY usbLibGetDevices: Found 10 USB devices, 0 captured
00:03:14.104978 USBPROXY usbLibGetDevices: Starting USB device enumeration
00:03:14.105279 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 2
00:03:14.109010 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 8
00:03:14.109135 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 9
00:03:14.110525 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 11
00:03:14.110703 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 12
00:03:14.110828 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 14
00:03:14.112946 USBPROXY usbLibGetDevices: Found 10 USB devices, 0 captured
00:03:19.120960 USBPROXY usbLibGetDevices: Starting USB device enumeration
00:03:19.121366 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 2
00:03:19.125498 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 8
00:03:19.125712 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 9
00:03:19.127312 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 11
00:03:19.127514 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 12
00:03:19.127697 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 14
00:03:19.130681 USBPROXY usbLibGetDevices: Found 10 USB devices, 0 captured
00:03:28.981098 USBPROXY usbLibGetDevices: Starting USB device enumeration
00:03:28.981520 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 2
00:03:28.986837 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 8
00:03:28.987047 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 9
00:03:28.989362 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 11
00:03:28.989570 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 12
00:03:28.989754 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&20caf07&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 14
00:03:28.993235 USBPROXY usbLibGetDevices: Found 10 USB devices, 0 captured
00:03:46.043498          Removed USB filter ID=1
00:03:46.070474          Saving settings file "C:\Users\[redacted]\VirtualBox VMs\Pop OS\Pop OS.vbox" with version "1.16-windows"
00:22:25.373987          Saving settings file "C:\Users\[redacted]\.VirtualBox\VirtualBox.xml" with version "1.12-windows"
00:22:25.398933          Saving settings file "C:\Users\[redacted]\.VirtualBox\VirtualBox.xml" with version "1.12-windows"
00:22:25.403933          Saving settings file "C:\Users\[redacted]\.VirtualBox\VirtualBox.xml" with version "1.12-windows"
00:22:30.937153 main     VirtualBox: object deletion starts
00:22:30.937253 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={ad47ad09-787b-44ab-b343-a082a3f2dfb1} aComponent={MediumWrap} aText={Medium 'C:\Users\[redacted]\VirtualBox VMs\Pop OS\Pop OS.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:22:30.937915 main     HostDnsMonitor: shutting down ...
00:22:30.937984 main     HostDnsMonitor: shut down
00:22:30.940816 Watcher  ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={d0a0163f-e254-4e5b-a1f2-011cf991c38d} aComponent={VirtualBoxWrap} aText={The object is not ready}, preserve=false aResultDetail=0
00:22:30.940984 main     VirtualBox: object deleted
HLR
 
Posts: 5
Joined: 15. May 2021, 19:00

Re: Fatal error (blue screen of death) when starting VM

Postby sarj » 22. Jun 2021, 19:46

I have virtually the exact same log as above. just need better guidance and hoping to find it here. Is there a fix for this? it really seems prevalent to any installation where USB is added, removed, or switched and the manager is opened.

I have the manager opened and when i switch on my KVM to another machine - as soon as i switch back CRASH!!!...

i have done all M$ recommends, all that forums recommend and it is just a continual thing that is documented for ages with VB. I have to believe that there is a fix that doesnt include moving to VMWARE.

That is a bit of a rant but i guess i am trying to figure out if i need to move from Windows and VB to another host OS or to VMWARE.

But for sure - on windows it is a crash guaranteed if i disconnect USB and expect to come back and not spend a large chunk of time rebooting.
sarj
 
Posts: 2
Joined: 22. Jun 2021, 19:35

Re: Fatal error (blue screen of death) when starting VM

Postby scottgus1 » 22. Jun 2021, 19:50

sarj, without any troubleshooting info there is nothing we will be able to do for you.

Please start a new topic, and provide the diagnostic info asked for above in your new topic.
scottgus1
Site Moderator
 
Posts: 12447
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Fatal error (blue screen of death) when starting VM

Postby sarj » 22. Jun 2021, 21:03

scottgus1 wrote:sarj, without any troubleshooting info there is nothing we will be able to do for you. Please start a new topic, and provide the diagnostic info asked for above in your new topic.


I will fire off a new topic another time but for now i went ahead and performed same tests as was previously mentioned in this thread; removing all usb. No more time spent on M$ telling me its a driver issue in vbox or sending minidumps i just removed every USB device from my system.

If i have everything connected and launch the VB manager it works fine, launch the session it works fine, work in session and close session and the close manager - all work fine. But have manager up and as soon as duty calls and i need to switch computers - i press button on the KVM, do my work and then switch back to VB host... CRASH! However if I close VB Manager before switching i can switch back and forth from all my computers with no issue. Leave it VB Manager open and it is a confident BSOD

VB doesnt play nice with USB hubs or KVM switches. So - I will need to do more testing. In the end virtualbox does not like anything that functions as a hub for usb devices. Neither the host or the session have issue with USB - only VB Manager has problem with it.

thanks for the poke and the good notes above.
sarj
 
Posts: 2
Joined: 22. Jun 2021, 19:35


Return to VirtualBox on Windows Hosts

Who is online

Users browsing this forum: No registered users and 20 guests