Win7 Guest fails after security update

[Jared Hargrave]

Good day.

I am in need of assistance with my Win7 guest, running on Mac OSX host Versioni 6.0.4.r128413.

After Windblows installed security patches, the machine fails at boot with a "critical error"

Unfortunately, I cannot see anything in the log that shows a blatant failure.
Would someone in the forum assist me with decoding what the critical error might be?
I attached the logs, below.

Thank you in advance!

[socratis]

I attached the logs, below.

I wish you did, but... you didn't!

We need to see a complete VBox.log, from a complete VM run, where the problem occurs:

• Start the VM from cold-boot (not from a paused or saved state) / Observe problem / Shutdown the VM (force close it if you have to).
• With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
• Save only the first "VBox.log", ZIP it and attach it to your response. See the "Upload attachment" tab below the reply form.

[Jared Hargrave]

Good morning!

Please accept my apologies!

I have tried, again, to post the ZIP file.

[mpack]

00:00:01.962218 Host RAM: 16384MB (16.0GB) total, 8035MB (7.8GB) available
...
00:00:02.116385 RamSize <integer> = 0x0000000300000000 (12 884 901 888, 12 288 MB, 12.0 GB)

00:00:02.116382 NumCPUs <integer> = 0x0000000000000004 (4)
...
00:00:02.474074 CPUM: Physical host cores: 4

You have overcommitted both RAM and CPU. RAM needs to be reduced to something like 6GB, CPU cores should be reduced to 2.

[Jared Hargrave]

Thank you for the information!

This thing has been running for years on this PC...

However, I have made the requested modifications and attached the still failing log files.

[mpack]

Actually, my suggestion was to reduce the number of CPUs to 2, not 1. Reducing it to 1 will badly affect performance.

Your remaining error is a triple fault. Typically this is caused by a guest driver doing something really nasty, but since it faults again inside the fault handler that's as much as I can tell you about the trigger.

00:06:18.117710 Console: Machine state changed to 'GuruMeditation'
00:06:18.118131 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:06:18.118132 !!
00:06:18.118132 !! VCPU0: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)
00:06:18.118145 !!
00:06:18.118149 !! Skipping ring-0 registers and stack, rcErr=VINF_EM_TRIPLE_FAULT
00:06:18.118153 !!
00:06:18.118153 !! {mappings, <NULL>}
00:06:18.118154 !!

I do now notice other weird features of your VM: it's a 32bit VM and therefore can't handle more than 4GB RAM, and yet you had 8GB allocated to it when I first looked and even now you still have it >4GB. 2GB should be more than enough for a 32bit Windows VM. And as I said it simply doesn't know what to do with more than 4096MB.

Another thing: there are two hard disks attached to the VM, and neither of them originated with this VM. The image files (one Parallels, one VirtualPC) have been copied and a new VM has been created around them. This makes me doubt the statement that this VM has been running (implication: without modification) for a long time, especially given the errors. The disk images have clearly existed for a long time, but when was this VM created? The potential seems high that this VM was recently ported from another host, and only the disks were moved, the VM settings were not retained.