Share via

Windows Server 2022 VM Migrated from VMWare to Azure Local with Azure Migrate BSOD on boot.

Richard Beyer 61 Reputation points
2025-11-23T13:03:01.6333333+00:00

I have attempted to migrate a Windows Server 2022 VM from VMWare 6.7 to Azure local on a Dell AX-760 cluster, Azure Local version 12.2511.1002.5. The VM is assigned :

  • 4 CPUs
  • 24 GB
  • 3 hard disks
  • one NIC, type E1000E, with 2 static IP addresses.
  • SCSI hard disk controller is set to LSI Logic SAS.

The VM has been prepared with the PowerShell script for static IP address and the Diskpart Policy=OnlineAll.

Upon completion of the migration, the VM boot loops with a BSOD. The error displayed alternates between "PAGE_FAULT_IN_NONPAGED_AREA" and "SYSTEM_THREAD_EXCEPTION_NOT_HANDLED". Secure boot is not enabled for this VM.

The same issue happens if I try to boot into safe mode and system repair does not help either.

I have migrated other Windows server 2016 and 2019 VMs successfully but this is the first Windows Server 2022 I have migrated.

Thank you,

Richard Beyer

Azure Migrate
Azure Migrate
A central hub of Azure cloud migration services and tools to discover, assess, and migrate workloads to the cloud.
0 comments
Answer accepted by question author
  1. Adam Zachary 2,025 Reputation points
    2025-11-23T23:38:34.2666667+00:00

    I’ve seen this exact problem with Windows Server 2022 specifically, and it isn’t Azure Migrate itself.

    Server 2022 on VMware often boots with LSI Logic SAS or E1000/E1000E, but Azure Local does not support those drivers once the VM is converted.

    When the OS loads and cannot find the expected storage or NIC driver, it throws PAGE_FAULT_IN_NONPAGED_AREA or SYSTEM_THREAD_EXCEPTION_NOT_HANDLED on boot.

    What fixed it for me:

    Switch the SCSI controller in VMware to VMware Paravirtual (PVSCSI) before running the migration. Server 2022 requires the correct storage driver during the image conversion.

    Change the NIC type to VMXNET3, then reinstall VMware Tools so the correct drivers load.

    Shut down, prepare again (static IP script + diskpart OnlineAll), then re-run the migration.

    Once I switched the storage and NIC controller types, the Server 2022 VM booted normally in Azure Local with no BSOD.

    Windows Server 2016 and 2019 work with LSI Logic SAS more often, but Server 2022 is much stricter with driver compatibility during Azure Local conversions.

    0 comments

5 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Richard Beyer 61 Reputation points
    2025-11-24T12:50:15.2366667+00:00

    This process worked. Thank you.

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.