Win10 guest hangs on Win10 host after guest updates: rdmsr(0x123) -> #GP(0)

[JannisSEA]

Hi, this is basically a new instance of viewtopic.php?t=95783 (which I started reading, didn't finish yet but is locked now anyways).

On my company provided laptop, I use Windows 10 64bit as host and run several VMs (Linux and Windows 10). After my vacation, I installed all available updates in my Windows 10 VM and it stopped booting (freezes at black screen with blue logo, no spinner). I thought of a random disk corruption, restored an older version (from backup, not from snapshot) and it booted right up. Installed updates again => same failure. Thus, I don't believe random disk corruption. Trying several tries to use Windows recovery tools didn't work, rolling back helps. I didn't yet investigate the exact Windows Update that caused it since rolling back and re-doing the updates is really time consuming.

The log (attached) indicates an MSR/Microcode-related problem that persists with all tried Acceleration methods:

Code: Select all

00:00:25.789619 TM: Switching TSC mode from 'VirtTSCEmulated' to 'RealTSCOffset'
00:00:25.789970 GIM0: HyperV: Enabled APIC-assist page at 0x000000000000e000
00:00:25.790121 IEM: rdmsr(0x123) -> #GP(0)

Host CPU: 11th Gen Intel(R) Core(TM) i7-11850H @ 2.50GHz
BIOS (Lenovo ThinkPad P15 Gen2):
wmic bios get smbiosbiosversion
SMBIOSBIOSVersion
N37ET46W (1.27 )

Virtualbox 7.0.10 without any Extension modules

Regarding the logs: Don't be surprised about the "VM resets" I had to do.... I fiddled with the boot loader / sequence and now the VM takes several tries to actually get to the error

[JannisSEA]

I've finished reading the thread at viewtopic.php?t=95783 and I can confirm that setting the CPUProfile to the i7-6700K fixes the problem also in my case.

Maybe that workaround could be mentioned in the first post? It might help people without forcing them to read all of the 4-page thread.

[JannisSEA]

Since the VM is booting again: According to my Windows Update History, the provblematic one could be KB5029331

[scottgus1]

Thanks for your information! This sort of problem may be good as a Bugtracker ticket, so the devs can plan for it.