I've been trying to create a virtual machine with different os's and the result is the same, as soon it starts booting from media installation (iso file) it hangs with a message window.
This is my hardware:
A triple fault error happens when the guest code does something nasty and unexpected, such as executing garbage as code. I would check the MD5 sums on that ISO you're booting from.
Otherwise all your settings look pretty good to me. That's also a very well specced PC! Is that a DIY build? I can only find that motherboard listed on its own.
mpack wrote:That's also a very well specced PC! Is that a DIY build? I can only find that motherboard listed on its own.
Yes, is DIY build...work and gaming
It's a shame that after all this I can't get to create a VM with VB, I've tried creating a Windows Server 2008 VM with the same results, checked everything about AMD-V and all are enabled, don't know what else to check. Thanks anyway for the effort.
Last edited by mpack on 24. Apr 2020, 15:55, edited 1 time in total.
Reason:Trim excessive quoting.
I was able to find a fix for my problem described at the beginning of this thread that works, just follow this steps to resolve (it worked for me):
1. In search box type "gpedit" then Goto - Computer Configuration - Administrative Templates - System - Device Guard - Turn on Virtualization Based Security. Now Double click that and "Disable"
2. In search box, type Turn Windows features on or off, now uncheck Hyper-V and restart system.
3. Open Registry Editor by typing regedit in search box, now Go to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\DeviceGuard. Add a new DWORD value named EnableVirtualizationBasedSecurity and set it to 0 to disable it.
Next Go to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\LSA. Add a new DWORD value named LsaCfgFlags and set it to 0 to disable it.
4. Open command prompt as a administrator and type the following commands
bcdedit /create {0cb3b571-2f2e-4343-a879-d86a476d7215} /d "DebugTool" /application osloader
Then copy paste the rest below and press enter
bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} path "\EFI\Microsoft\Boot\SecConfig.efi"
bcdedit /set {bootmgr} bootsequence {0cb3b571-2f2e-4343-a879-d86a476d7215}
bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} loadoptions DISABLE-LSA-ISO,DISABLE-VBS
bcdedit /set hypervisorlaunchtype off
Now, Restart your system
That's it, hope this works for somebody else having my same problem.
All of those fixes are well known fixes for fixing conflicts between VirtualBox and other users of CPU virtualization (VT-x/AMD-v). However, I don't remember anyone else reporting that those conflicts can lead to triple faults. The normal effect is that the VM fails to launch (graceful error and out), or runs very slowly.
As Scott suggests, we'll have to bear this report in mind.
We have had a couple of reports of people who claim to go through the whole 64-bits tutorial and still be unable to get Hyper-V to go away. Your steps 3 and 4 seem possibly somewhat related to the tutorial's post 2 steps 2 and 3, but through the registry. I will keep a link to your post as possible further info. Thanks, RSaint!
