VirtualBox.exe crashes VBoxSvc.exe on startup -> fixed in SVN/2.0.4

[kookyman]

After installing v2.0.2 (does not happen with 1.6.2-6, 2.0.0), VirtualBox.exe seems to be crashing VBoxSVC on startup.

If I go straight to VirtualBox.exe, I get a Debug Dialog indicating VBoxSVC has had an unhandled exception, and offers to debug (I have VS2008 installed). After saying no to debugging, I am then prompted with a critical error from VirtualBox as it is unable to create a COM Object. Error: "Callee RC: CO_E_SERVER_EXEC_FAILURE (0x80080005)"

I am pretty sure that it isn't VBoxSvc crashing on its own as I can manually start VBoxSvc from the command line and it runs stable until VirtualBox or VBoxSDL is started, at which it crashes immediately.

I Uninstalled 166, installed 202, and had the crash. I then uninstalled 202 and installed 200, worked just fine. Upgraded (Installed over) back to 202 and its crashing again. Uninstalled 202 and deleted the three left over drivers in Win\System32, then rebooted installed, rebooted and tried and crashed.

I was in the chat room earlier trying to troubleshoot the issue and there was another individual with the exact same issue. This makes VBox 2.0.2 completely unusable.

TEMPORARY SOLUTION See ​below.

[Onii]

I have the exact same problem (I even tried pretty much the same steps with same results).

However I noticed that it happens only as non administrator (even when user is in "power users" group). With administrator account everything works as usual.

My operating system is XP 64bit using AMD64 version of virtualbox.

[Robert Gesswein]

My problem may be related. Just installed 2.0.2 and on my system VboxSvc.exe keeps taking up more and more CPU. Starts at about 7% and works its way up to about 40% before I give up and reboot the host. Did not happen with 2.0.0 so I've rolled back.

Note that even with all virtual machines closed the VboxSvc.exe CPU keeps increasing.

[Stephan Wiechert]

I have the exact same problem (I even tried pretty much the same steps with same results).

And I am agree with Onii, it happens only with non administrative accounts.

Hope this will be fixed soon, I don't want to start VirtualBox as an administrator and the further versions solved this fine.

My operating system is XP 64bit using AMD64 version of virtualbox.

[Sander van Leeuwen]

Are all of you using XP 64? (rgesswein & kookyman)

[Robert Gesswein]

I'm running a Vista 32bit host (on an Intel laptop). Maybe that's why I'm not getting the full crash?

[tomc]

Memory leak in VBoxSVC under 32bit Vista, about 4MB/min - even without starting any virtual machine. UAC enabled, running VirtualBox with administrative rights. Works fine on 2.0.0 version.

No problems with 2.0.2 under OS X 1.5.4

[Sander van Leeuwen]

Please discuss the memory leak in ticket #2242.

[Xen0]

Error message when attempting to start VirtualBox on Vista 32 bit

[Xen0]

I get this with a fresh install of VirtualBox 2.0.2 on a new user account in the Administrator group (Vista 32-bit), even if I deliberately exclude the USB support.

(I cannot "not use" USB on the host, because my keyboard and mouse are USB-only).

I've been using 1.6.2 on the same machine since July with no problems whatsoever.

[kookyman]

I'm using XP 32Bit on AMD Opteron 185 processor. (Dual Core 64Bit)

I am however running into this problem with an Administrative account, not a limited account unlike many others.

[bunn]

I have this same error. I have XP x64 sp2. I am running the default administrator account in Windows. I recently added two host networking interfaces and bridged them, they disappeared when I updated to v2.02 from v2.0.

