QEMU Windows 10 instant BSOD

Hello, I'm having issues with running Windows 10 in QEMU.

When I boot up the Windows 10 ISO image with QEMU, after the BIOS boot screen I get an instant BSOD, error code: PAGE FAULT IN NONPAGED AREA. I've tried creating the VM with BIOS and UEFI, 2 threads and 10, 4GB of memory and 8GB. I've tried running both the official Windows 10 21H1 ISO and a Windows 11 ISO. I also ran Memtest86+ and had no errors. I can also confirm, that Linux distros boot normally, I've run both Arch and Manjaro.

Here's my inxi -Faz output:

Kernel: 5.14.8-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.1.0  
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=3b834534-b26f-47f7-bed0-5303c8f14998  
rw [email protected] quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
systemd.unified_cgroup_hierarchy=1 loglevel=3
Desktop: KDE Plasma 5.22.5 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11 vt: 1 dm: SDDM  
Distro: Garuda Linux base: Arch Linux  
Machine:   Type: Desktop Mobo: ASUSTeK model: ROG STRIX B450-F GAMING v: Rev 1.xx serial: <filter>  
BIOS: American Megatrends v: 4502 date: 07/13/2021  
CPU:       Info: 6-Core model: AMD Ryzen 5 3600 bits: 64 type: MT MCP arch: Zen 2 family: 17 (23)  
model-id: 71 (113) stepping: 0 microcode: 8701021 cache: L2: 3 MiB  
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 86241  
Speed: 3901 MHz min/max: 2200/3600 MHz boost: enabled Core speeds (MHz): 1: 3901 2: 3933  
3: 4103 4: 3968 5: 3368 6: 3916 7: 4037 8: 3938 9: 3855 10: 4115 11: 4051 12: 3893  
Vulnerabilities: Type: itlb_multihit status: Not affected  
Type: l1tf status: Not affected  
Type: mds status: Not affected  
Type: meltdown status: Not affected  
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp  
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization  
Type: spectre_v2  
mitigation: Full AMD retpoline, IBPB: conditional, STIBP: conditional, RSB filling  
Type: srbds status: Not affected  
Type: tsx_async_abort status: Not affected  
Graphics:  Device-1: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] vendor: Sapphire Limited  
driver: amdgpu v: kernel bus-ID: 09:00.0 chip-ID: 1002:67df class-ID: 0300  
Device-2: Logitech Webcam C110 type: USB driver: snd-usb-audio,uvcvideo bus-ID: 1-6:4  
chip-ID: 046d:0829 class-ID: 0102  
Display: x11 server: X.Org 1.20.13 compositor: kwin_x11 driver: loaded: amdgpu,ati  
unloaded: modesetting alternate: fbdev,vesa display-ID: :0 screens: 1  
Screen-1: 0 s-res: 3280x1080 s-dpi: 96 s-size: 865x285mm (34.1x11.2") s-diag: 911mm (35.9")  
Monitor-1: DisplayPort-1 res: 1360x768 hz: 60 dpi: 84 size: 410x230mm (16.1x9.1")  
diag: 470mm (18.5")  
Monitor-2: HDMI-A-0 res: 1920x1080 hz: 60 dpi: 102 size: 477x268mm (18.8x10.6")  
diag: 547mm (21.5")  
OpenGL: renderer: Radeon RX 570 Series (POLARIS10 DRM 3.42.0 5.14.8-zen1-1-zen LLVM 12.0.1)  
v: 4.6 Mesa 21.2.3 direct render: Yes  
Audio:     Device-1: AMD Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590] vendor: Sapphire Limited  
driver: snd_hda_intel v: kernel bus-ID: 09:00.1 chip-ID: 1002:aaf0 class-ID: 0403  
Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel  
bus-ID: 0b:00.4 chip-ID: 1022:1487 class-ID: 0403  
Device-3: Logitech Webcam C110 type: USB driver: snd-usb-audio,uvcvideo bus-ID: 1-6:4  
chip-ID: 046d:0829 class-ID: 0102  
Sound Server-1: ALSA v: k5.14.8-zen1-1-zen running: yes  
Sound Server-2: JACK v: 1.9.19 running: no  
Sound Server-3: PulseAudio v: 15.0 running: no  
Sound Server-4: PipeWire v: 0.3.38 running: yes  
Network:   Device-1: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel port: e000
bus-ID: 04:00.0 chip-ID: 8086:1539 class-ID: 0200
IF: enp4s0 state: up speed: 100 Mbps duplex: full mac: <filter>
IF-ID-1: virbr0 state: down mac: <filter>
Bluetooth: Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB driver: btusb v: 0.8
bus-ID: 3-1.3:3 chip-ID: 0a12:0001 class-ID: e001
Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Drives:    Local Storage: total: 2.95 TiB used: 134.67 GiB (4.5%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 980 1TB size: 931.51 GiB
block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
rev: 1B4QFXO7 temp: 33.9 C scheme: MBR
ID-2: /dev/sda maj-min: 8:0 vendor: Kingston model: SUV400S37240G size: 223.57 GiB block-size:
physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 37R5
scheme: GPT
ID-3: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST2000DM006-2DM164 size: 1.82 TiB
block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200
serial: <filter> rev: CC26 scheme: GPT
Partition: ID-1: / raw-size: 931.51 GiB size: 931.51 GiB (100.00%) used: 119.48 GiB (12.8%) fs: btrfs
dev: /dev/nvme0n1p1 maj-min: 259:1
ID-2: /home raw-size: 931.51 GiB size: 931.51 GiB (100.00%) used: 119.48 GiB (12.8%) fs: btrfs
dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /var/log raw-size: 931.51 GiB size: 931.51 GiB (100.00%) used: 119.48 GiB (12.8%)
fs: btrfs dev: /dev/nvme0n1p1 maj-min: 259:1
ID-4: /var/tmp raw-size: 931.51 GiB size: 931.51 GiB (100.00%) used: 119.48 GiB (12.8%)
fs: btrfs dev: /dev/nvme0n1p1 maj-min: 259:1
Swap:      Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 15.54 GiB used: 2.29 GiB (14.7%) priority: 100 dev: /dev/zram0
Sensors:   System Temperatures: cpu: 37.8 C mobo: N/A gpu: amdgpu temp: 52.0 C
Fan Speeds (RPM): N/A gpu: amdgpu fan: 780
Info:      Processes: 422 Uptime: 1d 4h 5m wakeups: 0 Memory: 15.55 GiB used: 8.54 GiB (54.9%)
Init: systemd v: 249 tool: systemctl Compilers: gcc: 11.1.0 clang: 12.0.1 Packages:
pacman: 1855 lib: 540 flatpak: 0 Shell: Bash v: 5.1.8 running-in: konsole inxi: 3.3.06

Strange ... I have Windows 10 1607 LTSB works in QEMU. Try this version, although with newer problems should not be. With Windows 7 there is such a problem?

This is not a Garuda issue.

If you wish support for Windows please seek support elsewhere.

5 Likes

Hi there, welcome to the community.
You may want to try virtualbox. You can get it installed from setup assistant. It was working last time I used it (For some weird stuff)

Also, you may message me or other moderators in case you want further discussion.
But remember, we can't fix QEMU or any other VM software. And your above issue is most probably problem with QEMU itself.

1 Like