![]() Host: Win7 64bit with 8GB mem, running several different guests (win 2008 r2, win 2008 32bit, win 2003, Ubunut 10.10. ![]() (First occurence was founded in unofficial test build 4.1.7, see comment 9 of ticket 7929. Expected result is a Paused VM state, but the VirtualBox simple crashed with guru mediation. ![]() I which I can contribute, but I lack the skill of programming OS or Viritualization software. I've resumed a virtual machine, but memory low. I sincerely hope that this is solved swiftly. I could also be VirtualBox that don't revert all parts when I downgraded to it's previous version. I uninstalled VirtualBox and downloaded an older version of VirtualBox, to my surprise it did not solve the problem, so it could be Microsoft that has released a Windows patch that has broken a feature in windows that VirtualBox depend upon. ![]() I'm still not sure of this, who am I going to blame, Microsoft or Oracle? No offense I like both of them. It could be some windows update that could caused my flickering screen and virtual instances limitation of memory consumption. I suspected that is could be Virtual Box release, the problems started when I updated the Oracle VM VirtualBox Extention Pack to version 4.1.8r75467 but I was not sure. The reason that I suspected hardware errors is because of the fact that the screen start to flicker when the memory consumption begin to reach its limit of 8GB. I have run all kind of memory checks and did not find anything wrong with my laptop. I thought it was my computer hardware that has been broken.
0 Comments
Leave a Reply. |