Any guest crashes on Windows 11 with VB 7.0

[xorredd]

screenshot

Screenshot 2022-10-20 192714.png (8.9 KiB) Viewed 3827 times

Since a couple days ago, all Windows my VMs crash at launch. All Linux VMs do not crash.

Result Code:
E_FAIL (0X80004005)
Component:
SessionMachine
Interface:
ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}

They crash with a message box, "The instruction at 0x00007FFDE8C29232 referenced at 0x000001927A5E358. The memory could not be written."

[fth0]

Please try VirtualBox 7.0.2 and if the issue persists, provide a (zipped) VBox.log file and the corresponding Application Error dialog.

[xorredd]

Issue persists even after I upgraded.

It persists for ANY windows VM.

VBox.zip

(20.76 KiB) Downloaded 8 times

[fth0]

The VBox.log file shows the start of a VM from a saved state, which means that the guest OS was not started anew, but continued after pausing. In consequence, it doesn't make much sense to analyze this VBox.log file. Also, next time provide it together with the corresponding Application Error dialog as requested, and additionally the VBoxHardening.log file, please.

Additionally, either uninstall the VirtualBox Extension Pack or install the matching version.

[xorredd]

I don't know what you mean by "Application error" - I already provided a screenshot of the application error dialog box (which no longer shows in 7.0.2 - the VM simply crashes silently, which is ... an upgrade).

The VirtualBox extensions in the VM is the latest 7.0.2 version already, the VM still crashes.

I did not "resume" from a saved state. The VM crashes. When you click "turn on" the VM, it boots normally. That's where the log you requested comes from.

VBox.zip

(64.16 KiB) Downloaded 3 times

[fth0]

Since a couple days ago, all Windows my VMs crash at launch. [...] They crash with a message box

Issue persists even after I upgraded.

I don't know what you mean by "Application error" - I already provided a screenshot of the application error dialog box (which no longer shows in 7.0.2 - the VM simply crashes silently, which is ... an upgrade).

I can only react on the information you gave, and the second quote above told me that you still had a "crash with a message box". If you had the same error with VirtualBox 7.0.2, the address in the message box would probably have changed, that's why I wanted a new screenshot of it. I now understand that it's not necessary any more.

---

00:00:05.032720 VirtualBox VM 7.0.2 r154219 win.amd64 (Oct 19 2022 21:29:26) release log
00:00:05.032722 Log opened 2022-10-23T17:49:04.672334700Z
00:00:05.118593 Console: Machine state changed to 'Restoring'

I did not "resume" from a saved state.

The VBox.log file from 2022-10-23T17:49:04.672334700Z obviously contradicts your statement.

---

The VBoxHardening.log file indicates that some software invaded the process memory of VirtualBoxVM.exe, but it doesn't say which software this is. I can at least identify 0patch. Prevent any 3rd-party software from invading the address space of the VirtualBoxVM.exe process, either by uninstalling it or by configuring it accordingly.

---

00:00:05.324436 VirtualBox VM 7.0.2 r154219 win.amd64 (Oct 19 2022 21:29:26) release log
00:00:05.324438 Log opened 2022-10-24T13:57:34.229531100Z
[...]
00:00:05.397043 Installed Extension Packs:
00:00:05.397055   Oracle VM VirtualBox Extension Pack (Version: 6.1.38 r153438; VRDE Module: VBoxVRDP; Crypto Module:  unusable because of 'VBoxExtPackVMRegister returned VERR_VERSION_MISMATCH, pReg=0000000000000000 ErrInfo='Helper version mismatch - expected 0x30000 got 0x50000'')

The VirtualBox extensions in the VM is the latest 7.0.2 version already

The VirtualBox Extension Pack is on the host, not in the VM.

---

00:00:05.324436 VirtualBox VM 7.0.2 r154219 win.amd64 (Oct 19 2022 21:29:26) release log
00:00:05.324438 Log opened 2022-10-24T13:57:34.229531100Z
[...]
00:00:05.714610 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available

I'd suggest to get rid of Hyper-V on the host.

[rexcat]

Enabling Virtual Machine Platform also causes the guest to fail to start.

[xorredd]

I'd suggest to get rid of Hyper-V on the host.

On W11, I uninstalled every possible mention of Hyper-V following several articles. Do you know of other means of uninstalling it? Is it possible that it's still always present on w11?

Thanks for all your other suggestions, implemented, testing now.

[fth0]

Do you know of other means of uninstalling it? Is it possible that it's still always present on w11?

There are lots of Windows features implicitly using the Windows hypervisor (Hyper-V). On Windows 11, especially "Memory integrity" is alway active in default installations. For all the others, see HMR3Init: Attempting fall back to NEM (Hyper-V is active).

[xorredd]

the VMs keep crashing. One crashed at "insert guest additions" and then trying to open My Computer to install. Then after reboot, I tried again, and the VM crashed during installation of the additions (almost at the end).
Reboot. Insert CD. Crash immediately on trying to open the "CD" from My computer.

0Patch - turned off.

Considering the amount of people complaining that their VMs crash after 7.0 release, I don't think it's my machine.

VBox.zip

(92.02 KiB) Downloaded 3 times

[fth0]

0Patch - turned off.

Didn't change anything. Search the VBoxHardening.log file for "0patch" to see for yourself. Many so-called security softwares cannot be fully disabled without uninstalling them.

Considering the amount of people complaining that their VMs crash after 7.0 release, I don't think it's my machine.

Quite possible! You'll eventually know it when the crashes of the other users will have been eliminated.

Note that your VBoxHardening.log files show several other problems, and nobody will probably have a look at the secondary errors because they could be consequential errors.

In your VBox.log file, I noticed that the VBoxService.exe 7.0.2 gets started twice, possibly indicating a corrupt VirtualBox Guest Additon installation.

[xorredd]

0patch was completely uninstalled. The issue persists. I also completely reinstalled VirtualBox, same thing.

[xorredd]

VBox.zip

(58.8 KiB) Downloaded 5 times

adding logs. Still experience the same problem, after uninstalling 0patch...

[mpack]

First, you allocated all 4 of the host CPU cores to the VM. Starving the host of CPU does not make it stable. Reduce the VM allocation to 2 cores. While I'm there I would increase VM RAM to 8GB (5GB is a strange number to give).

And you have not disabled Hyper-v.

00:00:47.260643 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
00:00:47.371197 NEM: info: Found optional import WinHvPlatform.dll!WHvQueryGpaRangeDirtyBitmap.
00:00:47.371207 NEM: info: Found optional import vid.dll!VidGetHvPartitionId.
00:00:47.371211 NEM: info: Found optional import vid.dll!VidGetPartitionProperty.
00:00:47.371287 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...

See HMR3Init: Attempting fall back to NEM (Hyper-V is active).

[fth0]

Still experience the same problem, after uninstalling 0patch...

The new VBoxHardening.log indicates that not only the signs of 0patch are absent now, but also the secondary errors, so far, so good. What remains is the exit code of 0xc0000409 (STATUS_STACK_BUFFER_OVERRUN). In summary, we've verified that 0patch didn't play a role.

In consequence, it looks like some of the issues that other users have reported when running VirtualBox 7.0.2 on the Windows Hypervisor (Hyper-V, NEM). In addition to what mpack (and I in an older post) wrote regarding eliminating Hyper-V, you can either wait for VirtualBox 7.0.4 or try the VirtualBox test builds 7.0.3r154539 or newer. There have been several major bugfixes, but I don't know if your issue is amongst them.