Re: Upgrade from virtualbox 6.x to 7.0.20 has made working Win10 guest unstable

[gbell]

Windows 10 gets to the desktop, but then quickly throws a 0xc0000225 error.

This VM has been working for years.

An Ubuntu VM works fine and is stable.

This upgrade from VirtualBox 6.x to 7.0.20 was done as part of upgrading my host OS from Ubuntu 20.04 LTS to 22.04 LTS.

Thanks for having a look at my log.

[multiOS]

The Log shows these two "fatal condition" reports:

00:00:11.256745 Enabling different vbva mode
00:00:11.492345 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=00007f294c000000 w=1280 h=960 bpp=32 cbLine=0x1400 flags=0x1 origin=0,0
00:00:13.412218 GIM: HyperV: Guest indicates a fatal condition! P0=0xef P1=0xffffe78b1f1c70c0 P2=0x0 P3=0x0 P4=0x0
00:00:13.412259 GIMHv: BugCheck ef {ffffe78b1f1c70c0, 0, 0, 0}
00:00:13.412260 CRITICAL_PROCESS_DIED
00:00:15.191623 AHCI#0: Reset the HBA
00:00:15.191644 VD#0: Cancelling all active requests
00:00:15.192024 AHCI#0: Port 0 reset
00:00:15.193036 VD#0: Cancelling all active requests
00:00:16.296690 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
00:00:25.344102 VMMDev: Guest Log: VBoxGuest: BugCheck! P0=0xef P1=0xffffe78b1f1c70c0 P2=0x0 P3=0x0 P4=0x0
00:00:25.344292 GIM: HyperV: Reset initiated through MSR
00:00:25.344300 Changing the VM state from 'RUNNING' to 'RESETTING'

00:01:59.170727 GIM: HyperV: Guest indicates a fatal condition! P0=0xef P1=0xffff938c28b2d140 P2=0x0 P3=0x0 P4=0x0
00:01:59.170751 GIMHv: BugCheck ef {ffff938c28b2d140, 0, 0, 0}
00:01:59.170751 CRITICAL_PROCESS_DIED
00:02:00.941273 AHCI#0: Reset the HBA
00:02:00.941292 VD#0: Cancelling all active requests
00:02:00.941689 AHCI#0: Port 0 reset
00:02:00.942700 VD#0: Cancelling all active requests
00:02:01.982364 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
00:02:11.158918 VMMDev: Guest Log: VBoxGuest: BugCheck! P0=0xef P1=0xffff938c28b2d140 P2=0x0 P3=0x0 P4=0x0
00:02:11.159114 GIM: HyperV: Reset initiated through MSR
00:02:11.159122 Changing the VM state from 'RUNNING' to 'RESETTING'

Both appear to occur when attempting to interact with the Guest Additions installation.

The Guest Additions installation is a very old version (6.1.34) which is not fully compatible with VirtualBox 7.0.20, given the program changes which were implemented on the release of Version 7.0. I suggest you upgrade the Guest Additions installation and see if that has any impact.

[gbell]

I couldn't get the Guest Additions update or iso installer to go through because the system wouldn't be stable long enough.

So I installed Windows to a fresh VM, and that was stable, big clue. So I manually copied the settings to my old VM. Wasn't anything special that I hadn't already tried - number of CPUs, Graphics Controller. One thing that jumped out: disabled shared clipboard. Also, Enabled Nested Paging.

Now stable, the Guest Additions installer seemed happy, yet the system tray icon kept reporting it was v6.x.

The installation seemed otherwise b0rked though - start menu wouldn't display, couldn't run the Settings applet to reset the PC. sfc /scannow and the usual DISM stuff didn't fix it.

But that'd be another thread.

Three dozen reboots and I've had enough, so will just go with the fresh install of Windows.

Thanks for the help @multiOS.

[dornech]

Quick question: instead of reinstalling Windows (and applications) why not going back to last working VB 6.1.x, start VM and de-install GA, update virtualbox again and then reinstall appropriate GA in the VM ?

However, warning in VB install that GA might be incompatible when API was changed would be helpful?