[Bug]: Kernel Panics or BSODs in Windows XP Professional x64 Edition in Modern Windows 11 Hosts

[TryinAndTestin]

Version

7.2.8, 7.2.10, 7.2.12

Host OS Type

Windows

Host OS name + version

Windows 11 Build 26200.8737

Host Architecture

x86

Guest OS Type

Windows

Guest Architecture

x86

Guest OS name + version

Windows XP Professional x64 Edition SP2

Component

VMM

What happened?

Description:
Generally, it is observed that in Virtualbox 7.2 environments with Windows NT 5.2 kernel (here, Windows XP x64) guests in Windows 11 hosts in modern processors, running an instance of Windows XP Professional x64 Edition (NT 5.2) crashes with kernel panics or BSODs such as SYSTEM_SERVICE_EXCEPTION or IRQL_NOT_LESS_OR_EQUAL.
This kernel level stop errors occur when the guest operating system handles modern intensive multi threaded workloads with heavy memory paging demands, especially when rendering complex modern websites using browser infrastructures (tested extensively with Supermium and occasionally in Internet Explorer).
Update: The same error occurs even in Virtualbox 7.2.12.

The crashdump and the log files are given in the .zip file.

XPx64Errors.zip

Technical Isolation Details:

1. Kernel-Mode Failure Isolation: Evaluation of the guest crash dump footprint indicates that while the active process context is flagged under the browser (chrome.exe), the execution failure vectors strictly into a kernel-mode address space violation. The crash is not an application-level user-mode exception, but an unhandled system trap occurring while processing core memory-page translations inside the hypervisor pipeline.
2. Crash Progression Behavior: On a fresh VM boot, running the workload often results in an initial silent user-mode process termination (the browser force-closes without warnings). Subsequent immediate launch attempts followed by visitng heavy sites or multi tab workloads result in an instantaneous 0x0000003B or 0x0000000A or sometimes 0x0000007E BSOD, indicating that the initial execution leaves behind orphaned or corrupted kernel page table states that cascade into a structural VMM crash on the next allocation cycle.
3. Architectural Scope Restrictions: This behavior is isolated strictly to the 64-bit NT 5.2 kernel architecture. Under identical conditions, host hypervisor configurations, and workloads, the bug cannot be replicated on Windows XP 32-bit (x86) guests or Windows Vista x64 guests.
4. Host Hardware Vector (Intel Hybrid Architecture): The host machine runs an Intel Core i7-14700HX (Raptor Lake Refresh) featuring asymmetric Performance-cores and Efficient-cores. The alternating 0x3B/0x0A loop suggests a failure within VirtualBox's VMM engine when handling thread-scheduling or core-migration events across P/E-cores under Windows 11 host execution streams.
5. Guest Additions: The issue reproduces natively regardless of whether VirtualBox Guest Additions are installed or completely removed.

Update: On testing across VboxSVGA and VboxVGA controllers, in VboxVGA, the guest OS seems to crash with kernel level stop errors or BSODs on almost visiting each and every website while in the case of VboxSVGA, the guest OS seems to load certain simple or moderately bloated websites. However heavy websites and multi tab workloads force an immediate guest OS kernel level crash regardless of the controller used.

Expected Behavior:
The Virtual Machine Monitor (VMM) should accurately map, translate, and process nested paging structures and modern CPU instructions called by the guest kernel to the host CPU via the Windows Hypervisor Platform (WHV) / NEM framework without causing page-table address variations or kernel-mode IRQL traps.

Screenshots
The screenshots are also given to help solving this issue
A recorded video is also given showing the crash in the .gif format.

How can we reproduce this?

Steps to reproduce the behavior:

1. Install Windows XP x64 in Virtualbox 7.2.8 or 7.2.10 or 7.2.12 with Windows 11 as host.
2. Install Supermium 64-bit.
3. Open a heavy website (like any news website or any other heavy website) or multiple tabs.
4. The system crashes with SYSTEM_SERVICE_EXCEPTION or IRQL_NOT_LESS_OR_EQUAL BSOD or in certain cases, 0x0000007E.

Did you upload all of your necessary log files, screenshots, etc.?

• Yes, I've uploaded all pertinent files to this issue.