VM crashed PC on boot

[brittains]

Hey there, I am having an unusual issue. 
Any time I start a virtual machine I get a blue screen windows crash. System_service_Exception is the error it reports.
The crash happens the moment I select the disk image to boot from. Tried ubuntu, debian, and winows - they all yield the same result. 

System specs:
Windows 10 enterprise.
mobo: h270i gaming pro a/c
gskill: 2400 ddr4 2x8gb
cpu: g2650
g.card: rx580
C: bpx m.2 ssd
D: 2x seagate 3tb in hardware raid1

Will gladly report other specs or more detailed if relevant.

I tried using hyperV first to create a VM on the raid array since it has tons of space. 
blue screen when launched.
At first I thought it was just a hyperV thing (I've never used it before) so I downloaded oracle virtual box.
I had the same results with VirtualBox so I thought maybe there is some compatibility with running a VM on a raid array. 
Tried again: built the VM on the C drive. Same crash.
Tried uninstalling entirely and putting all info on the C drive. Same crash.
Checked bios to confirm cpu has virtualization enabled. It is. 

Built the system yesterday so it's essentially a fresh install. 

Any sort of insight would be awesome. 
Thank you. 

 

Edited May 6, 2017 by brittains
quoted wrong error code

[Electronics Wizardy]

You probably have bad vt-x on the cpu or the board. Assuming your running the newest bios and microcode updats, the only option really is to rma it.

[paddy-stone]

Have you actually enabled virtualization in the BIOS?

[brittains]

31 minutes ago, paddy-stone said:

Have you actually enabled virtualization in the BIOS?

Intel virtualization is enabled. Is there something else I am looking for?

[paddy-stone]

Just now, brittains said:

Intel virtualization is enabled. Is there something else I am looking for?

Nope, that's it... just wondered whether you had enabled it. I actually forgot with my newest system an Ryzen CPU, and was playing about in ubuntu and setting stuff up and went to import some VMs and make some new ones and obviously had problems    I was not happy, lol.

I have only used windows as the host a few times when using virtualization, I didn't like it TBH, I much prefer using vmware in ubuntu or flavours thereof... but I can't imagine there'd be a problem with VMwarte, tons of people use it.

When/if it happens again, can you take a screengrab or picture.. as I said I'm not that up on it at all, but someone else might get a clue from that maybe. It usually tells you which service it has a problem with.

[brittains]

2 hours ago, Electronics Wizardy said:

You probably have bad vt-x on the cpu or the board. Assuming your running the newest bios and microcode updats, the only option really is to rma it.

Updated the bios to the most current version. 
I will look up what microcode is as I am unfamiliar.

 

Still receiving the same crash. 

https://www.dropbox.com/s/e0h64wpwhp1aoi3/DSC_0257.JPG?dl=0 
Picture of the blue screen - not that it really helps.

 

[Electronics Wizardy]

4 minutes ago, brittains said:

Updated the bios to the most current version. 
I will look up what microcode is as I am unfamiliar.

 

Still receiving the same crash. 

https://www.dropbox.com/s/e0h64wpwhp1aoi3/DSC_0257.JPG?dl=0 
Picture of the blue screen - not that it really helps.

 

microcode is updated with windows, so don't worry abou tthat.

 

Its probably the cpu, so id call intel up about that.