This started occurring after a Windows update. First it was due to the haspnt drive being installed. Uninstalled that and it actually allowed me to log in. Now every time the NIC requests DHCP info, a triple fault occurs. If setting the NIC to NAT, it'll grab it's own DHCP fine and still can get on the net with no fault. Setting the NIC to host only is fine. Setting it to Bridged but setting a static IP before doing so works also with no fault. A work-around would be to just section off the DHCP pool for static addresses for these VMs (more that one have this problem) and give them all statics; however, I would like to avoid a workaround if possible, especially if there's a solution out there.
Which VMware product are you using?
Typically Workstation Pro 12; however, I've tested the image on our ESXi 6.5 server and the guest automatically reboots at the same point without throwing out an error.
Moderator: Moved to Workstation Pro