1.32 crashing/restarting

[rkv]

I've got a similar problem (VM crashing after VB 6.1.32 upgrade). The issue seems to be fixed by updating Guest Additions on VM.

[rkv]

Actually, it is still crashing...

[scottgus1]

Start the VM from full power off, not save-state. Run until you see the problem happen, then shut down the VM from within the VM OS if possible. If not possible, close the Virtualbox window for the VM with the Power Off option set.

Please right-click the VM in the main Virtualbox window's VM list, choose Show Log. Save the far left tab's log, zip the log file, and post the zip file, using the forum's Upload Attachment tab.

[rkv]

Attaching the log after VM rebooted itself (and I shut it down after that).
Host: Win10Pro
Guest: Win10Pro

[mpack]

Your VM is poorly configured.

You have 27GB RAM available on your host (32GB installed), yet only give 2GB to a Win7-64bit VM. I would increase that to 8Gb (8192MB).

You have only assigned 1 vCPU. Make that 2.

You only have 48MB of graphics RAM configured, despite attempting to run with fullhd+ graphics. Increase to 128MB (or 256MB if it lets you) and enable 3D acceleration.

You should eject the Guest Additions CD.

You have Hyper-v enabled on the host. This or the lack of graphics RAM are IMHO the most probable cause of the crashes.

00:00:03.381499 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
00:00:03.434133 NEM: info: Found optional import WinHvPlatform.dll!WHvQueryGpaRangeDirtyBitmap.
00:00:03.434193 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...

Have a read of: HMR3Init: Attempting fall back to NEM (Hyper-V is active).

[rkv]

I will work on Hyper-V. I must say everything worked fine until 6.1.32...

[rkv]

I have tried to adjust memory and CPU and VideRAM - that makes my VM hung. I had to revert it back

[mpack]

Given more RAM and CPU never made any PC worse.