Can't connect usb devices

[hakahme]

I've updated from 4.2.16 to 4.2.18, including extension pack. Host: Windows 8 pro, all updates up to 11.09.2013 Guests: Several, the problem exists at least with W7/32bit and W8/64bit If I attach any well-known usb device (stick, disk...) the host crashes (blue screen). A reset does not suffice - it takes a cold start to get going again. This didn't happen with version 4.2.16.

[Aleksey Ilyushin]

When Windows crashes it writes a minidump file. Could you please locate it in C:\Windows\Minidump and upload it to ​Oracle FTP server?

[jbeta]

I am having this issue too. ​https://forums.virtualbox.org/viewtopic.php?f=6&t=57410 let me know if you would like any information from me.

[Aleksey Ilyushin]

Please try this ​test build.

[jbeta]

I tried build 89379 twice. first attempt, usb flash drive attach did not cause host to crash initially, but guest would not see it. i tried again and it said device busy. I shut down the VM (I think) and then physically removed the still non-responsive drive, and the host crashed.

Second attempt: attach device, nothing happens. check the device menu->usb devices, and the VM freezes and looses all responsiveness. X-Close button doesn't even work. Tried to shut down the host, and it crashed again (with usb drive still attached).

hope this helps. I'm going back to 4.2.16 for now. -Jason

P.S. I uploaded logs and dumps to the oracle ftp server

[Aleksey Ilyushin]

Thank you for the logs and dumps, Jason. You can try ​test build 89545. While it won't make problematic devices to appear in guests, it should prevent host crashes. It also enables debug printouts that can be captured by debugview. Please take a look at #12119.

[jbeta]

Replying to aleksey:

Thank you for the logs and dumps, Jason. You can try ​test build 89545. While it won't make problematic devices to appear in guests, it should prevent host crashes. It also enables debug printouts that can be captured by debugview. Please take a look at #12119.

Thanks, I have not tried 89545, but I would like to report I am not seeing the problem in the 4.3.0 release build 89960. I am running windows 8.1 now though, for what it may be worth.

EDIT: Of course, I am not the OP on this bug, but had a similar configuration (Windows 8 Pro x64 VB4.1.18 at the time)

[aeichner]

Please reopen if still relevant with a recent VirtualBox release.