Cannot Install Windows 10 in New VM
-
Hi,
I've just created a new VM to install the latest version of Windows 10 in. I selected the Windows 10 template and pointed it at the ISO, but whenever I tried to boot it, I get a BSOD with the error "SYSTEM THREAD EXCEPTION NOT HANDLED".
Other VMs on this server are working fine.
-
@mickwilli Could you provide the host hardware configuration and ISO being used?
-
@dinhngtu can you please explain what you mean and exactly what information you’re asking for?
-
@mickwilli What host hardware do you have and which ISO did you use for the Windows installation? I assume you used the default Windows 10 template?
-
@dinhngtu the host is a Dell Precision T3610 workstation with Intel Xeon processor and 120GB RAM. I used the default Windows 10 (64bit) template. The ISO was built with the Microsoft Windows 10 media creator about a month ago and it successfully installed a VirtualBox VM. The ISO is located on a NFS SR.
-
is the vm set to bios, uefi? is secure boot enabled in the vm?
-
Also what Xeon model exactly?
-
@acebmxer it is UEFI, and I’ve tried with and without secure boot enabled.
-
@olivierlambert it is a “ Intel(R) Xeon(R) CPU E5-2660 v2 @ 2.20GHz”
-
Could you provide a crash dump?
-
@dinhngtu given it’s trying to boot from the installer, where would it save the crash dump to?
-
@mickwilli Forget that, I just realized E5-2660 v2 is way too old for Windows 10. See the supported processors.
-
@dinhngtu Win10 on XCP 8.3 with E5-2600v2 works just fine for me...
-
@Andrew Still, having an unsupported CPU makes it somewhat difficult to troubleshoot the issue, especially when it's a recent ISO.
SYSTEM_THREAD_EXCEPTION_NOT_HANDLEDis sometimes associated with execution of unsupported instructions (though I don't know if that's the case here). For instance, there's a poke-of-death on some newer Intel CPUs related to the Architectural LBR feature (https://docs.xcp-ng.org/troubleshooting/windows-pv-tools/#windows-bug-check-0x3b-system_service_exception-on-systems-with-newer-intel-cpus). -
@mickwilli Do you know how to create custom Windows PE ISOs? It might be possible to put the boot kernel in the ISO into debugging mode, then using the Connecting to guests using serial console guide to collect a crash analysis.
-
@dinhngtu sorry, I don't know how to do that offhand. If you point me in the direction of some instructions, I'm happy to give it a go.
-
@mickwilli You can extract the ISO, run the following command:
bcdedit /store <extracted ISO path>\Boot\BCD /set {default} debug on bcdedit /store <extracted ISO path>\Boot\BCD /dbgsettings serial debugport:1 baudrate:115200Then repack the ISO.
You can also create a new ISO using this guide: https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/winpe-create-usb-bootable-drive then run the two commands above on
media\Boot\BCDbefore you runMakeWinPEMedia. -
@dinhngtu Thanks. I'll try and give that a go in the next few days and will report back.
Note that I have Windows 10 1803 installed without any issues. Trying to update to 22H2 fails with the same blue screen error as you'd expect. Sadly, no crash dump as it seems to fail very early in the boot process.
-
@mickwilli said in Cannot Install Windows 10 in New VM:
@dinhngtu Thanks. I'll try and give that a go in the next few days and will report back.
Note that I have Windows 10 1803 installed without any issues. Trying to update to 22H2 fails with the same blue screen error as you'd expect. Sadly, no crash dump as it seems to fail very early in the boot process.
Do you get any additional BSOD details in
xl dmesg? -
@TeddyAstie apologies for the tardy reply.
This is the tail end of note from xl dmesg:
(XEN) [1029242.324130] d17v1 VIRIDIAN GUEST_CRASH: 0x7e 0xffffffffc0000094 0xfffff80272497e14 0xffff9f8d4689e7c8 0xffff9f8d4689e000 (XEN) [1029490.963515] d18v1 VIRIDIAN GUEST_CRASH: 0x7e 0xffffffffc0000094 0xfffff80251497e14 0xffffac025109e7c8 0xffffac025109e000 (XEN) [1029557.664243] d19v1 VIRIDIAN GUEST_CRASH: 0x7e 0xffffffffc0000094 0xfffff8073c497e14 0xfffff4895049e7c8 0xfffff4895049e000 (XEN) [1029654.360658] d20v1 VIRIDIAN GUEST_CRASH: 0x7e 0xffffffffc0000094 0xfffff80030497e14 0xffff848fdee9e7c8 0xffff848fdee9e000 (XEN) [1029786.928461] d21v0 VIRIDIAN GUEST_CRASH: 0x7e 0xffffffffc0000094 0xfffff80639697e14 0xfffff50ea42897c8 0xfffff50ea4289000 (XEN) [1030181.784003] d23v0 VIRIDIAN GUEST_CRASH: 0x7e 0xffffffffc0000094 0xfffff80749297e14 0xfffffb0fe66897c8 0xfffffb0fe6689000 (XEN) [1030346.926513] d24v0 VIRIDIAN GUEST_CRASH: 0x7e 0xffffffffc0000094 0xfffff80337c97e14 0xffff8304baa897c8 0xffff8304baa89000 (XEN) [1030399.047734] d25v0 VIRIDIAN GUEST_CRASH: 0x7e 0xffffffffc0000094 0xfffff80542c97e14 0xfffff204226897c8 0xfffff20422689000 (XEN) [1529444.878620] d13v1 VIRIDIAN GUEST_CRASH: 0x7a 0x117a30 0xc00000c0 0x2c9f6be0 0x22f46000 (XEN) [1529695.616425] d30v1 VIRIDIAN GUEST_CRASH: 0x7e 0xffffffffc0000094 0xfffff80355497e14 0xffff8387fbcb37c8 0xffff8387fbcb3000 (XEN) [1546475.266724] d49v0 VIRIDIAN GUEST_CRASH: 0x7e 0xffffffffc0000094 0xfffff80649896f0a 0xffffba8689a897c8 0xffffba8689a89000 (XEN) [2060275.879001] d54v0 VIRIDIAN GUEST_CRASH: 0x7e 0xffffffffc0000094 0xfffff8027a497e14 0xfffff302fea897c8 0xfffff302fea89000The last line appears to be from my most recent test with a fresh VM (just to check those messages were related).
