2

I want to enable Intel Virtualization Technology via the updated BIOS of my ASUS ROG STRIX Z270I motherboard, but each time I enable it, Windows crashes to blue screen of death with a system_service_exception error.

I chased this bug down as far as I could reviewing the Event Viewer system logs, Googling, removing software and drivers, etc. but it still persisted. I could boot into safemode with virtualization enabled, just not regular Windows.

Improve this question

3 Answers 3

Reset to default
0

I chased down something like this on my ROG ASUS running Win10 after I changed the "Core Isolation" configuration following a freeze/suspected virus.

  • Turning on Core Isolation Protection (Settings > Windows Security > Device Security):
    Results with a BSOD (driver was similar to iobc.sys) for ROG Gaming Center and Asus/Intel XTU. Core Isolation could be in conflict with Intel VT-X.

Turning off Core Isolation Protection:
Needs to be done with one the instructions below after it is turned on within Device Security

Improve this answer
0

BSOD when turning on Virtualization.

My Machine:

  • Windows 10 (Host)
  • Asus ROG MAXIMUS X CODE (LGA1151),
  • Intel Core i7 8700K (Coffee Lake),
  • GeForce RTX 3070 Ti

I had this setup before but got deleted b/c of my stupidity.

So I know this setup would work again.

Installed Oracle VM, then XP OS (64 bit) as guest. I run an older version of AutoCad, it won't run on newer systems.

After all this installed, Enabling Virtualization, booted, BSOD.

What I did:

  • Disable Virtualization, got my machine back. Installed latest graphic driver from Nvidia, make sure everything is good with your new Nvidia driver. (not sure if this had anything to do with the fix). Back in Bios, Disable SECURE BOOT, DO NOT DELETE YOUR KEYS.

  • Reboot, make sure everything is OK.

  • Go back into Bios, enable Virtualization.

  • Hyper-V is disabled.

  • Reboot and this worked for me.

Why did this work? I have no clue. Maybe someone else can chime in and explain.

Improve this answer
1
  • 1
    As it’s currently written, your answer is unclear. Please edit to add additional details that will help others understand how this addresses the question asked. You can find more information on how to write good answers in the help center.
    – Community Bot
    Commented Mar 22 at 16:58
0

There seems to be many problems with Hyper-V, and although I did not have Hyper-V installed (you can check this by typing Hyper-V in the Win 10 search bar, selecting "Turn Windows Features On or Off", then scrolling down to Hyper-V) it seems that a hypervisor was still running on bootup.

Anthony J. Celaya's answer from poweronplatforms.com finally allowed me to enable virtualization via the BIOS and start up Win 10 v1709 build 16299.334:

  1. Start a command prompt with administrator privileges
  2. Run bcdedit and check the status of hypervisorlaunchtype
  3. If hypervisorlaunchtype is set to auto, run bcdedit /set hypervisorlaunchtype off
  4. Reboot and enable virtualization in BIOS
Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .