Windows 10 VM crashing on VirtulalBox 6.1

[RogerM]

I've had a Windows 10 VM running for years on VBox - most recently on Fedora 27 and VirtualBox 5.1. I have just upgraded to Fedora 31 and in the upgrade process upgraded VirtualBox to 6.1. Now the Wndows VM crashes within 15 minutes. There is no pattern to the crash - it happens more quickly when an app is being run. The VM logs show differing checkbug codes. I've installed the updated extensions, guest additions, changed the video driver and reinstalled VirtualBox with the latest 6.1.2 release (after removing everything from the previous installs). There is no change in the behaviour. I've attached a Vbox log of the windows VM booting, crashing, rebooting crashing and then an orderly shutdown. I'd appreciate any help on this.

[konsultnisse]

I have a similar behavior on a Dell XPS 7390 running Ubuntu 18.04-3, first with VB 6.0 and later upgraded to 6.1
still sometimes win10 guests just die...

Best regards,
konsultnisse

[fth0]

00:00:00.770653 VirtualBox VM 6.1.2 r135662 linux.amd64 (Jan 13 2020 11:59:19) release log
00:00:00.804985   Oracle VM VirtualBox Extension Pack (Version: 6.1.2 r135662; VRDE Module: VBoxVRDP)
00:00:10.257599 VMMDev: Guest Additions information report: Version 6.1.0 r135406 '6.1.0'

Uninstall the Guest Additions, reboot the guest OS, and install the correct version of the Guest Additions. Does the problem persist?

[RogerM]

The story so far
- with the 6.1.2 Guest additions: no change Windows 10 still crashes
- de installing guest additions: no change Windows 10 still crashes
- removed all shared drives: no change Windows10 still crashes
- changed to Hyper-V virtualization: no change Window 10 still crashes
All the crashes seem to be memory related from the window's error codes. The only pattern to the crashes appear to be a more intensive process grabbing memory resources.

I decided at this point to build a new Windows 10 virtual machine. This exhibits similar behaviour.
On both Window's VM's page fusion and ballooning are disabled
Linux VM's don't exhibit any issues.

I'm starting to suspect the Fedora 31 - VirtualBox 6.1.2 combination. B.t.w Fedora 31 is up-to-date.

[fth0]

00:12:36.283976 VMMDev: Guest Log: VBoxGuest: BugCheck! P0=0x3b P1=0xc0000005 P2=0xfffff80023bece4a P3=0xfffff98188cd5b20 P4=0x0
00:18:36.102237 VMMDev: Guest Log: VBoxGuest: BugCheck! P0=0x1e P1=0xffffffffc0000005 P2=0xfffff80009c4b77d P3=0x0 P4=0xffffffffffffffff

Since you didn't provide a 2nd VBox.log file, I took a 2nd look at the 1st one. I noticed that the Windows Bug Check events took place almost exactly 6 minutes apart from each other. If you compare this with other Bug Check event times, maybe you can find a pattern.

Generally speaking, the crashes happen inside your guest OS, and you should investigate them as if they occurred on a physical host. The VirtualBox Guest Additions driver registers itself for Bug Check events and logs them. This does not indicate that the Bug Check event occurred inside a VirtualBox component, but also doesn't indicate the opposite. I would start with checking inside the Windows Event Viewer, and letting Windows stop at a BSOD, to find out which Windows driver crashes.