VirtualBox

Ticket #1655 (new defect)

Opened 6 months ago

Last modified 2 months ago

Critical Error when Starting in XP 32-bit

Reported by: cubsftw Assigned to:
Priority: critical Component: other
Version: VirtualBox 1.6.0 Keywords: COM object, assertion failed
Cc: Guest type: other
Host type: Windows

Description (Last modified by frank)

I've been trying to get Virtual Box versions 1.4-1.6 working on my Windows XP SP2 32-bit machine for a while with no success. I've tried the methods in the FAQ's and forums and they haven't worked (i.e.: starting VBoxSVC.exe manually). This is the error message that comes up after I try to start the program:

Virtual Box- Critical Error Failed to Create the VirtualBox COM object. The Application Will Now Terminate. 

Assertion failed at 'C:\vbox\32\w32-rel\src\VBox\Main\VirtualBoxImpl.cpp' (271) in VirtualBox::init.
Unknown exception
.
Please contact the product vendor!.

Result Code: E_FAIL (0x80004005) Component: VirtualBox Interface: IVirtualBox {2d3b9ea7-25f5-4f07-a8e1-7dd7e0dcf667} Callee RC: E_NOINTERFACE (0x80004002)

I appreciate your help in resolving this ticket.

Best Regards,

Peien Liu

Attachments

f27c_appcompat.xml (22.7 kB) - added by lwesker on 09/08/08 21:17:15.
XML file of active process detected by dwwin.
CCE714.dmp (91.5 kB) - added by lwesker on 09/08/08 21:20:30.
Dwwin dump file in binary. I couldn't capture equivalent on-screen text.
LVCOMSX.LOG (6.6 kB) - added by lwesker on 09/08/08 21:21:25.
COM related file created at same time as dump.

Change History

08/06/08 04:22:37 changed by andrei.tulai

I am also having this issue.

My problem was my external HDD. If I keep it plugged in, then attempt to run VirtualBox, I get the exact error mentioned above. If I don't have the external HDD connected, then it works perfectly. If I then try to plug in the HDD, it crashes and becomes unusable.

I am also using XP Pro SP3 32 bit. I will try this in Vista to see if there is any difference.

08/12/08 09:51:27 changed by frank

Andrei, was your external HDD a USB device? And did you set up any USB filters? cubsftw, from which version did you report the above error?

08/12/08 15:35:42 changed by andrei.tulai

Yes, the HDD was a USB device and no I didn't set up any filters. VirtualBox itself won't start up because of my HDD being connected to the computer, so unless I can set a USB filter for the HDD without the HDD being connected, there is no way for me to set a filter anyway.

Although I'm fairly sure I tried removing or making sure that no USB devices were enabled in VBox and then tried it only to get the same thing.

08/28/08 16:05:01 changed by andrei.tulai

This is not an XP only issue, nor is it a 32bit only issue. It's happening on my Vista Business 64 installation also. The error was a little different though. I will post it as soon as I get the chance.

08/29/08 05:59:55 changed by andrei.tulai

In Vista Business 64 I get:

Failed to create the VirtualBox COM object.

The application will now terminate.

Callee RC: CO_E_SERVER_EXEC_FAILURE 0x80080005

09/08/08 21:17:15 changed by lwesker

  • attachment f27c_appcompat.xml added.

XML file of active process detected by dwwin.

09/08/08 21:20:30 changed by lwesker

  • attachment CCE714.dmp added.

Dwwin dump file in binary. I couldn't capture equivalent on-screen text.

09/08/08 21:21:25 changed by lwesker

  • attachment LVCOMSX.LOG added.

COM related file created at same time as dump.

09/08/08 22:50:49 changed by lwesker

I have nearly the same problem described (the callee code is different), with the same conflict with the USB subsystem appended by "andrei.tulai". I am not sure if this should be a different ticket since the error code differs from the originator "cubsftw", but since he has not replied if his problem matches, I am assuming the ticket has evolved. This bug is still not fixed as of v2.0.0. My problem history is in forum topic:

VirtualBox fails to start, assertion failure

A fresh install of VirtualBox (with no machines and empty .VirtualBox directory) crashes on start with: 

Assertion failed at 'C:\vbox\32\w32-rel\src\VBox\Main\VirtualBoxImpl.cpp' (301)
 in VirtualBox::init.

I get more detail on the error using VBoxManage: 

