GP Exception 13 in world 187416:vmm3:XXXXXXXX @ 0x418021d8adc7
xxxx-xx-xxTxx:xx:xx.xxxZ cpu16:187416)Backtrace for current CPU #16, worldID=187416, fp=0x0
xxxx-xx-xxTxx:xx:xx.xxxZ cpu16:187416)0x4393e0c1bf20:[0x418021d8adc7]VmAnon_AllocVmmPages@vmkernel#nover+0x3b stack: 0x100008785, 0x192d6c43b, 0x4393e84a7000, 0x6, 0x4393e84a7100
xxxx-xx-xxTxx:xx:xx.xxxZ cpu16:187416)0x4393e0c1bf80:[0x418021d18ad7]VMMVMKCall_Call@vmkernel#nover+0x157 stack: 0x4393e0c1bfec, 0x4024600000000, 0x418021d4a64b, 0xfffffffffc606d00, 0x0
xxxx-xx-xxTxx:xx:xx.xxxZ cpu16:187416)0x4393e0c1bfe0:[0x418021d4a6d2]VMKVMM_ArchEnterVMKernel@vmkernel#nover+0xe stack: 0x0, 0xfffffffffc4074b3, 0x0, 0x0, 0x0
xxxx-xx-xxTxx:xx:xx.xxxZ cpu16:187416)Panic: 623: Halting PCPU 16.
xxxx-xx-xxTxx:xx:xx.xxxZ cpu20:187418)Panic: 514: Panic from another CPU (cpu 20, world 187418): ip=0x418021d4a2e2 randomOff=0x21c00000:

 

If you are getting same entry in core dump then follow this solution

 

This issue is resolved in ESX 6.5.0a

 

Work around

 

To work around this issue for virtual machines migrated to an ESXi 6.5 host from previous version, recover the virtual machine from the ESXi 6.5 host and set Numa.FollowCoresPerSocket to 1 on all ESXi 6.5 hosts.

 

For further information refer this KB.

 

ESXi 6.5 host fails with PSOD: GP Exception 13 in multiple VMM world at VmAnon_AllocVmmPages (2147958) | VMware KB