Another thing I noticed, I recently had an external USB HDD (I haven't had it plugged in during the VM being on though). I found this post which may be related: ​http://www.virtualbox.org/ticket/1373

[Rob]

I am having the same issue with the AMD64 version of VirtualBox 2.0.2 However, I do not have any USB devices attached.

It will only run under administrator user credentials, which is unworkable for me.

My OS is 64-bit XP, and CPU is AMD Athlon64 x2 4800

Same variations of un/re/install attempted and with/without installing the USB component.

[kookyman]

Oh, I should add that I do have an hostif, but it was obviously removed during the upgrade/installs. It really shouldn't matter though as I've also removed all my machine configs and disks. I also removed my VirtualBox config from my user\.virtualbox directory to make it not look for anything but still no change.

[john simmons]

I have the same issue on XP64 (Phenom 9850, 8GB RAM, no USB devices plugged in). I went from 1.64 to 2.02.

[k776]

I'm getting the same issue with 2.0.2 (upgraded from 1.6.2).

Intel Centrino Duo 2GHz 2gb ram

Will have to use 2.0.0. What a shame :(

[k776]

Hmm, I might have to wait a while. I'm getting the error on 2.0.0 as well. Downgrading to 1.6.6 for now. Hopefully a patch release will be available soon (I'm looking forward to 2.0.x).

(by the way, I'm on Windows XP SP3, and I downloaded the 2.0.2 and 2.0.0 x86 packs)

[Frank Mehnert]

k776, please could you ensure to 100% that this crash happens with 2.0.0 as well? That is, uninstall the previous version completely, reboot and install 2.0.0. The check if you still observe these crashes (many others report they don't).

All: Are you sure that this crash does not happen with 2.0.0? And are you sure that this crash does not happen if you start VBoxSVC.exe manually?

[Xen0]

2.0.0 starts normally for me, it does not crash. How should I start VBoxSVC.exe "manually"?

[Frank Mehnert]

Manual start means to start the VBoxSVC.exe application from c:\program files\sun\xVM VirtualBox\VBoxSVC.exe. The next step is to start the VirtualBox.exe application from the same directory. Does it crash if you just start the GUI?

[Sander van Leeuwen]

Just start VBoxSVC.exe from the command line of Windows Explorer. kookyman mentioned VBoxSVC doesn't crash when launched separately; only when a client (VirtualBox.exe or VBoxSDL.exe) connects.

[Onii]

I always upgraded to the new versions when they were released (i.e. just installed over the old version). I went from 1.6.4 to 2.0.0 without any problems. 2.0.0 to 2.0.2 the problem showed up. Deinstalled 2.0.2 and reinstalled, problem remains. Deinstalled 2.0.2 and reinstalled 2.0.0, no problem at all. I rebooted several times, though I can't tell if it was before the last 2.0.2 install; I might try that again, as well as starting VBoxSVC, when I come home later.

[bitsfritz]

Replying to frank:

..

All: Are you sure that this crash does not happen with 2.0.0?

Can confirm

And are you sure that this crash does not happen if you start VBoxSVC.exe manually?

This one too

Celeron M 1150 WinXP Home SP1

[Onii]

Ok, I did now a complete deinstall of 200, rebooted, removed three leftovers in system32/drivers, installed 202, login as non-administrator -> crash. Manually starting VBoxSVC is possible (checked with taskmgr), but it crashes when starting VirtualBox.exe. Using "runas" command to start Virtualbox.exe as administrator works flawlessly (no need to start anything manually). Now back to 200, since this works.

[Xen0]

Starting VBoxSVC.exe manually works, but as before, and it continues to run until I start VirtualBox.exe, which then crashes exactly as before.

And this happens even when running logged in as Administrator, or otherwise.

[R. Jengsuebsunt]

More info from Event Viewer Application Log:

Faulting application VBoxSVC.exe, version 1.0.0.1, time stamp 0x48ca747a, faulting module VBoxSVC.exe, version 1.0.0.1, time stamp 0x48ca747a, exception code 0xc0000005, fault offset 0x000c43ad, process id 0x16ec, application start time 0x01c91888d80d1532.

Log Name: Application Source: Application Error Date: 17/09/2008 12:47:18 Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: Lek-M1330 Description: Faulting application VBoxSVC.exe, version 1.0.0.1, time stamp 0x48ca747a, faulting module VBoxSVC.exe, version 1.0.0.1, time stamp 0x48ca747a, exception code 0xc0000005, fault offset 0x000c43ad, process id 0x16ec, application start time 0x01c91888d80d1532. Event Xml: <Event xmlns="​http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2008-09-17T05:47:18.000Z" /> <EventRecordID>11294</EventRecordID> <Channel>Application</Channel> <Computer>Lek-M1330</Computer> <Security />

</System> <EventData>

<Data>VBoxSVC.exe</Data> <Data>1.0.0.1</Data> <Data>48ca747a</Data> <Data>VBoxSVC.exe</Data> <Data>1.0.0.1</Data> <Data>48ca747a</Data> <Data>c0000005</Data> <Data>000c43ad</Data> <Data>16ec</Data> <Data>01c91888d80d1532</Data>

</EventData>

</Event>

[kookyman]

Just tried it, and I'm now running with 2.0.2+Test files.

Hope it works for everyone else!

[Sander van Leeuwen]

Could you execute comregister.cmd in the VBox directory?

[Sander van Leeuwen]

Ok, that's probably not going to work. I'll rebuild the binaries tomorrow.

[Sander van Leeuwen]

kookyman. Sorry, deleted you comment by accident. Got rid of the urls to the fix. Wait until tomorrow please.

[kookyman]

Sandervl73 -

Earlier I tried that test case and was able to start VirutalBox. Just now I actually tried to /use/ VirutalBox and its unusable. Almost everything I do comes up with failure message of ClassNotReg. Here is the exact dialog box: (Not attached so its easier to reference)

Box Description: VirtualBox-Error Text: <Red X Icon> Failed to create a new session. Textbox: Callee RC: REGDB_E_CLASSNOTREG (0x80040154)

This pops up when I try to:

• Start a Guest VM
• Go into the settings for a VM
• Release a CD Image (Removal Works on non-assigned)
• Release a HD Image (Removal Works on non-assigned)

I can create a new VM, but can not change it afterwords. I also can't delete VMs.

While the testcase files may solve the problem of being unable to start VirtualBox, it doesn't appear to make VirtualBox usable.

(Comment re-added due to accidental deletion)

[Sander van Leeuwen]

Attempt nr 2; you can download replacement files for VBoxSVC.exe & VBoxC.dll:

• ​Win32 version.
• ​Win64 version.

They fix the following:

• memory leak in VBoxSVC.exe
• startup delay when starting VirtualBox
• the startup crash mentioned in this defect.

Copy both files to "Program Files\Sun\xVM VirtualBox". Make a backup copy of the old ones first. In Vista you need admin privileges to replace them.