a fault has occurred causing the virtual cpu?
238459
A fault has occurred causing a virtual CPU to enter the shutdown state. If this fault had occurred outside of a virtual machine, it would have caused the physical machine to restart. ... This issue occurs if the virtual machine's CPU executed a code that led to a triple fault.
656078
"FW status recovery error" - this means somehow Intel ME firmware got corrupted. There is no easy way to fix this, BIOS reflash will not fix it.
1185193
Error code 1 usually occurs when a JVM of the wrong architecture is being used, i.e. 32-bit instead of 64-bit or vice-versa, and it should be easy enough to fix: 1) start up a Command Prompt (make sure you select the option “Run As Administrator”)
470066
Unreasonable high CPU usage in Task Manager is one. ... In this post, we will be discussing one of the most commonly seen problems in Task Manager: high CPU usage caused by IAStoreDataSvc (32 bit). IAStorDataSvc is the name of the service translated as Intel Storage Data Service used by the Intel Rapid Storage Technology.
1115354
A fault has occurred causing a virtual CPU to enter the shutdown state. If this fault had occurred outside of a virtual machine, it would have caused the physical machine to restart. ... When this fault occurs, the virtual machine is automatically powered off.
976677
Therefore this error is caused by a group policy that fails to respond or if it stops running. This could be due to bad registry calls or a corrupt registry. Usually, this is caused by system updates and upgrades that might mess with the registry. A bad shutdown or startup process can also cause this issue.
384823
Also as you have mentioned, if not already enabled, turn on Intel VT virtualization in BIOS settings and restart the machine. Control Panel -> Program And Features -> Turn Windows Features on or off. You may need to reboot afterwords. Warning: Vagrant with VirtualBox cannot work with Docker at the same time.
248641
A page fault (sometimes called #PF, PF or hard fault) is a type of exception raised by computer hardware when a running program accesses a memory page that is not currently mapped by the memory management unit (MMU) into the virtual address space of a process.
579157
['Make sure /var/crash has space for vmcores. ... ', 'Add crashkernel=128M to your kernel command line in /boot/grub/grub.conf.', 'Setup /etc/kdump. ... ', 'Make sure the kdump service is set to start on boot and restart the system.', 'Check that there is an initrd in /boot created for kdump. ... ', 'Test your configuration.']
1000943
Transcript: More virtual CPUs are assigned to the virtual machine than the number of physical CPUs on the host system. This is likely to degrade performance of your virtual machine.
981241
['Find the corresponding VT option on the BIOS page. ( ... ', 'Click <Advanced>-> <Processor> (CPU)-> Virtual or Virtualization, for some computers, VT are included in Configuration or Security.', 'Set the VT option to Enabled.', 'Press Save (usually F10) to save and exit (Save & Exit).']
29102
You might try reducing your base memory under settings to around 3175MB and reduce your cores to 1. That should work given that your BIOS is set for virtualization. Use the f12 key, security, virtualization to make sure that it is enabled. If it doesn't say VT-x that is ok, it should say VT-d or the like.
1106939
Check virtualization settings and clear the virtual cache, if your Internet security software includes this feature, or visit the software provider's support site for more help. Firefox may fail to start for some Windows users after updating, if AVG or AVAST antivirus is installed.
1026966
The CPU needs to be stress tested in order to ensure its stability. It is stress tested using extreme workload, memory usage, clock speed, voltages, and different types of tasks.
28104
VT-x is not available (VERR_VMX_NO_VMX). Now my searches have told me that this is most commonly due to either virtualization not being enabled in BIOS, or Hyper-V running and not allowing VirtualBox access to VMX. I have checked my machine's BIOS and confirmed that virtualization is enabled.
1362833
['Enable the Virtualization option in the local machine BIOS and restart the computer.', 'If the BIOS does not have a Virtualization option or it is already enabled, please see this virtualbox forum post for additional workarounds.']
285152
In that case, it's usually a VMware Workstation problem where LCK files are not letting you take ownership of the VM. You can just delete the LCK files associated with the virtual machine in question. Once a file is unlocked, it can be edited or moved like any other file.