VB 4.2.18 crashes on activating usb device

[BCPete]

Just upgraded to 4.2.18 today. Using W7 host, with Ubuntu guest.

Everything worked fine for a couple of years and numerous upgrades. Now when I activate my usb device (Nexus 4) in the devices menu, the screen goes to snow, and W7 crashes.

W7 screen is all blue with message it has stopped to protect the interegty of the computer. Does as crash dump. Messages mentions VB as the source.

Repaired (reinstalled via W7), installed guest additions, still no go.

Any suggestions?

Tried rolling VB back in W7, but didn't help or seem to change the VB 4.2.18 to any earlier version.

[noteirak]

Minimum information needed for assistance.

[BCPete]

The version of VirtualBox you are using, and whether you have installed the Guest Additions (in the guest).
VB 4.2.18
installed guest additions: 4.2.18 r88780

Host & Guest make and version including 32 or 64 bit, and the amount of memory available to both.
Host: W7 ?32bit 6gb
Guest: Ubuntu 12.04 32bit 2gb

Guest log file (as an attachment) - see attachment

Peter

[noteirak]

What exact message do you actually get into the blue screen?

[BCPete]

Can't give you the exact message, only lasts ~10 sec. Then goes into reboot mode.

Seems to revert back to a "boot loader" level, fills screen with various seeming addresses in ?binary and 2 warnings. last warning mentions VBox..... at addresses [.........F ..... ]
Last item says saving some kind of dump to hard drive, and counts down while it proceeds.

I have zero familarity with W7 beyond basics. Only use it as a host for various unix type guests. If someone can point me to the correct place to find the W7 log of the screen messages, I can get there via DOS and have a look.

W7 was also upgraded yesterday, but I don't notice any issues from there. Can uninstall all the 20+ changes to eliminate that as a possibility.

Peter

[Perryg]

http://www.virtualbox.org/manual/ch12.html#idp56066128

[BCPete]

You did notice that the guest is not W7? W7 is the host. Your hyperlink is to a windows guest instruction, not a host.

[noteirak]

Then deactivate the automatic reboot of Windows on a crash, and you'll be able to see what the exact message is.

[BCPete]

from blue screen: VBoxUSBMON.sys .... address ......


W7 performs a crash dump, but I can't find the log when I use console after reboot. Not sure what I'm looking for and where. Checked log directory, nothing there with a date:time stamp or was recently modified/created.


Peter

[BCPete]

Installed Windows debugger (/petri.co.il/bsod-troubleshooting.htm & MSN pages).

Used debugger to produce output from C:\Windows\MEMORY.DMP Note had to copy to personal folder and use that as dump file source because of permissions error.

Ran !analyze -y inside debugger to get more detail. File attached.

Haven't been that intimate with Windows for over 10 yrs.

Hope the details help troubleshooting. All fingers point to VBoxUSBMON.SYS as the cause.

Let me know if there is other information I need to pull out.

Peter

[KennethB]

Just adding

I'm seeing the same problem as well

VB 4.2.18
Host W764
Guest W764

Boots fine blue screen pointing to VBoxUSBMON.sys as soon as I plug in my USB Key.

[PolarTiger]

Hello,

I was wondering if you have found a solution yet?
I am encountering the same problem since 4.2.18

When VirtualBox is running (even only the main window, not even guests) and I insert an USB device in a USB 3.0 slot the host crashes.
The screen goes dark and the computer simply reboots giving me the message windows was not shut down properly.

I have no problems when I insert the device in a USB 2 slot.

Edit:
After searching a bit on the forums I have temporarily solved this issue by downgrading to 4.2.16

Edit 2:
I decided to give VirtualBox 4.3 a swing, but unfortunately this did not resolve the problems, so back to 4.2.16...