Welcome to the Community - since you vmotioned and did not move the VMDK I would say not it is not a problem with the virtual disk. It is sounding like an issue with original ESXi host - to confirm do the problems return when you vmotion back to the original host?
If they do I would look make sure the CMOS settings for the CPU are the same on the both hosts.