[Solved] Host shutdown problems VB 2.2.4, guest BSOD 3.0.2

[cschales]

Dear community,

I am using VirtualBox version 2.2.4 r47978 with a Windows Vista Home Premium SP1 installation as host and Windows XP Home Edition SP3 as a guest system.

Everything runs fine except one major and two minor issues:

Major issue:
- After shutting down the virtual machine (normal shutdown or via send ACPI), the host system will hang upon its own shutdown.
- This happens in most cases and is reproducibly related to VirtualBox because it never happens if VirtualBox has not been startedn and a virtual machine run.
- I did update all drivers on my ChiliGreen model TW8 but to no avail.

Minor issues:
- Searching for updates has never worked. Despite the availability of VirtualBox Version 3.0.2. Luckily, I should say (see below).
- The connection to the virtual medium VBoxGuestAdditions.iso cannot be removed.

After reading dozens of forum contributions, I upgraded VirtualBox to version 3.0.2 which only made things worse:

- The upgrade seemed to work but after starting the virtual machine and shutting it down again, I got a blue scree in the guest.
- The BSOD cannot be viewed. The VBoxManage command to capture the information of the BSOD doesn't work (difficulties accessing the machine and drive information that is not on C: but on D:.
- The new 3.0.2 guest additions could be installed but the guest crashed nevertheless upon shutdown.
- I hat to revert to the last working snapshot losing several settings and installations that had been made in the guest because the virtual machine could only be killed and would never start up and shut down properly again.

- I then tried to uninstall VirtualBox 3.0.2 using the uninstaller. This didn't work.
- Files and registry entries had to be removed manually.
- I re-installed VirtualBox version 2.2.4 which fortunately worked.
- I re-applied all guest settings and installations that I had lost, took a snapshot and exported the virtual machine
- now everything works like before, including the issue with the shutdown of the Vista host as mentioned above.

I have tried all VirtualBox settings for the virtual machine that might have an effect (PAE/NX and 3D accelaration now deactivated, CD mapped to drive and not to ISO image. It doesn't help. The host doesn't shutdown properly in most cases.

The error logs in the Vista host show issues with WMI and the EventSystem upon unsuccessful shutdown.

Do you have any advice? Thanks in advance,

Chris

[vbox4me2]

Cook your own google like:
http://www.google.nl/search?hl=nl&q=vis ... rors&meta=
This can easely be a vista issue.

[fixedwheel]

to version 3.0.2 which only made things worse:

- The upgrade seemed to work but after starting the virtual machine and shutting it down again, I got a blue scree in the guest.
- The BSOD cannot be viewed.

hit [F8] into the booting guest, AFAIK there should be an option to turn off automatic reboot after BSOD

if its processr.sys or intelppm.sys - i have recently seen some related posts ... looks like there is an old VBox bug reactivated in 3.x http://forums.virtualbox.org/viewtopic.php?f=7&t=20089

[CodeComa]

Just want to chime in and say that I had this problem also with version 3.0.2 with Win7 host and WinXP guest. The fix above corrected the BSOD issue. Thanks for the help!

[cschales]

@fixedwheel: Thank you for the advice, I'll try it out.

The Vista host shutdown problem with the 2.2.4 installation after running and shutting down a virtual machine is meanwhile solved (more or less coincidentally):

- I had originally mapped a drive letter in the virtual machine to a host share using a batch file command "net use M: \\[host ip]\[share name] [password] /USER:[host user]" because setting up a shared folder in the "Settings" dialog of a non-running virtual machine didn't work properly.

- After an upgrade of the host Vista to SP2, this stopped working. Upon executing the "net use..." command, I received a "system error 5 access denied".

- Network settings, access rights, firewall settings etc. were all o.k. but the command wouldn't work anymore.

- I then used the "Devices - Shared folders" dialog in the running virtual machine which was successful as far as sharing goes but additionally ...

... since then, the host has been always shutting down properly without a hanging a single time.