virtualbox.org

Haven't been using VB for a little while but now everytime I want to start a VM (XP or Vista), VB crashes. Those VM machines were working fine before. The error is related with the file "nvoglv32.dll". I have try to uninstall and re-install VB but with the same effect. The strange thing is that if I uninstall the guest addons in safe mode, the VM can start again (even though they are looking for video and base drivers which It cannot find). Reinstalling the addons produce the same effect.
Was working just fine before. The only thing I've change is bumping my memory from 2 to 3GB and may be a video driver update (nvidia 8800GT)
Using VB 3.2.10r66523
Any idea ?

The video driver is the cause. The error module already states that, nvogl32.dll. That means nVidia OpenGL 32 bit library. Downgrade to an older version of the nVidia driver and things will work out fine. Another thing you can do is disable 3D if you have it enabled.

Hi wow that was quick support, thank you !

While I certainly don't want to downgraded my Win7 display driver for VB, disabling 3d acceleration fix the problem with the latest guest addons. Seems then that the new Nvidia driver (260.89) is causing problem with VirtualBox. I can certainly work without VB-3d but hopefully that will be fix in the next VB release ...

There is a setting in the nVidia manager that fixes this. Search using google for it. Sorry I don't remember exactly what it was.

http://forums.virtualbox.org/viewtopic.php?f=6&t=34764

Pay no attention to the admins, the issue IS in VirtualBox, not the driver.

Yup that is the one I read. So without saying that everyone that tries to help with this is an idiot squall, I fail to see how it would be a issue with VirtualBox and not an issue just because nVidia has changed their code. Seems to me to be standard movement between progressing codes. At least nVidia left a way to make it work, as you found out.

Well EXCUSE ME squall, for not being a true genius and actually remember that issue/work-around. Maybe it has something to do with me not running the buggy OS called Windows and the faulty driver? Maybe it's because the issue isn't discussed here often. But thanks to point it to the TS and remind me about it . I hope I will remember it for the next time, else I'll rely on you to give the proper answer.

@armagedon:
Why do you not want to downgrade the driver? Is there a certain fix for your video card or game that you must have?

Sasquatch wrote:Well EXCUSE ME squall, for not being a true genius and actually remember that issue/work-around. Maybe it has something to do with me not running the buggy OS called Windows and the faulty driver? Maybe it's because the issue isn't discussed here often. But thanks to point it to the TS and remind me about it . I hope I will remember it for the next time, else I'll rely on you to give the proper answer.

@armagedon:
Why do you not want to downgrade the driver? Is there a certain fix for your video card or game that you must have?

why should he have to change his video driver for a threading issue that the driver exposes in virtualbox.

I'm having the same exact issue. As soon as I installed the latest version of VB, I enabled Guest Additions for Folder Sharing. Right after that VB would crash @ startup; wouldn't even get to the actual start screen. In my case, a prompt came up telling me the GUI is crashing & needs to close. Just last night I researched a few possible solutions. Unfortunately, nothing worked & I had to uninstall VB again. BTW, I've been using VB for a while now [2+ years], mainly running a Window XP Host/Guest situation for software testing. That setup has worked nearly flawlessly for me, with a few hiccups here & there. Recently I upgraded my OS, now I'm using a Window 7 Ultimate 64-bit Host with a Windows XP Guest. Planning on using Mac & Linux Guests soon, too

After coming across this thread, I have to say I would have NEVER thought the problem could be the video driver [NVIDIA]. I actually had 3D acceleration enabled in the settings, so hoping a new VB install with that feature disabled will fix the issue of Folder Sharing.

Throwing my 2 cents in: I don't think it's right for someone to have to revert to an older video driver for other software to work. That's a non-starter for someone like me who games. I need to have every advantage afforded to me.

Will post my results as soon as I reinstall VB.

Thanks for the info, guys.

Wow lost following that thread for a while. So really no need to be nasty with this. VB is awesome, worth thousands of dollars in my book but hey FREE ! You can`t yell at the devs, just only help them to improve their fabulous software.
I`m a gamer too so NO downgrading driver for sure only for VB. Each NV driver bring its share of improvements and features. The VB-3D function is nice to experiment but I can`t hardly use it for serious gaming. So disabling it is no big deal.
From what I can see, the VB code is fine. Only the addons, more specifically the VB video driver seem to be the culprit and having issue with the new NV one. Lets get the VB team figure it out. In the meantime, VB is still working like a champ for me.
Cheer !

armagedon51 wrote:Wow lost following that thread for a while. So really no need to be nasty with this. VB is awesome, worth thousands of dollars in my book but hey FREE ! You can`t yell at the devs, just only help them to improve their fabulous software.
I`m a gamer too so NO downgrading driver for sure only for VB. Each NV driver bring its share of improvements and features. The VB-3D function is nice to experiment but I can`t hardly use it for serious gaming. So disabling it is no big deal.
From what I can see, the VB code is fine. Only the addons, more specifically the VB video driver seem to be the culprit and having issue with the new NV one. Lets get the VB team figure it out. In the meantime, VB is still working like a champ for me.
Cheer !

Ok, I have NO IDEA what you're talking about . Where do you get off making claims that I'm being "nasty" towards VB, or anything else, for that matter? In my post I simply state that I was having the same issue as the original poster. There is not a single instance where I'm being negative, derogatory &/or abusive towards VB software or its' developers. Where do I state VB costs thousand/millions of dollars & is not, in fact, a fantastic, versatile & free piece of genius software!?! So for you to make such a ridiculous leap & put up an incorrect & downright hilarious [not in a good way] post is frankly puzzling. Next time take a moment to actually read the post you're replying to. It would save us all a lot of time & energy.

OK, let's all take a moment of zen here and calm down. No need for any flame wars starting. I think we can all agree that this is a touchy topic and we all have our reasons for being disappointed, but is all fairness it is just a conversation. The actual cause is something that happens all the time when things change so drastically. Everyone will be back on target soon I'm sure.

MZAdotcom wrote: Ok, I have NO IDEA what you're talking about . Where do you get off making claims that I'm being "nasty" towards VB, or anything else, for that matter? In my post I simply state that I was having the same issue as the original poster. There is not a single instance where I'm being negative, derogatory &/or abusive towards VB software or its' developers. Where do I state VB costs thousand/millions of dollars & is not, in fact, a fantastic, versatile & free piece of genius software!?! So for you to make such a ridiculous leap & put up an incorrect & downright hilarious [not in a good way] post is frankly puzzling. Next time take a moment to actually read the post you're replying to. It would save us all a lot of time & energy.

My dear Mzadotcom don`t be so paranoiac. I didn`t quote you and there is nothing wrong with your post. I originate the whole thread and "somewhere" there was a change of tone while not specifying "anyone" in particular. So relax man, it`s not always about you.
Cheer !

In other words, he wasn't referring to you as a person, but used 'you' to generalise it. The kind of 'you' that means 'anybody'. You just happened to be the last one who posted when he made the reply.