Windows 8 host BSOD on connect USB after update to 4.2.18

[jbeta]

Hello,
I recently updated to VirtualBox-4.2.18-88780 (from 4.2.16) and now attaching a USB device to a VM is causing a blue screen, It happens instantly when i have a VM running and click Devices->USB Devices->Unknown device 13FE:3E00 [0100]
I have the latest extension pack, and have tried with usb 2.0 both enabled and disables on the guest.

The first example was an XP pro guest with guest additions, so I also tried it with another device on a DOS guest (because it has no Guest additions installed) with my galaxy nexus to verify. It still crashed.

To make things more complicated, this months windows updates were installed around a similar time, so I'm not sure if that could be the source of the problem instead.

Since it happens so fast I'm not sure there is much in the log to help, but there are a few lines that might be relevant. I currently have windows dumps disabled I believe so i don't have any data there yet.

Anyone else have this problem recently?

EDIT: System internal specs:
Windows 8 64-bit
ASUS M5A97 R2.0 motherboard
AMD FX-4100 CPU
ATI Radeon HD 5670
8GB Corsair DDR3 RAM
ATI PCIe TV Wonder HD 750 (I think)

[noteirak]

I think the dump and the error code & message of the BSOD would help here. Not much can be done like this, since nothing will be logged in the VMs.

[jbeta]

I think the dump and the error code & message of the BSOD would help here. Not much can be done like this, since nothing will be logged in the VMs.

Yeah, I figured. I just don't like repeatedly causing "intentional" crashes. makes me nervous.
Anyway, I set it to not restart automatically and generate a "small" dump. This time i ran a Ubuntu 12.04 guest. the USB 2.0 setting was disabled (I think that might rule out the ext. pack possibly.) I was able to see the BSOD this time:
DRIVER_IRQL_NOT_LESS_OR_EQUAL (VBoxUSBMon.sys)

attaching new log and small windows dump.

[noteirak]

Since I never use the usb part myself, I will let you in the hands of the other capable mods for now

[jbeta]

Since I never use the usb part myself, I will let you in the hands of the other capable mods for now

Thanks. Its not a show stopper for me, but If I want to (for example) access my GN I have to do it through the host and workaround by copying things. Just annoying, but no huge deal for me, because I know how to work around it. I just thought it might be pretty significant if anyone else is having the problem.

[mpack]

I really doubt that a USB related host BSOD on a Windows host actually has anything to do with VirtualBox - otherwise we would be seeing a lot more reports like this. Probably some dodgy USB driver in the host which doesn't interact well with others.

[Versus]

Having the same exact problem as the poster with a Canon printer attached. Had to downgrade to 4.2.16 for it to work again.

[jbeta]

Having the same exact problem as the poster with a Canon printer attached. Had to downgrade to 4.2.16 for it to work again.

Confirmed. I just downgraded to 4.2.16 and the issue does not happen in that release. Are you alos on Windows 8?

As for dodgy host USB drivers, I have tried several devices with the same results. I can't rule out a change in Windows drivers from this months update (until i look through each KB article...), but clearly 4.2.16 works, and 4.2.18 does not. for at least 2 people so far. Also, I don't regularly use that feature, maybe once a week, and I Imagine there are others experiencing it, just not a big enough deal to say anything.

I searched this forum and only found related issues in older versions a few years ago. possible regression?

I will now reinstall 4.2.18, mostly because I already have the newer guest additions in most of my VM's. I'll also install VBox on my Windows 7 host to see if it occurs there. If you need any more information let me know. Also, advise on whether I need to create a bug for this, or someone else should.

-Jason

EDIT: I just installed VBox on my Windows 7 x64 machine, and can not reproduce the error there. Maybe just Windows 8?

[jbeta]

I see several bugs for this now which are probably related:
https://www.virtualbox.org/ticket/12100

Maybe these too, but slightly different scenarios:
https://www.virtualbox.org/ticket/12096
https://www.virtualbox.org/ticket/12112

[Versus]

Having the same exact problem as the poster with a Canon printer attached. Had to downgrade to 4.2.16 for it to work again.

Confirmed. I just downgraded to 4.2.16 and the issue does not happen in that release. Are you alos on Windows 8?

As for dodgy host USB drivers, I have tried several devices with the same results. I can't rule out a change in Windows drivers from this months update (until i look through each KB article...), but clearly 4.2.16 works, and 4.2.18 does not. for at least 2 people so far. Also, I don't regularly use that feature, maybe once a week, and I Imagine there are others experiencing it, just not a big enough deal to say anything.

I searched this forum and only found related issues in older versions a few years ago. possible regression?

I will now reinstall 4.2.18, mostly because I already have the newer guest additions in most of my VM's. I'll also install VBox on my Windows 7 host to see if it occurs there. If you need any more information let me know. Also, advise on whether I need to create a bug for this, or someone else should.

-Jason

EDIT: I just installed VBox on my Windows 7 x64 machine, and can not reproduce the error there. Maybe just Windows 8?

Yep, using Windows 8 x64 here as well. The bug has already been "reported", but the guy that wrote it is using Windows 7 x64, so it's probably not just Windows 8.

[OmaSteak]

I made the post about a Brother MFC J220 USB printer producing a BSOD when enabled in a Windows XP 32 bit guest on a Windows 8 host with version 4.2.18. Downgrade to version 4.2.16 resolved the BSOD issue. My Windows 8 host system is 64 bit version.
OmaSteak

[jbeta]

I made the post about a Brother MFC J220 USB printer producing a BSOD when enabled in a Windows XP 32 bit guest on a Windows 8 host with version 4.2.18. Downgrade to version 4.2.16 resolved the BSOD issue. My Windows 8 host system is 64 bit version.
OmaSteak

I think it has something to do with USB 3.0. My Win7x64 machine worked, but it has an ASMedia USB 3.0 driver. If others have different drivers that might be an issue, but AFAIK Win 7 does not have native drivers still. Both of my mobos are ASUS M5 series, but that doesn't mean the USB controller is the same necessarily... I'll have to check. But everyone should most likely have the same Microsoft USB3 drivers in Windows 8x64, i believe.

Also, I came accross this:

https://www.virtualbox.org/changeset/48062/vbox

And I would bet good money the problem lies in there

EDIT: also its worth noting that my error was a device plugged into a USB 2.0 port. The only USB 3.0 device i have to test with is my backup HDD. I'm not gonna do that, but I might test the port anyway.

[Versus]

I'm using Etron's USB 3.0 drivers, not Microsoft's. But the situation was same as yours, my printer was connected to a USB 2.0 port when the BSOD hit. Only the mice is connected to a USB 3.0 port, nothing else.

[Tele]

I have the same problem. 4.2.16 worked and all versions before that, but not this new one. My problematic driver is a most common USB Mass Storage Device (an SD card reader) with a Microsoft driver (driver date 6/21/2006 ver:6.1.7601.17577)
If I unplug that device, it works again, no BSOD anymore. Unfortunately I need that device, because I write SD cards on linux guest.
In this topic people have different USB devices, they worked in the previous 4.2.16 but not in 4.2.18 , that's a common symptom
Most probably the problem is in vboxusbmon.sys
What was changed in that driver ?
EDIT:
I forgot to say I have Win7x64 host and Linux x64 guest

[mpack]

This discussion and all of the "me too" stuff should be happening in the 4.2.18 release feedback topic if you want the devs to notice.