VirtualBox

Ticket #20180 (new defect)

Opened 3 months ago

Last modified 2 days ago

Windows 10 guest OS crashes with STATUS_DATATYPE_MISALIGNMENT exception

Reported by: hottobar Owned by:
Component: other Version: VirtualBox 6.1.18
Keywords: Cc:
Guest type: Windows Host type: Linux

Description

My Windows 10 20H2 guest OS keeps crashing and rebooting after a few minutes of uptime, even when left at idle with no user activity. The amount of uptime before crash varies, from a couple of minutes to maybe 30'.

This is an extract of the VBox.log file with the exception (full log attached):

00:04:04.476177 GIM: HyperV: Guest indicates a fatal condition! P0=0x1e P1=0xffffffff80000002 P2=0xfffff80426ae4793 P3=0xffffbd0cd2c0237a P4=0x7010008004002001
00:04:04.476246 GIMHv: BugCheck 1e {ffffffff80000002, fffff80426ae4793, ffffbd0cd2c0237a, 7010008004002001}
00:04:04.476246 KMODE_EXCEPTION_NOT_HANDLED
00:04:04.476246 P1: ffffffff80000002 - exception code - STATUS_DATATYPE_MISALIGNMENT
00:04:04.476246 P2: fffff80426ae4793 - EIP/RIP
00:04:04.476247 P3: ffffbd0cd2c0237a - Xcpt param #0
00:04:04.476247 P4: 7010008004002001 - Xcpt param #1
00:04:07.226307 AHCI#0: Reset the HBA
00:04:07.226322 VD#0: Cancelling all active requests
00:04:07.226560 AHCI#0: Port 0 reset
00:04:07.227608 VD#0: Cancelling all active requests
00:04:07.367081 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
00:04:09.277149 VMMDev: Guest Log: VBoxGuest: BugCheck! P0=0x1e P1=0xffffffff80000002 P2=0xfffff80426ae4793 P3=0xffffbd0cd2c0237a P4=0x7010008004002001

The VM's guest OS was freshly installed from Microsoft's ISO. No third party AV software nor drivers installed.

My host setup:

  • OS: Ubuntu 20.04.1
  • Kernel: tested with 5.8.0-41-generic (Ubuntu) and 5.9.16-050916-generic (mainline)
  • System: HP ProBook 650 G8
  • CPU: 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz
  • VirtualBox: tested with 6.1.16 (Ubuntu's repo) and 6.1.18 r142142 (Oracle's repo)

Conditions that do not cause a crash:

  • running the VM in safe mode
  • running the VM in a different host with Ubuntu 20.04.1, kernel 5.8, Virtualbox 6.1.18 r142142, CPU AMD Ryzen 9 3900X
  • converting the VM's vdi file to qcow2 and running it with KVM

What have been tested without success (VM still crashes):

  • running it with a different CPU profile, "i7-6700K" instead of "host"
  • uninstalling the VirtualBox Guest Additions
  • changing the paravirtualization interface from "Default" to "Legacy"

This issue has been discussed in this forum post:  https://forums.virtualbox.org/viewtopic.php?f=7&t=101667

Searching the forums for similar problems led to these apparently relevant discussions, all with no solutions nor workarounds:

Attachments

VBox.log_STATUS_DATATYPE_MISALIGNMENT.zip Download (32.6 KB) - added by hottobar 3 months ago.

Change History

Changed 3 months ago by hottobar

comment:1 Changed 3 months ago by fth0

In the VirtualBox forums, this problem has been reported by at least 8 users in the last weeks and months. I've analyzed those cases and from my POV the following conditions apply:

  1. The host CPU is always a 10th/11th generation Intel CPU, so far i7-1065G7, i5-1135G7 or i5-1185G7. Using older Intel CPUs or AMD CPUs does not exhibit the problem. VirtualBox does not know up to 20 new and previously reserved bits in the CPUID leaf 7.
  1. On the host, a Linux kernel 5.8 or later is always running. Using a Linux kernel 5.4 does not exhibit the problem.
  1. VirtualBox versions 6.1.14, 6.1.16 or 6.1.18 are being used. Running a VM with the same virtual disk in KVM or VMware does not exhibit the crash.
  1. In the guest, Windows 10 or Windows Server 2016|2019 is running. Using Windows 7 or Linux does not exhibit the problem. It suffices to start a VM from a Windows 10 ISO and to wait, so no VirtualBox component is running inside the guest.
  1. The crash occurs independent of the chosen Graphics Controller. It also occurs without configured audio and network devices.

The STATUS_DATATYPE_MISALIGNMENT exception inside the Windows guest OS is the most prevalent type of crash. There are several other types of crashes occurring less often, but always in the Windows kernel space. I could add them here if necessary.

Are there any other known problems with VirtualBox and 10th/11th generation Intel CPUs?

Last edited 3 months ago by fth0 (previous) (diff)

