Windows Bluescreen ( KMODE EXCEPTION NOT HANDLED )

User Support General
1

Hi everyone,

I installed windows 10 on Qubes 4.2 following the standard installation using the official Microsoft ISO.
The setup worked fine but after few minutes using the machine randomly the windows crash.
I already tried setup other windows hvm, and I got one crash trying to setup other, so the error is not related after startup.
I’m providing enough RAM and VCPU, and I’m currently using certified hardware for Qubes.
I have no idea how should I fix this, I have been searching into every post, did not saw anything relevant.
I am also new user of Qubes, I am enjoying everything and experience, just have this little problem.
Any ideas how to fix this?

Thanks.

2

How much memory did you give to the qube?
Did you disable memory balancing?

3

I gave 8192 MB to the qube and yes, i disabled the memory balancing.

4

Which edition of Windows 10 did you install? I never had issue with a “home” edition but I didn’t use it much either, at least it survived staying up for hours.

5

I’m getting the error also in the first boot ISO load ( on setup ), I tried right now other Microsoft Windows ISO ( the enterprise version ) Also got the bluescreen on setup.
Do you want see the logs ? Maybe can help ?

6

I believe this maybe be a problem with drivers, its normally on Qubes OS Global Config the “Xen:” should filled with “unknown” value ?

7

You can check the logs but I’m not sure that there will be anything valuable.
Run in dom0:

journalctl -f -n0

Try to install Windows and when it’ll get BSOD check the log in journalctl output, Xen log using this command:

xl dmesg

And your Windows stubdom log in /var/log/xen/console/guest-VMNAME-dm.log.

It’s an unrelated bug with Qubes Global Config displaying Xen version.

8 
xl dmesg

