VBoxSVC/VirtualBox startup problems - Hangs - related to bug #2212?

[pdrg]

First time after a machine reboot, running VirtualBox works fine, but the second time onwards although VirtualBox and VBoxSVC processes start in Task Manager, the application never starts up. VBoxSVC seems to sit at about 25% of my processor useage, VirtualBox itself at 0%. Killing the VBoxSVC processes brings up the same error as in bug # 2212 ​http://vbox.innotek.de/attachment/ticket/2212/VirtualBox_2.0.2_critical_error.jpg

Callee RC: CO_E_SERVER_EXEC_FAILURE (0x80080005)

I've attached a few log files, they are all pretty similar but may contain useful details?

[pdrg]

Log3 bug #4975

[pdrg]

Logfile 2 - bug #4975

[pdrg]

For reference, machine is running Vista 32-bit Hme Professional, and I can repro in v3.04 and v3.06 of Virtualbox (an upgrade didn't fix the problem)

[Technologov]

hmmm... really strange one. To me, it looks like you have some conflicting software/driver. We need to find out what is it.

I have two hosts similar to yours, and VBox works fine on both.

Host1: Windows Vista Home Premium 32-bit, Intel Core 2 P8600, VBox 3.0.10.

Host2: Windows 7 Ultimate 64-bit, Intel Core 2 Q6600, VBox 3.1.0-BETA2.

My recommendation: Go to device manager->View->Show hidden devices, and try to disable those that are related to other installed software.

-or-

Go to Add/Remove programs, and try to uninstall conflicting software. (I don't know what it is. It may be some system software or some Anti-Virus.)

Do this only if you have installers, so you can re-install it later.

I bet that if you install a new Vista OS (without installing drivers or software on it), VBox will work. You can dual-boot. (old Vista + new Vista)

-Technologov, 24.11.2009.

[pdrg]

Cheers for the tips, and sorry it's taken me so long to respond - so far 3.08 seems ok, and shortly about to upgrade to 3.0.12, will keep you updated if I suss it out :-)

PS - made me giggle - I thought of the Vista dual-boot, then immediately thought "I know, I'll run it on a VM instead..." :-$

[oneuser]

I also have the same problem. Build 3.1.2-56127, Host Win 7 Pro, Core 2 Duo

VBox starts fine once, but if I close it up it doesn't start again. If I reboot, I can start it again, but after closing it won't start a second time, no matter how later I try. Both VirtualBox.exe and VBoxSVC.exe start, but the SVC service remains at 50% (I have a dual core CPU, so this is equivalent to 100% CPU) and the GUI doesn't initialize. I have tried killing both processes, if I kill VBoxSVC.exe I get the error described above, if I kill VirtualBox.exe nothing happens (the other process stays at 50% CPU). Have also tried to repair, the same. The system is clean, no trials/crapware... etc.

[oneuser]

Issue solved for me, it was something about the sound. If another application was using the soundcard then VB wouldn't start. If I close all the sound playing apps, everything works.

[Hanspeter232]

I had the same Problem and i could solve it by closing all Programs that have Sound-Output (e.g. Winamp). It is reproducible - everytime when there is Winamp playing, VBoxsvc.exe gets 50% CPU Load and VirtualBox wont open (After VBoxsvc.exe is started, it is no Problem with palying Sound in Winamp).

[Hanspeter232]

I forget my System-Details: Virtualbox-Version: 3.1.2 r56127 OS: Win7 Pro x64 CPU: Amd Athlon 64 X2 5600 Winamp: v5.572

[Adam Lamers]

Replying to Hanspeter232:

I had the same Problem and i could solve it by closing all Programs that have Sound-Output (e.g. Winamp). It is reproducible - everytime when there is Winamp playing, VBoxsvc.exe gets 50% CPU Load and VirtualBox wont open (After VBoxsvc.exe is started, it is no Problem with palying Sound in Winamp).

Wow, glad you found this. It's completely true. I closed Windows Media Player, (using vBox 3.1.4r567640 on 32-bit Vista Home Basic) and the app started up nearly instantly. Wonder what the problem is.

[Frank Mehnert]

Hmm, so probably the sound output needs adaption to Vista and Windows 7...

[Ted]

Reproduced on Windows 7 x64 using version 3.2.8 r64453. Using an HP 8540w, the issue only occurs while using an external sound card: SIIG SoundWave.

[gencha]

I am experiencing this same issue on 4.1.6. Closing "audio-related" application did not help for me. I had to switch the default audio output device in Windows to another device to get VirtualBox to start.

[aeichner]

Please reopen if still relevant with a recent VirtualBox release.