by sdavmor » Wed Sep 10, 2008 9:38 pm
On a parallel problem course to the above (downloading files crashing Newsbin) I just posted this over at the Virtualbox forum.
I upgraded Vbox yesterday morning from 1.6.4 to 2.0.0 on an Ubuntu Studio 8.04 (Hardy) AMD64 machine with 4gb PC6400 RAM and an Athlon 5200+ dual core CPU. My virtual Windows is XP with up to date service packs. It's been running with hardly any issues for several months other than Explorer sometimes locking up for no good reason.
On a whim, seeing that there's a 2.0.0 out there and I missed the 1.6.6 revision, I went for the upgrade. Since then my virtual windows has crashed into the blue screen of death numerous times while doing usenet downloads using Newsbin (which has been very stable on the 1.6.4 Vbox platform). If I leave it sitting on the desktop doing nothing, nothing bad happens, as I'd hope would be the case.
So I uninstalled the 2.0.0 Vbox, then reinstalled it, did a chkdsk c: /F in case there was any MFT corruption (none), then reloaded the 2.0.0 guest additions. But it keeps blowing up in the same way. Specifically anytime I d/l a file in Newsbin, as soon as it completes, I crash into a blue screen of death. I can harvest headers OK and small text files, but not larger audio/video files. Which I suspect may have something to do with them needing to be assembled.
I tried downgrading back to 1.6.6 but it doesn't want to provide me access to my virtual hard drive. As soon as I reupgrade back to 2.0.0 I get access to the virtual drive again. I've also reinstalled and reconfigured Newsbin but nothing changes, and I've tried running the virtual Windows with VT-x/AMD-V and PAE/NX both Enabled or Disabled. Makes no difference either way.
So it looks like I'm stuck with solving the problem at the 2.0.0 release level instead of just ignoring it until somewhere down the road. FWIW the other program that I need the virtual Windows for is sony Acid Pro 6. It works flawlessly.
Here's the error message I get from the Vbox launcher when I try to run after downgrading to 1.6.6:
Could not load the settings file '/home/sdavmor/.VirtualBox/Machines/Win2KOEM/Win2KOEM.xml'.
Element '{http://www.innotek.de/VirtualBox-settings}HardwareVirtExNestedPaging': This element is not expected. Expected is ( {http://www.innotek.de/VirtualBox-settings}PAE ).
Element '{http://www.innotek.de/VirtualBox-settings}GuestProperties': This element is not expected.
Result Code:
0x80004005
Component:
VirtualBox
Interface:
IVirtualBox {2d3b9ea7-25f5-4f07-a8e1-7dd7e0dcf667}
Has anyone else experienced this kind of blue screen crash since 2.0.0 was released? If so, what did you do about it? Are you still on 2.0.0, and if so are you living with intermittent failure, or have you just returned to an earlier revision? (i.e. 1.6.6 or 1.6.4)
On the whole I'm impressed with the stability and functionality of the Vbox product. It does what I want when I need to go into Windows. But right now I'm cursing myself and hitting my head with a hammer for not letting sleeping dogs lie/fixing something that wasn't broken!
Any constructive help here would be appreciated.