Virtual box crashes on Windows host.

[wjw1964]

I get similar frequent crashes with the same error (assuming this is the same: The instruction at 0x00007FFF04362B32 referenced memory at 0x0000000000000000. The memory could not be written. Click on OK to terminate the program).
I never use Save states.
My laptop has 8 threads (4 cores) and the VM 1
Guest addition and VirtualBox are both 6.1.16 r140961
The thing just crashes when it feels like it, happens somewhere between every few hours or perhaps daily. Totally random and I need not be using the VM in any way at the time.
I couldn't even get 6.1.12 to work on Windows 10, went to 6.1.16 to be able to boot the VMs (new laptop). On 6.1.12 on the previous laptop (Surface pro 4) VMs never crashed.

[wjw1964]

Updating this, with the shared clip board disabled it still crashes and it crashes frequently.

[scottgus1]

Split off to separate topic. Do not hijack other threads, create your own. Choose your title carefully.

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

Right-click the VM in the main Virtualbox window's VM list, choose Show Log. Save the far left tab's log and the hardening log next to it, zip them, and post the zip file, using the forum's Upload Attachment tab.

[mpack]

Clearly a hardening problem. FAQ: Diagnosing VirtualBox Hardening Issues.

[wjw1964]

Thanks Scott, Logs upload.

[scottgus1]

You do show a hardening error ExitCode=0xc0000005.

However you also have Hyper-V enabled. See HMR3Init: Attempting fall back to NEM (Hyper-V is active). When the vbox.log doesn't have "Attempting fall back to NEM" in it anymore, then Hyper-V is gone.

Turn off Hyper-V, then try the VM again. If crashes happen, please re-post the two logs.

One other thing that may help. You have only one processor in the VM and you have 4 available on the host. If 8.1's load is like 10's load, 8.1 might like two processors.

[wjw1964]

I believe I made the changes you recommended I'm still having crashes.

[scottgus1]

The hardening log exit code is 0, so the hardening problem is not there for now.

The VM is still on one processor.

When the vbox.log doesn't have "Attempting fall back to NEM" in it anymore,

Did you search the vbox.log for those words before you posted it? Because they're still there. Hyper-V is still enabled.

[wjw1964]

stopping "Attempting fall back to NEM" appearing seems to be near impossible. I disable it and get some reliability and then within 24 hours it must re-instate because it crashes with it again. It is better, at least I get most of a day rather than sometimes minutes.

[BillG]

Have you used the bcdedit command to prevent the Windows hypervisor from loading? That is the best way to make sure that Hyper-V related problems don't interfere with the operation of VirtualBox.

viewtopic.php?f=1&t=62339

[wjw1964]

I run these two commands as Administrator:
bcdedit /set hypervisorlaunchtype off

DISM /Online /Disable-Feature:Microsoft-Hyper-V

I have a laptop so powering off for 20 seconds is not really an option, I can't remove the batteries esasily.

As I said; The above helps but does not resolve the problem.

[scottgus1]

The above helps but does not resolve the problem.

Please post a new log not showing "Attempting fall back to NEM".

[mpack]

I have a laptop so powering off for 20 seconds is not really an option, I can't remove the batteries esasily.

So what did you do instead? Restarting the PC is not an optional part of the instructions. Perhaps check with your laptop vendor or manual to find out how to do a hard reset.

[wjw1964]

It seems like something enables overnight, which then means first thing in the morning the first use of the Paste buffer triggers the vM to aborted (even thou the VM is not being touched or bought even forward amongst the windows)

[scottgus1]

wjw, please read and act on the replies above your last post.

edit, should have been 'wjw' not 'wow', darn autocorrect....