Clever Geek Handbook

BSoD on vagrant up (KMODE_EXCEPTION_NOT_HANDLED) - Windows 8

I have a problem with Vagrant

trying to initialize a field virtualbox

with laravel/homestead

.

I have installed the latest version Vagrant (1.7.4)

in Windows 8. I have installed Oracle VirtualBox 5.5.0.

Then I did this in Windows Command Prompt:

vagrant add box laravel/homestead

to add laravel homestead box

vagrant init laravel/homestead

and

vagrant up

After vagrant up

sometime in the process, the system crashes with BSoD (KMODE_EXCEPTION_NOT_HANDLED)

Any ideas on what I might have done wrong, or has anyone experienced this problem?

Thank!

+3


source to share


2 answers


Make sure the Windows Hyper-V resource is active. If you've installed Docker before testing this, coz Docker needs Hyper-V.

In my case this works for me



Find "Windows resource" in the Windows Start menu and click "Turn Windows resources on or off", find "Hyper-V", uncheck the boxes and check the boxes. Restart your computer after that.

Tee

+3


source


I had almost the same problem (BSOD gave SYSTEM_SERVICE_EXCEPTION error). Yesterday I installed Docker on Windows 10 and today I tried to "roam" (using VirtualBox Provisioner) and got a BSOD. Hyper-V is conflicting and I disabled it from "Windows Features" and the issue was resolved.



0


source






More articles:


All Articles