VM VirtualBox Manager has stopped working

[gwardell]

Hi,

I'm getting this error in the VM VirtualBox Machine Manager when shutting down a guest machine.

I am able to reproduce this.

The guest machine is stand alone in a workgroup with bridged networking.

Both guest and host are Windows 7 Professional SP 1.

The guest is a new install. I also recently upgraded VB to 4.2.18 r88780.

VB used to run good on this host.

Any ideas on what is going on.

Problem signature:
Problem Event Name: APPCRASH
Application Name: VirtualBox.exe
Application Version: 4.2.18.0
Application Timestamp: 5229dc13
Fault Module Name: QtGuiVBox4.dll
Fault Module Version: 4.8.4.0
Fault Module Timestamp: 51cc7be7
Exception Code: c0000005
Exception Offset: 00173e13
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

[noteirak]

Please read Minimum information needed for assistance.
Also, you say it used to run good. What changed since then? What did you install/remove/change?

[gwardell]

Actually two things changed.

I upgraded the MB and then I upgraded Virtual Box to 4.2.18.

Ok, just got another crash:

Problem signature:
Problem Event Name: APPCRASH
Application Name: VirtualBox.exe
Application Version: 4.2.18.0
Application Timestamp: 5229dc13
Fault Module Name: QtGuiVBox4.dll
Fault Module Version: 4.8.4.0
Fault Module Timestamp: 51cc7be7
Exception Code: c0000005
Exception Offset: 00173e13
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789


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

Windows 7 Professional SP1 32bit
Virtual Box 4.2.18 r88780
Virtual Box Ext 4.2.18r88780 - How do I tell if it's installed in the guest?

Guest
Windows 7 Professional SP1 32bit

Both host and guest are members of a domain.

The error happens after shutting down the guest and the guest window closes.

-----------------

Host Information:

Host time: 2013-11-01T02:47:20.015000000Z
Processor online count: 6
Processor count: 6
Processor#0 speed: unknown
Processor#0 description: AMD FX(tm)-6300 Six-Core Processor
Processor#1 speed: unknown
Processor#1 description: AMD FX(tm)-6300 Six-Core Processor
Processor#2 speed: unknown
Processor#2 description: AMD FX(tm)-6300 Six-Core Processor
Processor#3 speed: unknown
Processor#3 description: AMD FX(tm)-6300 Six-Core Processor
Processor#4 speed: unknown
Processor#4 description: AMD FX(tm)-6300 Six-Core Processor
Processor#5 speed: unknown
Processor#5 description: AMD FX(tm)-6300 Six-Core Processor
Memory size: 3320 MByte
Memory available: 2561 MByte
Operating system: Windows 7
Operating system version: 6.1.7600

Host & Guest make and version including 32 or 64 bit, and the amount of memory available to both.
Guest log file (as an attachment)

[noteirak]

Did you uprgade your drivers to the latest version after changing your MB? The faulty module is related to Qt, so graphical issue.

[gwardell]

Yes and no. It's using the same video card and other peripherals. I had thought about reinstalling the OS and how traumatic that is.

Does Virtual Box use Quicktime?

I don't use Quicktime for anything. Could I uninstall it?

[gwardell]

Ok, I updated QT and rebooted the host.

Started the guest, waited for it to settle down, and then shutdown the guest. I didn't log on.

And it still crashed.

[noteirak]

QT doesn't stand for Quicktime but for the Qt framework.

If you didn't reinstall the OS, you should at least uninstall then reinstall Virtualbox and see if it makes any difference.

[gwardell]

I installed this version of Virtual Box AFTER changing the mother board. And I've also tried reinstalling this version of Virtual Box.

The next step is to try repairing the OS installation.

I'm wondering if this version of Virtual Box is stable on Windows 7 32 bit?

I relay love Virtual Box and am using it in my business for testing and development, but having it crash is not nice.

Is it possible to purchase a support contract?

Can you tell from the logs if the problem is in the guest or the VB manager?

If I end up reinstalling the host OS, I'm thinking to go with a 64 bit version. Is VB stable with a Windows 7 64 bit host?

[noteirak]

