Windows 10: Hyper V causes BSOD on Windows 10

I was trying to install Docker Desktop and it prompted me to enable Hyper V on my machine.

After enabling Hyper V, Windows went into BSOD with SYSTEM_THREAD_EXCEPTION_NOT_HANDLED error.

I have searched high and low for solution but none worked.

My Hardware:

- CPU: intel i7-8086K (i7-8700K equivalent)
- Motherboard: Gigabyte Z370N
- BIOS: I have enabled VT-d, but couldn't find VT-x setting

VMWare Workstation and Virtual Box worked which suggest that my machine already support virtualization.

Task Manager also indicated that Virtualization is enabled.

Hyper V also runs without issue if run on the Win10 guest OS on VMWare.

What could be wrong with my setup?

submitted by /u/watchy2
[link] [comments]

:)

 

Trying to Disable Hyper-V, Getting BSOD

I have been trying to disable Hyper-V so that I can use VirtualBox. Each time I attempt to remove Hyper-V through Windows Features, the OS shuts down, and then hits a BSODs during boot. I am then able to return to a restore point.

I have tried:

• Removing the Hyper-V features after a clean boot.
• Manually disabling the Hyper-V service, manually removing Hyper-V network adapters, and then disabling Hyper-V in Windows Featuers.

I believe the issue might be similar to this (but not the exact same): Trying disable Hyper-V cause blue screen when windows restart

 

Firmware update or hyper-v causes automatic repair loop everytime

Microsoft does not upgrade BIOS firmware you have to install the BIOS firmware from your computer manufacturer website.

Use the following steps to enable Hyper-V on Windows 10:

• Open Control Panel.
• Click on Programs.
• Click on Turn Windows features on or off.
• Check the Hyper-V option making sure: Hyper-V Management Tools and Hyper-V Platform are also selected.
• Click OK to begin the process.

 

Firmware update or hyper-v causes automatic repair loop everytime

Actually some machines can receive Firmware updates through Windows Updates. As for the reboots, I would also look at Secure Boot getting fouled up and clearing that option to reset it. The Hash may not match when it reboot causing these errors.