virtualbox.org

Hi I have a Windowsw VM, that crashes since last week about 20 seconds after I opened it. I have since upgraded to VirtualBox 5 and uninstalled the latest Windows Updates (Win 7 ) but it still crashes all the time.

See log attached

There is nothing in the provided log about a VM crash. The VM in that session was shut down normally. No crash, no abort, no error.

Do you have a screenshot of the crash?

I do see this :-

VBox.log wrote: 00:00:12.916918 OHCI#0: Lagging too far behind, not trying to catch up anymore. Expect glitches with USB devices
00:00:23.129000 PIIX3 ATA: LUN#0: IDLE IMMEDIATE, CmdIf=0xe7 (-1 usec ago)
00:00:23.129014 PIIX3 ATA: LUN#0: aborting current command

Are you running the VM from an abnormally slow drive? (USB or network)? ATA is your disk, so this is saying that the disk is too slow and causing aborts. Another possibility is that you have some I/O intensive process going on in the background, which is hogging the disk.

Looks like a guest OS crash. What is the error message? A screenshot might help here.

I notice in the log files:

VirtualBox VM 5.0.0 r101573 win.amd64 (Jul 9 2015 11:08:16) release log
00:00:06.513182 VMMDev: Guest Additions information report: Version 4.2.16 r86992 '4.2.16'

I would definitly update the guest additions.

Finally:

00:00:00.944428 File system of 'C:\Users\Tyron\VirtualBox VMs\course testing\fep development-disk1.vmdk' is ntfs
00:00:01.108587 Name <string> = "course testing" (cb=15)

If someone provided that VM to you, then they need to update the image. Workaround would be to revert to an older version of VirtualBox and see if it helps.

noteirak wrote:

00:00:00.944428 File system of 'C:\Users\Tyron\VirtualBox VMs\course testing\fep development-disk1.vmdk' is ntfs
00:00:01.108587 Name <string> = "course testing" (cb=15)

If someone provided that VM to you, then they need to update the image.

Can you explain that, Max? The only thing I see is that the name doesn't match the VM, which should not be fatal.

"Course Testing" - the OP could be a student or another teacher testing the said VM - either way, this VM could be made to be shared in mind.

I fixed it by simply disabling the Network in the VM. That was what stopped it from crashing.

Thank you for reporting back. It would have been good to see the crash screenshot tho for anyone else who would have had this issue.