mpack wrote:Let's see what pops out at me while I look at your log :-
512MB seems low for a Win7 VM. On your host you can afford to increase this to 1536MB.
If you are finished installing the VM the eject the virtual CD (ISO) from the drive.
Speaking of which, your ISO looks like a download. If so, did it come from a legit source? If it is pirated then who knows what's on it. Crashes would be expected.
Increase VRAM to 48MB.
1.OK I will try to increase ram. I have 8GB in my machine
2. I cant even get into the install phase of the windows 7 insall yet, on that version.
3. It is a download from a legit source, and I am using a corporate code at work.
4. ill try the ram too.
4.3.12 is working so far. Does that mean I should never update?
No, if 4.3.12 works but further versions don't it means either you have unsigned dll's trying to poke their way into your system (theme patches, some antivirus, a few other uncommon programs do this) or bad Windows Updates are interfering. The vboxstartup.log or vboxhardening.log will say if such issues are interfering.
I have upgraded to Virtualbox 5.0.10 and it crashes on anything I do.. I have uninstalled and reinstall. I have reinstalled 5.0.8 and back to 5.0.10.
Since it was working on 5.0.8 it seems that whatever changed since you did the upgrade to 5.0.10 caused the problem. Maybe you did something at the same time as the Virtualbox upgrade. You mentioned you did Windows updates, that would cause the problem. Did you install any other programs at the same time as the Virtualbox upgrade?
4.3.12 is working so far. Does that mean I should never update?
No, if 4.3.12 works but further versions don't it means either you have unsigned dll's trying to poke their way into your system (theme patches, some antivirus, a few other uncommon programs do this) or bad Windows Updates are interfering. The vboxstartup.log or vboxhardening.log will say if such issues are interfering.
I have upgraded to Virtualbox 5.0.10 and it crashes on anything I do.. I have uninstalled and reinstall. I have reinstalled 5.0.8 and back to 5.0.10.
Since it was working on 5.0.8 it seems that whatever changed since you did the upgrade to 5.0.10 caused the problem. Maybe you did something at the same time as the Virtualbox upgrade. You mentioned you did Windows updates, that would cause the problem. Did you install any other programs at the same time as the Virtualbox upgrade?
Sorry I wasn't clear, I was on a really old 4.* version and upgraded to 5.0.10 and it did not work. Then I downgraded to 5.0.8 and it still didn't work. So I installed windows updates and tried 5.0.8 and 5.0.10 again and neither worked.
Well, shoot. Early version of 4. Extremely essential piece of info there. Would have saved rather a bit of posting...
Anything from 4.3.14 onward will show security issues over unsigned DLL's, which malware producers use to sneak their bad guys onto your system. DLL's from other programs can inject themselves into running processes on the PC, and in the case of Virtualbox really bad stuff can happen if a malware DLL injects into Virtualbox. So Virtualbox won't run if there's unsigned DLL's present.
Microsoft put out a few Windows updates that damaged the authenticity certificate database for core Windows DLLs, making the signature for those files appear bad. That's why Virtualbox won't run with some Windows updates present.
So you will have to either stay on 4.3.12 or earlier and make sure you never get malware on your host, or dig through the VboxStartup.log and Vboxhardening.log and see if there are any errors listed affecting DLLs on your system. If the DLLs referred to are Windows DLLs (The errors will mention "lacks WinVerifyTrust") you still have the bad Windows update(s) present. If the DLL being referred to is not a Windows DLL but some other program, get a new version of the program with signed DLLs. if it's a theme hack DLL, put the original unhacked Windows copy of the theme DLL in the same folder as Virtualbox.exe on your host (where Virtualbox is installed) that should allow the theme hack to still be usable.
The VBoxHardening log was posted at the start of this topic. It shows a 0xC0000005 crash (access violation), perhaps caused when one (valid sig) DLL which was allowed tries to call another DLL, which was blocked.
No, I don't have a list. Just about anything can be important depending on the nature of the issue reported. I think you're already aware of the "popular" errors (too much or too little RAM, overcommittment of cores, unusual paths to media files etc).