Virtualbox is stable on Windows 7 32 & 64 bits. I am more under the impression that something went wrong on your OS when you switched hardware without reinstalling.
I don't know if a support contract alone is possible, but you would find more info on the Oracle website, Virtualbox part (but not the direct virtualbox site!)
The problem is in the VB manager, but your guest seems fine. The crash happens AFTER the VM has finished running.

[gwardell]

Hi,

I think I solved it.

I did a setup recovery and a SysPrep and still it crashed. I setup a new guest and it still crashed. However, I have a DOS guest that doesn't crash.

But I noticed that in the guest the base system device was missing a driver. So I investgated that a bit but didn't find anything. So I figured that if the guest was ok I'd just continue with it.

In the process of setting up the new guest I was checking out the various settings and information the manager displayed and I notice it said the guest additions weren't installed. I thought I had installed them. So I did it again. Now when I looked the base system device driver was there and when I wet to the manager it said the guest additions were detected. And now it don't crash.

I still think I'll go with the 64bit OS later, when I have time to set it up.

Thanks for the help and guidence and for answering my questions.

Gary

[gwardell]

Hi,

Ok, I'm back.

I installed a fresh copy of Win7 64 on the host in a new partition. No upgrades.

I installed Virtual Box 4.2.16 and the corresponding Extension Pack.

I then created a Virtual Machine for Windows 7 64 bit win NAT networking and installed Windows 7 x64 sp1 on it.

I installed the corresponding Guest Additions

I installed all of the windows updates and was preparing the machine as a base machine for future clones.

When I thought it was all ready I shut down the guest machine and changed the network to Bridged.

The network stopped working. I played around with it a lot trying to get it to work. Switching back to NAT it would always work. In bridged it wouldn't. I then noticed that in Device Manager there was a device with no driver now. I installed the Guest Additions ( I think I did it before but I did it again ) The missing driver was found. But still the networking didn't work. I tried removing the network adapter and letting it reinstall. Magic. The bridged networking started working. I could ping the router, and the host and the host could ping me.

However, when I shut down the guest after this the Virtual Box Manager crashed with that same error, c0000005. And when I restart the guest after this the bridged networking fails to work. NAT still does though. And shutting down and restarting works; until I remove and reinstall the network adapter, then the bridged networking works, and shutting down crashes. and the cycle repeats.

I've attached a log file from after a crash.

Problem signature:
Problem Event Name: APPCRASH
Application Name: VirtualBox.exe
Application Version: 4.2.16.0
Application Timestamp: 51d57f8d
Fault Module Name: QtGuiVBox4.dll
Fault Module Version: 4.8.4.0
Fault Module Timestamp: 51cd5a50
Exception Code: c0000005
Exception Offset: 0000000000194fcc
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 1d98
Additional Information 2: 1d985baa09ac61a81304e07bb5997ab0
Additional Information 3: caad
Additional Information 4: caad4739ddb3c92ce995416b6875470f

I've spent too much time playing with this. I'm going to try uninstalling Virtual Box and reinstalling and then creating a new virtual machine with bridged mode set at the start and then install windows and the guest additions bridged from the get go and see what happens. I need this for work and it's costing me time on a project with the dead line coming up.

[gwardell]

Hi,

Ok, uninstalled, reinstalled, new VM, new OS install, no patches as yet. Guest Additions installed.

All looked good, the bridge worked, could see the network and the networks could see me. Then it went down hill The network couldn't access the host. I have no idea why. The host only saw me and and it's self. When I shutdown the guest the VB Manager crashed. And then the network between the host and others worked again.

I bring up the guest gain and this time the bridge isn't working. It's not getting an IP from the DHCP again.

In the guest under network neighborhood I see the guest pc and VBOXSVR (whatever that is).

I go into the device manager and uninstall the network adapter. It reboots and reinstalls the network adapter. But still doesn't get the DHCP address. This time that trick doesn't work.

I went in and changed from dhcp to a static address. Now I can ping the host, but I can't ping the router that is on the same subnet. The host can ping both the guest and the router, but other machines on the lan can't ping the guest.

It really looks to me like the bridging adapter is getting corrupted somehow. This used to work good in the 32 bit version. I could live with the manager crashing if it would just work while the VM is up. It also looks to me like the crashing is related to the bridging adapter.

Unfortunately I need to access the guests from other machines on the lan so I need the bridging adapter to work.

Gary