(XEN) Built-in command line: ept=exec-sp spec-ctrl=unpriv-mmio
Xen 4.17.4
(XEN) Xen version 4.17.4 (mockbuild@[unknown]) (gcc (GCC) 12.3.1 20230508 (Red Hat 12.3.1-1)) debug=n Fri Apr 26 07:15:54 GMT 2024
(XEN) Latest ChangeSet:
(XEN) Bootloader: kexec 2.0.26
(XEN) Command line: placeholder console=none dom0_mem=min:1024M dom0_mem=max:4096M ucode=scan smt=off gnttab_max_frames=2048 gnttab_max_maptrack_frames=4096 no-real-mode reboot=no vga=current
(XEN) Xen image load base address: 0
(XEN) Video information:
(XEN) VGA is text mode 80x25, font 8x16
(XEN) Disc information:
(XEN) Found 0 MBR signatures
(XEN) Found 0 EDD information structures
(XEN) Enabling Supervisor Shadow Stacks
(XEN) Enabling Indirect Branch Tracking
(XEN) Multiboot-e820 RAM map:
(XEN) [0000000000000000, 0000000000000fff] (reserved)
(XEN) [0000000000001000, 000000000009ffff] (usable)
(XEN) [00000000000a0000, 00000000000fffff] (reserved)
(XEN) [0000000000100000, 0000000076990fff] (usable)
(XEN) [0000000076991000, 00000000803fffff] (reserved)
(XEN) [00000000c0000000, 00000000cfffffff] (reserved)
(XEN) [00000000f8000000, 00000000f9ffffff] (reserved)
(XEN) [00000000fb000000, 00000000fb000fff] (reserved)
(XEN) [00000000fc800000, 00000000fe7fffff] (reserved)
(XEN) [00000000feb00000, 00000000feb7ffff] (reserved)
(XEN) [00000000fec00000, 00000000fecfffff] (reserved)
(XEN) [00000000fed40000, 00000000fed6ffff] (reserved)
(XEN) [00000000fed80000, 00000000fed87fff] (reserved)
(XEN) [00000000fed90000, 00000000fed92fff] (reserved)
(XEN) [00000000feda0000, 00000000feda1fff] (reserved)
(XEN) [00000000fedc0000, 00000000feddffff] (reserved)
(XEN) [00000000ff000000, 00000000ffffffff] (reserved)
(XEN) [0000000100000000, 000000107fbfffff] (usable)
(XEN) New Xen image base address: 0x76200000
(XEN) ACPI: RSDP 000F0000, 0024 (r2 COREv4)
(XEN) ACPI: XSDT 7699E0E0, 0064 (r1 COREv4 COREBOOT 0 CORE 20230628)
(XEN) ACPI: FACP 769A3B30, 0114 (r6 COREv4 COREBOOT 0 CORE 20230628)
(XEN) ACPI: DSDT 7699E280, 58A7 (r2 COREv4 COREBOOT 20110725 INTL 20230628)
(XEN) ACPI: FACS 7699E240, 0040
(XEN) ACPI: SSDT 769A3C50, 5575 (r2 COREv4 COREBOOT 0 CORE 20230628)
(XEN) ACPI: MCFG 769A91D0, 003C (r1 COREv4 COREBOOT 0 CORE 20230628)
(XEN) ACPI: TPM2 769A9210, 004C (r4 COREv4 COREBOOT 0 CORE 20230628)
(XEN) ACPI: LPIT 769A9260, 0094 (r0 COREv4 COREBOOT 0 CORE 20230628)
(XEN) ACPI: APIC 769A9300, 0152 (r3 COREv4 COREBOOT 0 CORE 20230628)
(XEN) ACPI: DMAR 769A9460, 0088 (r1 COREv4 COREBOOT 0 CORE 20230628)
(XEN) ACPI: HPET 769A94F0, 0038 (r1 COREv4 COREBOOT 0 CORE 20230628)
(XEN) System RAM: 65381MB (66950336kB)
(XEN) Domain heap initialised
(XEN) WARNING: APIC ID 0x17161514 and/or ACPI ID 0x10 beyond limit - processor ignored
(XEN) WARNING: APIC ID 0x17161514 and/or ACPI ID 0x11 beyond limit - processor ignored
(XEN) WARNING: APIC ID 0x17161514 and/or ACPI ID 0x12 beyond limit - processor ignored
(XEN) WARNING: APIC ID 0x17161514 and/or ACPI ID 0x13 beyond limit - processor ignored
(XEN) WARNING: APIC ID 0x17161514 and/or ACPI ID 0x14 beyond limit - processor ignored
(XEN) WARNING: APIC ID 0x17161514 and/or ACPI ID 0x15 beyond limit - processor ignored
(XEN) WARNING: APIC ID 0x17161514 and/or ACPI ID 0x16 beyond limit - processor ignored
(XEN) WARNING: APIC ID 0x17161514 and/or ACPI ID 0x17 beyond limit - processor ignored
(XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-119
(XEN) Switched to APIC driver x2apic_mixed
(XEN) microcode: CPU0 updated from revision 0x42c to 0x433, date = 2023-12-05
(XEN) CPU0: TSC: 38400000 Hz * 130 / 2 = 2496000000 Hz
(XEN) CPU0: bus: 100 MHz base: 2500 MHz max: 4700 MHz
(XEN) CPU0: 400 … 2500 MHz
(XEN) xstate: size: 0xa88 and states: 0x207
(XEN) CPU0 CMCI LVT vector (0xf9) already installed
(XEN) Unrecognised CPU model 0x9a - assuming vulnerable to LazyFPU
(XEN) Speculative mitigation facilities:
(XEN) Hardware hints: RDCL_NO EIBRS RRSBA SKIP_L1DFL MDS_NO TAA_NO SBDR_SSDP_NO FBSDP_NO PSDP_NO GDS_NO
(XEN) Hardware features: IBPB IBRS STIBP SSBD PSFD L1D_FLUSH MD_CLEAR RFDS_CLEAR
(XEN) Compiled-in support: INDIRECT_THUNK HARDEN_ARRAY HARDEN_BRANCH HARDEN_GUEST_ACCESS HARDEN_LOCK
(XEN) Xen settings: BTI-Thunk: JMP, SPEC_CTRL: IBRS+ STIBP+ SSBD- PSFD- BHI_DIS_S+, Other: IBPB-ctxt VERW BRANCH_HARDEN
(XEN) Support for HVM VMs: MSR_SPEC_CTRL MSR_VIRT_SPEC_CTRL RSB EAGER_FPU VERW
(XEN) Support for PV VMs: MSR_SPEC_CTRL EAGER_FPU VERW
(XEN) XPTI (64-bit PV only): Dom0 disabled, DomU disabled (with PCID)
(XEN) PV L1TF shadowing: Dom0 disabled, DomU disabled
(XEN) Using scheduler: SMP Credit Scheduler rev2 (credit2)
(XEN) Initializing Credit2 scheduler
(XEN) Disabling HPET for being unreliable
(XEN) Platform timer is 3.580MHz ACPI PM Timer
(XEN) Detected 2496.009 MHz processor.
(XEN) cpu0: spurious 8259A interrupt: IRQ7
(XEN) Intel VT-d iommu 0 supported page sizes: 4kB, 2MB, 1GB
(XEN) Intel VT-d iommu 1 supported page sizes: 4kB, 2MB, 1GB
(XEN) Intel VT-d Snoop Control not enabled.
(XEN) Intel VT-d Dom0 DMA Passthrough not enabled.
(XEN) Intel VT-d Queued Invalidation enabled.
(XEN) Intel VT-d Interrupt Remapping enabled.
(XEN) Intel VT-d Posted Interrupt not enabled.
(XEN) Intel VT-d Shared EPT tables enabled.
(XEN) I/O virtualisation enabled
(XEN) - Dom0 mode: Relaxed
(XEN) Interrupt remapping enabled
(XEN) Enabled directed EOI with ioapic_ack_old on!
(XEN) Enabling APIC mode. Using 1 I/O APICs
(XEN) ENABLING IO-APIC IRQs
(XEN) → Using old ACK method
(XEN) …no 8254 timer found - trying HPET Legacy Replacement Mode
(XEN) Allocated console ring of 32 KiB.
(XEN) VMX: Supported advanced features:
(XEN) - APIC MMIO access virtualisation
(XEN) - APIC TPR shadow
(XEN) - Extended Page Tables (EPT)
(XEN) - Virtual-Processor Identifiers (VPID)
(XEN) - Virtual NMI
(XEN) - MSR direct-access bitmap
(XEN) - Unrestricted Guest
(XEN) - APIC Register Virtualization
(XEN) - Virtual Interrupt Delivery
(XEN) - Posted Interrupt Processing
(XEN) - VMCS shadowing
(XEN) - VM Functions
(XEN) - Virtualisation Exceptions
(XEN) - TSC Scaling
(XEN) HVM: ASIDs enabled.
(XEN) HVM: VMX enabled
(XEN) HVM: Hardware Assisted Paging (HAP) detected
(XEN) HVM: HAP page sizes: 4kB, 2MB, 1GB
(XEN) altcall: Optimised away 237 endbr64 instructions
(XEN) [VT-D]DMAR:[DMA Read] Request device [0000:00:02.0] fault addr 7c980000
(XEN) [VT-D]DMAR: reason 01 - Present bit in root entry is clear
(XEN) [VT-D]DMAR:[DMA Read] Request device [0000:00:02.0] fault addr 7ccfd000
(XEN) [VT-D]DMAR: reason 01 - Present bit in root entry is clear
(XEN) [VT-D]DMAR:[DMA Read] Request device [0000:00:02.0] fault addr 7ccb8000
(XEN) [VT-D]DMAR: reason 01 - Present bit in root entry is clear
(XEN) [VT-D]DMAR:[DMA Read] Request device [0000:00:02.0] fault addr 7ccba000
(XEN) [VT-D]DMAR: reason 01 - Present bit in root entry is clear
(XEN) [VT-D]DMAR:[DMA Read] Request device [0000:00:02.0] fault addr 7ccbd000
(XEN) [VT-D]DMAR: reason 01 - Present bit in root entry is clear
(XEN) microcode: CPU2 updated from revision 0x42c to 0x433, date = 2023-12-05
(XEN) microcode: CPU4 updated from revision 0x42c to 0x433, date = 2023-12-05
(XEN) microcode: CPU6 updated from revision 0x42c to 0x433, date = 2023-12-05
(XEN) microcode: CPU8 updated from revision 0x42c to 0x433, date = 2023-12-05
(XEN) microcode: CPU12 updated from revision 0x42c to 0x433, date = 2023-12-05
(XEN) Brought up 12 CPUs
(XEN) Scheduling granularity: cpu, 1 CPU per sched-resource
(XEN) Initializing Credit2 scheduler
(XEN) Dom0 has maximum 1160 PIRQs
(XEN) Xen kernel: 64-bit, lsb
(XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x200000 → 0x3800000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 000000104c000000->0000001050000000 (1022522 pages to be allocated)
(XEN) Init. ramdisk: 000000107d63a000->000000107fbff079
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: ffffffff80200000->ffffffff83800000
(XEN) Phys-Mach map: 0000008000000000->0000008000800000
(XEN) Start info: ffffffff83800000->ffffffff838004b8
(XEN) Page tables: ffffffff83801000->ffffffff83822000
(XEN) Boot stack: ffffffff83822000->ffffffff83823000
(XEN) TOTAL: ffffffff80000000->ffffffff83c00000
(XEN) ENTRY ADDRESS: ffffffff8273f8f0
(XEN) Dom0 has maximum 12 VCPUs
(XEN) Initial low memory virq threshold set at 0x4000 pages.
(XEN) Scrubbing Free RAM in background
(XEN) Std. Loglevel: Errors and warnings
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) *** Serial input to DOM0 (type ‘CTRL-a’ three times to switch input)
(XEN) Freed 668kB init memory

9

There are no Xen errors after Qubes OS startup in xl dmesg. Check the other logs.

10

windows.log (7.1 KB)

11

Nothing relevant here as well.

12

What should I do ? Do you think can be my xen version ? I d’ont know why I have 2022 xen version, this is normal ? I have dom0 updated and setuped Qubes 4.2.1 ISO.

13

Your Xen version is:

And it’s normal version for Qubes OS 4.2.1.

I’m not sure why do you have this issue.
I don’t know where did you get your ISOs but try to download the Windows 10 ISO directly from microsoft site if you got them from somewhere else.

14

Its from microsoft site, I also tried two different Windows, same experience.

15

Did you do anything special for creating the qube, other than making a new HVM qube, choosing the cpu/memory/disk space and loading an iso in it?

16

Only this commands:
qvm-create --class StandaloneVM --label orange --property virt_mode=hvm WindowsNew
qvm-volume extend WindowsNew:root 300g
qvm-prefs WindowsNew memory 8192
qvm-prefs WindowsNew maxmem 8192
qvm-prefs WindowsNew kernel ‘’
qvm-prefs WindowsNew qrexec_timeout 7200

17

Is your CPU an 10th/11th generation intel?

It seems this bug happens in virtualbox as well with these gens of CPUs,

https://www.virtualbox.org/ticket/19998

More details in this and possibly a fix here if split_lock_detect=off kernel parameter can be used on Qubes OS.

2 Likes
18

Yes, its 11th gen.

19

Set maxmem to 0 to disable memory balancing or use GUI Qube Settings to disable it.

20

It is already disabled.