I do not see any zdump created for this crash and as this a windows Vm do you configured minidump inside the guest OS.
The VM is reporting that the VMware tools services has been restarted inside the guest and this has been done by the OS itself.
2019-03-18T11:08:42.351Z| vmx| I120: Vix: [13789130 mainDispatch.c:4210]: VMAutomationReportPowerStateChange: Reporting power state change (opcode=2, err=0).
2019-03-18T12:17:03.880Z| vmx| I120: Vix: [13789130 mainDispatch.c:4210]: VMAutomationReportPowerStateChange: Reporting power state change (opcode=2, err=0).
Please upload the vmware.log of the other VM as well to see any correlation.
The vmware.log of a non-impact VM will not help as we need to verify this from the guest OS side as well.
so do you need minidump from Guest OS
when i download tool for minidump log
i found the error in ntoskrnl.exe
so how can i fix this
Check any corrupt files inside the guest by running a windows repair or chkdsk
actually i replaced all OS from win 2012r2 to win 2016
and the problem still happens , this problem happens only with Active Directory VMs and all other OS version like Linux all kernels is working normally