C:\Program Files\Sun Microsystems\xVM VirtualBox>vboxmanage createvdi
 -filename xxx -size 64
VirtualBox Command Line Management Interface Version 2.0.0
(C) 2005-2008 Sun Microsystems, Inc.
All rights reserved.

[!] Failed to create the VirtualBox object!
[!] Primary RC  = E_FAIL (0x80004005) - Unspecified error
[!] Full error info present: true , basic error info present: true
[!] Result Code = E_FAIL (0x80004005) - Unspecified error
[!] Text        = Assertion failed at 'C:\vbox\32\w32-rel\src\VBox\Main\
VirtualBoxImpl.cpp' (301) in VirtualBox::init.
Unknown exception
.
Please contact the product vendor!
[!] Component   = VirtualBox, Interface: IVirtualBox, {557a07bc-e6ae-4520-
a361-4a8493199137}
[!] Callee      = <NULL>, {00000000-0000-0000-0000-000000000000}

C:\Program Files\Sun Microsystems\xVM VirtualBox>

As indicated by "andrei.tulai", the conflict is with having an attached USB hard drive. With the drive attached, VirtualBox fails to start. With the drive removed, all runs OK. If the USB hard drive is attached while VirtualBox is running, it immediately crashes with the Microsoft error window: 

Error signature
    AppName: vboxsvc.exe    AppVer: 1.0.0.1    ModName: vboxrt.dll
    ModVer: 0.0.0.0    Offset: 00027676

I have also attached the debug and trace files that XP would phone home to report the crash to Microsoft.

Interesting, the problem does not occur on other computers with similar attached USB hard drives. So there must still be some third party catalyst that is triggering the conflict on select systems and preventing Sun from duplicating the problem. Hopefully, I have attached enough information to finally trace the bug through a debugger and source code.

Also interesting is the problem is not all USB drives. With a 16 GB flash, the program runs, but with a 300 GB hard disk, the program fails.

09/09/08 13:57:33 changed by sflynn

I'm also having the exact same problem as lwesker above.

VirtualBox just dies when my Seagate 120gb usb drive is plugged in.

09/09/08 17:45:38 changed by lwesker

I found the problem follows the drive. I moved it to four other VirtualBox installations. In all cases, the program fails to start when the drive is attached. In my case it is a Seagate 300 GB. Maybe its a Seagate conspiracy ;-)

09/15/08 22:10:49 changed by andrei.tulai

Hmmm that's kinda funny mine is also a Seagate HDD, except it's inside a Western Digital MyBook? Case.

09/20/08 20:07:47 changed by LNRDGHN

I got this exact problem (Assertion Failed) too when trying to open VirtualBox 2.0.2. In my case it was due to my USB modem.

I reinstalled with the USB support option disabled and it starts up fine for me now.

09/21/08 00:29:40 changed by colderthanice

Also I got this problem. I have closed USB support and reinstalled. But nothing changed. It is again crashing.

09/22/08 09:01:37 changed by frank

  • host changed from other to Windows.
  • description changed.

So most people except colderthanice agree that this has something to do with USB support, right? Please could you test this with VBox 2.0.2 and attach a minidump in case VBoxSVC crashes again?

09/23/08 17:47:56 changed by lwesker

Interesting andrei.tulai, my SATA 300 GB Seagate drive causing this problem is also in a Western Digital MyBook? case. Frank, since I have rearranged my components (swapping the problem drive with a different machine at another location), it may take me a few days to pull all the pieces back together to test VBox 2.0.2.

09/24/08 06:21:52 changed by lwesker

No change with v2.0.2, except the error line number is now 306.

As mentioned earlier, the crash seems to be in vboxrt.dll. When the USB drive is disconnected, VirtualBox starts up normally. If the drive is plugged in while VirtualBox is running, it crashes. The Microsoft error box shows: 

Error signature
    AppName: vboxsvc.exe    AppVer: 1.0.0.1    ModName: vboxrt.dll
    ModVer: 0.0.0.0    Offset: 00027676

Note the offset changed from v2.0.0 which was 00027606.

Frank, please elaborate on what file and where is the "minidump" you want sent. All I could find were the Microsoft error report XML and DMP files which I already attached for v2.0.0.

09/24/08 09:24:49 changed by frank

lwesker, please check the minidump section of our FAQ. It might be that you have to enable minidumps at first.

© 2008 Sun Microsystems, Inc.
Contact – Privacy policy