Windows 10: Enabling Hyper-V causes IRQL_NOT_LESS_OR_EQUAL

The very latest version of Windows 10 Pro and all updates as of 17th Oct 2018.


Winver 1803 (OS Build 17134.345)

Problem:

Installing Hyper-V causes a BSOD at any random time. It doesn't need to be configured it doesn't need to have any VM running. Just installing Hyper-V makes my DELL XPS 15 9550 laptop unstable. It might be fine for several hours but this system is going down and you never know when.

What I have tried:
All Windows updates completed
Checked that all drivers are the very latest from DELL

Updated to latest system BIOS.


The only solution I have found:

Uninstall Hyper-V. (This is a permanent fix and the system is rock steady after this)


It's not a very good solution as I bought Win 10 Pro so I could run a VM in the background. I have VM's running perfectly on other systems on my network so I can only assume it's a fundamental hardware/driver incompatibility. My instinct tells me it's an issue with the Killer Wireless-n/a/ac 1535 Wireless Network Adaptor which is crap at the best of times. I've tried disabling this device through Windows but this does not fix the problem.

My next step is to physically remove the wi-fi card (ideally replace with an Intel 9260 NGW M.2 2230 or earlier for function and stability) failing that I'm honestly running out of ideas. I've installed WinDbg but haven't worked out yet how to turn the Minidump file into something readable.

Am I on the right track? Does anyone have any other ideas/suggestions?

:)

 

How to enable Hyper V windows 10

fwiw;

Operating System Requirements

The Hyper-V
role can be enabled on these versions of Windows 10:

• Windows 10 Enterprise
• Windows 10 Professional
• Windows 10 Education

The Hyper-V role cannot be installed on:

• Windows 10 Home
• Windows 10 Mobile
• Windows 10 Mobile Enterprise

 

Win10Pro, Hyper-V and missing files

I am aware that does not install Hyper-V, it was from me attempting to clear up the issue that was preventing me installing Hyper-V. The dism log when issuing the commands;

• DISM /Online /Enable-Feature /All /FeatureName:Microsoft-Hyper-V
  
• DISM /Online /Enable-Feature /All /FeatureName:Microsoft-Hyper-V-All

Show the exact same errors, so I was guessing were rooted in the same cause.

 

Enabling Hyper-V after it has been disabled?

Hi, I was doing Android development on my Surface Pro 3. Use of the android emulators required hyper-v being turned off, so I turned it off. Now, I'm working on a UWP app, and use of the emulators requires hyper-v. I have enabled hyper-v in the "Turn Windows
features on/off" tool, so it's enabled there, but it doesn't seem to be enabled elsewhere, possibly the BIOS. Problem is, there is no option in the SP3 BIOS to enable hyper-v. Windows tells me in two places (task manager, turn Win features on/off) that hyper-v
is enabled. However, running the following script in powershell:

tells me that it is disabled. Visual Studio also tells me it is disabled.

Any suggestions on how to fix?