When disabling hyper-v winhvr.sys causes a SYSTEM_THREAD_EXCEPTION_NOT_HANDLED


I am in kind of a bind where I need to run Virtualbox (v6.0.0) for one of my classes and I also need docker for my work. I downloaded Virtualbox first and everything was going great then I downloaded Docker a few days later without thinking. Obviously, after
docker was installed Virtualbox stopped working.

Virtualbox error: 


VT-x is not available (VERR_VMX_NO_VMX).

After some digging around I realized hyper-v was the issue so, I decided to just disable hyper-v so that I can work in Virtualbox then switch it back when I need docker. Easy enough. I go through the UI to disable hyper-v and restart my computer then I get
the BSOD.


After downloading "WhoCrashed" and checking out the error I come to find that it’s a driver issue, not surprising. However, what was surprising is that it’s a hyper-v driver causing the error. I was trying to disable hyper-v why would one of their
drivers give me an error?

Any help would be appreciated! I’m running a X1 Carbon Lenovo 6th Gen. 

Read full post . . . .

Go Que Newsroom Categories

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 36 bytes) in /home/content/36/8658336/html/goquecom/wp-includes/taxonomy.php on line 3613