virtualbox.org

Hi,

I realise this has been covered in previous posts but all suggestions do not work, including running "%programfiles%\oracle\virtualbox\vboxmanage.exe" setextradata "Image Name" VBoxInternal/CPUM/CMPXCHG16B 1 or manually inputting into the associated vbox file. When booting from Windows 2012 R2 ISO or other already established Windows 2012 R2 VHD's in the latest VirtualBox version VirtualBox-4.3.18-96516-Win.exe or any other version, I have tried many it comes up with the following or similar:

Your PC needs to restart.
Please hold down the power button.
Error Code: 0x000000C4

followed by various parameters than seem to change on each restart.

VirtualBox is installed on Windows 2008 R2 64bit on an IBM x3650 server, with virtualisation enabled in the BIOS. I have attached the vbox log file and would appreciate any help! Thanks

Does your computer support Hardware acceleration?
Also make sure you have No-Excecute Memory Protection enabled in BIOS

EDIT: Can you attempt to install Windows 2012 on your physical PC, I am not asking you to install,
But,

1.Open your disc drive
2.Turn your computer off Holding the disk drive open,
3.Put the windows 2012 disk in
4. Power on your PC and close the disk tray,
5.If it shows that same error whilst booting from the disk on your PC, your PC cannot support it
6.If it gets to the bit where it shows setup, remove the disk from the drive and reboot normally into your current OS
7. This happens with my PC as well (Acer aspire 7739G) I have windows 8 and 7 dual booting, but cannot install windows 8 or above in vm.

VBox.log wrote: 00:00:37.886708 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:00:37.886712 !!
00:00:37.886712 !! Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)
00:00:37.886758 !!
00:00:37.886801 !! Skipping ring-0 registers and stack, rcErr=VINF_EM_TRIPLE_FAULT
00:00:37.886808 !!
00:00:37.886809 !! {mappings, <NULL>}
00:00:37.886810 !!

You are getting a triple fault exception. Unfortunately this is hard to diagnose since it means that the exception handler itself caused an exception. When I've seen this before it was when someone was trying to install a 64bit OS using the wrong guest OS profile. You have the correct profile, but I'm concerned that you've been messing (unnecessarily) with extradata settings you don't understand (*).

(*) There was a short period of time after Windows 8.1 came out and VBox didn't have a specific template for it; it needed a tweak to manually modify the Win8 profile after the VM was created. That issue was fixed long ago, and I'm not sure it applied to Win2012 anyway. Applying irrelevant and obsolete tweaks without understanding their purpose... probably isn't the way to go.

Thanks so much! "No-Execute Memory Protection enabled in BIOS" has made the difference and switching this on allowed Windows 2012 to install.