comment:2 Changed 7 weeks ago by hottobar

Tested again the same VM, Linux 5.10.25 mainline kernel, and VBox 6.1.18 r142142 (Oracle's repo) with the same results:

00:00:05.011688 GIM: HyperV: Guest indicates a fatal condition! P0=0x1e P1=0xffffffff80000002 P2=0xfffff8063ec6457e P3=0x48589ee8 P4=0x0
00:00:05.011754 GIMHv: BugCheck 1e {ffffffff80000002, fffff8063ec6457e, 48589ee8, 0}
00:00:05.011755 KMODE_EXCEPTION_NOT_HANDLED
00:00:05.011755 P1: ffffffff80000002 - exception code - STATUS_DATATYPE_MISALIGNMENT
00:00:05.011755 P2: fffff8063ec6457e - EIP/RIP
00:00:05.011755 P3: 0000000048589ee8 - Xcpt param #0
00:00:05.011755 P4: 0000000000000000 - Xcpt param #1

comment:3 Changed 12 days ago by hottobar

Tested again the same VM, Linux 5.10.25 mainline kernel, and VBox 6.1.20 r143896 (Oracle's repo) with the same results:

00:30:18.095230 GIM: HyperV: Guest indicates a fatal condition! P0=0x1e P1=0xffffffff80000002 P2=0xfffff80582ce4793 P3=0xffffba80840362fc P4=0x7010008004002001
00:30:18.095305 GIMHv: BugCheck 1e {ffffffff80000002, fffff80582ce4793, ffffba80840362fc, 7010008004002001}
00:30:18.095306 KMODE_EXCEPTION_NOT_HANDLED
00:30:18.095306 P1: ffffffff80000002 - exception code - STATUS_DATATYPE_MISALIGNMENT
00:30:18.095306 P2: fffff80582ce4793 - EIP/RIP
00:30:18.095306 P3: ffffba80840362fc - Xcpt param #0
00:30:18.095306 P4: 7010008004002001 - Xcpt param #1

comment:4 Changed 4 days ago by slvr

FYI, I still see a kernel mode exception crash w/a Win10 (32-bit) VM and Linux x86_64 5.10.34 mainline kernel and VBox 6.1.22...

00:00:07.120137 GIM: HyperV: Guest indicates a fatal condition! P0=0x7f P1=0x11 P2=0x0 P3=0x0 P4=0x0
00:00:07.120177 GIMHv: BugCheck 7f {11, 0, 0, 0}
00:00:07.120178 UNEXPECTED_KERNEL_MODE_TRAP
00:00:07.120178 P1: 0000000000000011 - x86 trap number
00:00:07.120178 P2: 0000000000000000 - reserved/errorcode?
00:00:07.120178 P3: 0000000000000000 - reserved
00:00:07.120178 P4: 0000000000000000 - reserved
00:00:10.432240 GUI: Request to close active machine-window.
Last edited 4 days ago by slvr (previous) (diff)

comment:5 Changed 2 days ago by farzad

I am experiencing the same issue:

02:25:53.052036 GIM: HyperV: Guest indicates a fatal condition! P0=0x1e P1=0xffffffff80000002 P2=0xfffff8011bee4793 P3=0xffff890f26a0233a P4=0x7010008004002001
02:25:53.052096 GIMHv: BugCheck 1e {ffffffff80000002, fffff8011bee4793, ffff890f26a0233a, 7010008004002001}
02:25:53.052098 KMODE_EXCEPTION_NOT_HANDLED
02:25:53.052098 P1: ffffffff80000002 - exception code - STATUS_DATATYPE_MISALIGNMENT
02:25:53.052099 P2: fffff8011bee4793 - EIP/RIP
02:25:53.052099 P3: ffff890f26a0233a - Xcpt param #0
02:25:53.052099 P4: 7010008004002001 - Xcpt param #1
02:25:56.008625 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
02:25:56.843982 AHCI#0: Reset the HBA
02:25:56.843993 VD#0: Cancelling all active requests
02:25:56.844190 AHCI#0: Port 0 reset
02:25:56.845278 VD#0: Cancelling all active requests
02:26:07.277458 VMMDev: Guest Log: VBoxGuest: BugCheck! P0=0x1e P1=0xffffffff80000002 P2=0xfffff8011bee4793 P3=0xffff890f26a0233a P4=0x7010008004002001
02:26:07.277620 GIM: HyperV: Reset initiated through MSR
02:26:07.277640 Changing the VM state from 'RUNNING' to 'RESETTING'
02:26:07.279613 GIM: HyperV: Resetting MMIO2 regions and MSRs

Linux Host: Linux pop-os 5.11.0-7614-generic #15~1618626693~20.10~ecb25cd-Ubuntu SMP Thu Apr 22 16:00:45 UTC x86_64 x86_64 x86_64 GNU/Linux
Guest: Windows 10
CPU: 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz
VirtualBox: 6.1.18

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use