Using the Android emulator in a Windows virtual machine can result in a blue screen.

Discussion in 'Windows Virtual Machine' started by mengl2, Jan 18, 2026 at 11:09 PM.

  1. mengl2

    mengl2 Bit poster

    Messages:
    3
    When using the Android emulator in a Windows virtual machine, if the 64-bit Android emulator is launched, it will cause the virtual machine to freeze and crash.Is there something wrong with my settings?
     

    Attached Files:

  2. mengl2

    mengl2 Bit poster

    Messages:
    3
    One more thing, I used an Android 9 64-bit emulator.
     
  3. Dmitry Geynisman

    Dmitry Geynisman Parallels Team

    Messages:
    710
    Hey @mengl2 , need more details to understand your environment. If you can send a tech report via the Help menu and send me the ID here, would be ideal.
    What's your use case? Games or development? Why do you run an Android emulator in a VM?
     
  4. Trishna Oobeyram

    Trishna Oobeyram Staff Member

    Messages:
    378
    Hello @mengl2
    We have created a support ticket to assist you.
    Kindly check your email for future communication.
    Regards,
     
  5. mengl2

    mengl2 Bit poster

    Messages:
    3
    Thank you for coming to help me.

    My detailed computer configuration is as follows:
    Processor: 2.3 GHz 8-Core Intel Core i9
    Graphics Card: Radeon Pro Vega 20 4 GB, Intel UHD Graphics 630 1536 MB
    Memory: 32 GB 2400 MHz DDR4
    Operating System: macOS 15.7.3 (24G419)

    My use case involves running the Yeshen emulator (https://res06.bignox.com/full/20250...0bdf.exe?filename=nox_setup_v7.0.6.2_full.exe) within a Windows virtual machine to perform penetration testing on Android apps. The Android emulators on macOS are not user-friendly, and many tools are not compatible with this scenario. When I attempt to use the multi-instance feature of the Yeshen emulator and launch an Android 9 64-bit emulator (even if only one instance is started), the Windows virtual machine crashes with a blue screen.

    Additionally, I use Parallels for some penetration testing-related tasks (some of which must be performed in Windows). These tasks are somewhat sensitive, and it is not convenient to share technical reports. I apologize for any inconvenience caused.
     
  6. fulvicearth

    fulvicearth Bit poster

    Messages:
    2
    This can happen when an Android emulator is used inside a Windows virtual machine. Both the VM and the emulator often try to access hardware virtualization at the same time, which can lead to conflicts and sometimes a blue screen.

    Disabling Hyper-V, checking virtualization settings in BIOS, or running the emulator directly on the host system instead of inside a VM usually helps. Updating drivers and the emulator version is also worth trying.

    By the way, if anyone here is interested in natural wellness products, I share info on my site as well: https://fulvicearth.com/ -- just mentioning it in case it's useful.
     

Share This Page