virtualbox.org

Hi All.. Just installed the latest VirtualBox 3.2.2 and finding that any of my VM's that are using the Host Only Adapter VirtualBox crashes my Windows 7 Pro Host. This was not the case in VirtualBox 3.2.0 but seems to have begun with the new release. Not sure what changed with VB, but there were no changes on my system except for the VirtualBox version from 3.2.0 to 3.2.2. -Herb

System Specs:
Host: Windows 7 Pro - 2GB - VB 3.2.2
Guest: Any Windows Guest using Host Only Adapter.

Did you reboot?

Didn't have to, VB rebooted the host for me. I reproduced the issue at least 7 times before I posted. -Herb

Any error reports from Windows? Anything special about the system?
I installed in Win 7 Pro and do not have this problem.

Same problem here with the same text in BSOD, and also using HostOnly adapter. I didnt try disabling it, i just reverted back to 3.2.0
Happened many times in a row, disabling VT-x didnt help.

Log file attached, I can provide the windows dump file if needed.

The BSOD STOP message is "VMMRO.RO Address B576F7CB base at B572B000. Nevertheless, after uninstalling, rebooting, reinstalling fresh and rebooting, the same problem continues with the Host Only Adapter. In fact, on my final installation the Host Only Adapter was not created and I received an error when attempting to create one manually in the VB properties. So I've uninstalled 3.2.2 rebooted and downgraded to 3.2.0 and everything is working properly. So whatever changed in 3.2.2 isn't working on my system. As it stands, I'm staying with 3.2.0 for now.

Opened [http://www.virtualbox.org/ticket/6875 bug]

Same crash and same fix here with Win 2003 R2 Datacenter x64 as host OS

Hi, Same problem Windows 7 Ultimate x64, 8gb, vb3.2.2 Host-Only Adapter crash BSOD STOP message is "VMMRO.RO"

need to downgrade again

What is the complete version number of VirtualBox that you are using?
Note there was a problem with the June 2nd build and they put out a repaired June 3rd build. The correct build is VirtualBox-3.2.2-62321-Win.exe

Well the update seems to have done the trick. Thanks to all involved in addressing this.

Ya fix for me with vb3.2.4 thanx...