Ubuntu Jammy x64 host, Windows 10 guest, vbox keeps crashing

[jik]

I'm running a Windows 10 x64 guest on Ubuntu Jammy x64. My VM is crashing every few minutes. Sometimes Windows doesn't even boot all the way before it crashes. Sometimes it restarts itself instead of crashing entirely. I'm _also_ having trouble inside the VM getting KB5016688 to install; I don't know whether this is related. I've attached the log of a recent crash. If anybody can help I sure would appreciate it.

[scottgus1]

The log was taken while the VM was running, so we don't have all the diagnostic data. Logs are best taken after all the VM's windows are closed.

The VM 'hardware' keeps running through the VM OS's perturbations, so it looks like Virtualbox is working.

The VM OS BSODed 4 times, 3 0x3B's and a 0x154. Seems like the OS is having issues, not Virtualbox.

You're running the Ubuntu fork of Virtualbox, which they support. We technically only support official Virtualbox from www.virtualbox.org. This may not be an issue here, though, but be prepared to have to switch to official.

Try making a new 10 VM, see if it has trouble. Also try troubleshooting the BSODs in the old VM using Microsoft's web-searchable methods.

[jik]

When I saved the attached log, the Virtualbox console said that the VM was in state "Aborted" and it was not, as far as I know, running.

I did finally manage to get the aforementioned Windows update to install, so we shall see if, now that it is installed, the problem stops happening. If not, I will follow your instructions for additional troubleshooting.

[sdbillin]

I had this problem (albeit with a Windows 11 guest) after updating to the 5.15.0-47 kernel.
Reverting to the 5.15.0-46 kernel seems to resolve the problem (select advanced from the GRUB boot menu on your host OS).

[mpack]

Update VirtualBox to 6.1.36 to get support for later kernels.

[lgvb247]

Same issue for me, that kernel update seems broken for me. All my Linux VMs were crashing, Windows VM now corrupted.
Switching back to 5.15.0-46 kernel solve it.

[fth0]

Background information for all reported issues in this thread so far:

Linux kernels 5.19, 5.18, 5.17.12+ (e.g. Fedora 35 + 36), 5.15.44+ (e.g. Arch Linux 5.15.45-1-lts, Ubuntu 5.15.0-47.51) and 5.10.119+ (e.g. Debian Bullseye 5.10.0-15) and 5.4.200+ (e.g. Ubuntu 5.4.0-126.142) are only supported by VirtualBox 6.1.36 and newer.