Virtualbox - Guru Meditation Error

[Tostone]

Dear all,
today I met this error when I execute Windows7 on VirtualBox 5.2.18.
I used it many times, untill yesterday it worked.

could anyone help me?

Thankyou very much

[socratis]

could anyone help me?

With that amount of information? No way.

We're going to need to see a VM log from a complete VM run:

• Start the VM from cold-boot (not from a paused or saved state) / Observe error / 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.

[Tostone]

Here the log file

[andyp73]

00:02:52.613414 !!         VCPU1: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)

This is your guru meditation - it is an indication that the guest has done something unexpected and can be difficult to interpret. Looking at the log file then none of the usual culprits are obvious - you haven't overcommitted RAM or CPU cores and VT-x is being reported correctly.

I used it many times, untill yesterday it worked.

What happened yesterday? Did something on the host or in the guest get updated as VirtualBox won't suddenly have decided that 25th September 2018 was a good day to down tools and stop working!

-Andy.

[Tostone]

Maybe a W7 automatically update!

by the way I continue to receive this error and I don't know how to resolve it.

[Tostone]

no way to understand what happen. Any idea?
[ModEdit: Partial log deleted]

[mpack]

This does not seem like a normal VM, created from an ISO in the normal way. It's using a 32bit template with 3GB RAM, the vdi file is different from the VM name, it's in an unusual host folder.

Frankly, I doubt the assertion that this VM worked until recently WITH NO CHANGES TO THE VM. Where did this VM come from? How did it get this unusual configuration?

Triple fault is usually caused by something nasty, such as illegal processor instructions. This can be caused by corruption or by using non native device drivers intended for different hardware. If it's corruption then it can only be fixed from a backup.

[Tostone]

I created it with not dinamically HD resize than I recreate it with dynamic HD resize.
This, long time ago, so I don't remember what I did.
Maybe I found the image somewhere, I don't remember.

The only difference is that today I'm working on a different network.

I don' know.