Solve vmwarevm crash: VMware Player unrecoverable error: (vmx)

--- When all the methods you have found online to delete. vmss or. lck are invalid, do not reinstall them. Here we will discuss how to solve the problem for you. Solve vmwarevirtual machine VMware Player unrecoverable error: (vmx) Problem 1. Problem description: After the Virtual Machine (computer running system win7 64-bit flagship Edition sp1, virtual machine running federo8, if the software is installed on a non-virtual machine, the system prompts you to restart the computer. If you want to start the system in the virtual machine again, the system prompts:

VMware Player unrecoverable error: (vmx)

ASSERT d:/build/ob/bora-591240/bora/vmcore/vmx/main/timeTracker_user.c: 237 bugNr = 148722

A log file is available in "E: \ Virtual Machines \ Windows 7x64 base Pim \ vmware. log ". A core file is available in "E: \ Virtual Machines \ Windows 7x64 base Pim \ vmware-vmx-7608.dmp ". you can request support and include the contents of the log file and the core file.

To collect data to submit to VMware support, run "vm-support ".

We will respond on the basis of your support entitlement.

Or Chinese (there are many such problems on the Internet, but most of the solutions are the same ):

VMware Workstation Failure Recovery error: (vmx) ASSERT d:/build/ob/bora-471780/bora/vmcore/vmx/main/timeTracker_user.c: 237 bugNr = 148722 the log file is located at D: \ 00 \ vmware. log. The core file is located in D: \ 00 \ vmware-vmx-3308.dmp. The request supports logs and core files. send collected data to VMware support and select "collect supported data" from the Help menu ". you can also run the "vm-support" script directly in the Workstation folder. we will reply to your basic support power.

For example:

Click OK:

Ii. solution:

For more information, see the vmware official forum: https://communities.vmware.com/message/2018580.

In fact, this is an interesting problem because the CPU frequency of the system is chaotic. You can modify the Registry to solve the problem:

1. Open Registry Editor: Open the window key + R and enter regedit;

2. Find

HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ services \ vmx86 \ Parameters

3. Set

Host. maxkHzEstimate. cpuidHash

Host. maxkHzEstimate. value

Delete or rename two keys.

4. Restart vmware

5. OK

The following is an official answer:

Well, this is an interesting problem indeed. Somehow our estimate of your system's CPU speed got seriously messed up. I think we can fix it though... Try this:

 

1) Shut down your VM (s) and quit VMware Workstation.

 

2) Start Registry Editor (regedt32.exe), and navigate to the key named

 

HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ services \ vmx86 \ Parameters

 

That registry key shoshould contain at least the following two values of type REG_DWORD:

 

Host. maxkHzEstimate. cpuidHash

Host. maxkHzEstimate. value

 

Delete (only) those two abovenamed keys-or, if you want to be particle ly cautious, just rename them to something else so you can put them back if things don't work out.

 

3) Launch VMware Workstation and power on your VM.

 

At this point, those two registry keys shoshould be automatically recreated, and hopefully your VMs will all behave themselves again. until we figure out what caused the bad estimate in the first place, it's possible that the problem might recur.

Reference: https://communities.vmware.com/message/2018580

Reprinted Please note: http://blog.csdn.net/guo8113/article/details/21820971

Zookeeper