Upgraded to Virtualbox 5.0.10 Crashing

[Minor723]

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.

Windows 7 host and windows 7 guest. When trying to install windows 7 guestit jsut goes right back to aborted and then when i check the log file it says this.(See attached log, error lines at the bottom.)

[Minor723]

Does anyone have an idea on this? I cant run / install any virtualbox. I will get you any logs if you have questions.

It looks to be crashing on these lines.

33b8.540: supR3HardNtChildWaitFor[2]: Quitting: ExitCode=0xc0000005 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 14271 ms, the end);
3180.31e4: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0xc0000005 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 14930 ms, the end);

[Perryg]

Post the guests log file ( as an attachment ). Right click on the guest in the Main Manager then click show log. Save and post as an attachment. Compress if it is too large to post.

[Minor723]

Post the guests log file ( as an attachment ). Right click on the guest in the Main Manager then click show log. Save and post as an attachment. Compress if it is too large to post.

Attached is the vbox guest log file.

[Perryg]

Code: Select all

00:00:03.989473 VMMDev: Guest Log: BIOS: Booting from CD-ROM...

Do you have a guest that is already installed and was working?

Also this log file is truncated. Did it abort, stop, or crash the host? Be very clear on how the guest fails and what you see on the screen.

[Minor723]

Code: Select all

00:00:03.989473 VMMDev: Guest Log: BIOS: Booting from CD-ROM...

Do you have a guest that is already installed and was working?

Also this log file is truncated. Did it abort, stop, or crash the host? Be very clear on how the guest fails and what you see on the screen.

I deleted everything, and started over.
The guest starts up goes the windows is loading files screen, then starting windows. then just closes completly. On the Oracle VM VirtualBox Manager screen it shows Windows 7 Aborted.

[Minor723]

I have installed all the latest windows updates, and still cannot get a host to load. everything still crashes. Even livecds.


Any ideas?

[Perryg]

Not really. All indications are pointing to the host. Some program install, Windows update, or even a virus or virus program being installed or updated since the last time this worked. I will stand down and let one of the Windows experts continue with you but if you can remember what changed between the time it worked and now you might have a better chance of fixing this. You can also downgrade to 4.3.12 and see if it works. If so then the aforementioned will more than likely be the cause.

[scottgus1]

Windows update KB3081320 has been reported as a Virtualbox killer a few times recently in the forum, also KB3004394 and KB3045999 some months ago.

[Minor723]

I lowered the version to what you mentioned and I am presented with this error.

Failed to open a session for the virtual machine Windows 7 32 .

The VM session was aborted.

Result Code: E_FAIL (0x80004005)
Component: SessionMachine
Interface: ISession {12f4dcdb-12b2-4ec1-b7cd-ddd9f6c5bf4d}

[scottgus1]

In addition to the error messages you see, please provide this info: Minimal information needed to be able to help especially the zipped logs. They're needed to find out what went wrong to cause the error.

[Minor723]

Windows 7 32 -2015-11-17-08-50-23.log

vbox.log

(59 KiB) Downloaded 3 times

Windows 7 host, windows 7 32 bit guest with additions. Version 4.3.34

[scottgus1]

I'm not too familiar yet with all the info in the logs, but the latest posted log appears to me to be cut off, as if the guest did just suddenly die off.

The first log you posted has a lot of "lacks WinVerifyTrust" errors in it. I wonder if you are having Windows Updates troubles with one or more of the updates I posted about? Please confirm that these updates are or are not on your host.

Perry suggested downgrading to 4.3.12. You did downgrade, but to 4.3.34. Any reason you didn't go to Perry's suggested version?

[Minor723]

I'm not too familiar yet with all the info in the logs, but the latest posted log appears to me to be cut off, as if the guest did just suddenly die off.

The first log you posted has a lot of "lacks WinVerifyTrust" errors in it. I wonder if you are having Windows Updates troubles with one or more of the updates I posted about? Please confirm that these updates are or are not on your host.

Perry suggested downgrading to 4.3.12. You did downgrade, but to 4.3.34. Any reason you didn't go to Perry's suggested version?

When i googles his version, and downloaded the first link that came I misread the version, I will find the correct version.

But after uninstalling the first 2 updates mentioned above the Vm got further then aborted. Here is the new log.

*Update* 4.3.12 is working so far. Does that mean I should never update? ha

[mpack]

Let's see what pops out at me while I look at your log :-

1. 512MB seems low for a Win7 VM. On your host you can afford to increase this to 1536MB.
2. If you are finished installing the VM the eject the virtual CD (ISO) from the drive.
3. 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.
4. Increase VRAM to 48MB.

Edit: If switching to 4.3.12 solves the problem then that implies that the problem is related to the hardening feature. In which case good luck, as very little information is bestowed on us poor infantry regarding that feature: the hardening log is essentially unreadable; it doesn't even have timing info, so you can't compare event timing with the main log. I can only guess that your crash may be due to an injected DLL being blocked. You might like to test if disabling your AV allows the VM to boot. Failing that, tell us if you've installed third party themes etc.