Hi,
I have a similar problem as "Out of Memory" errors after Windows 10 Creators Update .
I am running VMWare 12.5.5.5234757 on Win10 Build 16179 (Quadcore 3,3 GHz 16 GB Ram).
Since Build 16176 all guests (Win10, Server2003) crash after ~30-60 min without any error window. It makes no difference if I am working on the guest or not.
In the vmware.log I see the following lines:
2017-04-23T11:49:07.006+02:00| vcpu-1| E105: PANIC: Semaphore 984 wait failed: 257
2017-04-23T11:49:07.006+02:00| vcpu-1| I125: Panic: can't get userlevel lock.
2017-04-23T11:49:07.006+02:00| vcpu-1| W115: Win32 object usage: GDI 10, USER 19
2017-04-23T11:49:07.006+02:00| vcpu-1| I125: CoreDump_CoreDump: faking exception to get context
2017-04-23T11:49:07.011+02:00| vcpu-1| I125: CoreDump: Minidump file D:\Virtual Machines.VMWare\VM-Win10_x86_DE\vmware-vmx.dmp exists. Rotating ...
2017-04-23T11:49:07.032+02:00| vcpu-1| W115: CoreDump: Writing minidump to D:\Virtual Machines.VMWare\VM-Win10_x86_DE\vmware-vmx.dmp
Before the build 16176 I never had this problem.
I attached the logfile and vmcore-dump.
Virtual printing is disabled.
Edit: Link to logfiles Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.
Thanks for posting issue here.
I haven't seen any attached logs. Could you upload them again ?
Hi,
attaching does does not work, I tried it several times.
Link Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.
Thank you.
For what it's worth, I'm having the same exact issue running build 16179.1000. Strangely enough the issue doesn't happen with my Linux guests as far as I can tell. Only my Windows 7 Professional (64-bit) guest has the issue.
I have attached the two latest minidumps and the vmsupport file if it helps.
Any reaction?
Similar issue. win 10 creators update, insider fast build.
if this helps - i have 2 monitors and computer was locked overnight. crash in vmware coincides with 2nd monitor driver failure and monitor turned off.
2017-06-17T11:34:42.745-05:00| vcpu-0| E105: PANIC: Semaphore 864 wait failed: 257
2017-06-17T11:34:42.745-05:00| vcpu-0| W115: Win32 object usage: GDI 10, USER 29
2017-06-17T11:34:42.745-05:00| vcpu-0| I125: CoreDump_CoreDump: faking exception to get context
2017-06-17T11:34:42.746-05:00| vcpu-0| W115: CoreDump: Writing minidump to C:\Users\chris\Documents\Virtual Machines\June 16 2017\vmware-vmx.dmp
2017-06-17T11:34:42.878-05:00| vcpu-0| I125: CoreDump: including module base 0x0x7ff775cc0000 size 0x0x01685000
2017-06-17T11:34:42.878-05:00| vcpu-0| I125: checksum 0x0140a7b1 timestamp 0x57103101
2017-06-17T11:34:42.878-05:00| vcpu-0| I125: image file C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe
2017-06-17T11:34:42.878-05:00| vcpu-0| I125: file version 12.1.1.6932
VMware Workstation Pro and Player 12.5.6 have been released, and contain a workaround for the "Semaphore nnnn wait failed: 257" compatibility issue affecting Workstation running on Windows 10 Creators Update.
VMware Workstation 12 Pro Version 12.5.6 Release Notes
Download VMware Workstation Pro
VMware Workstation 12 Player Version 12.5.6 Release Notes
Download VMware Workstation Player
Please let us know if you continue to encounter "Semaphore nnnn wait failed: 257" errors after applying the update.
Cheers,
--
Darius