I think you should read his post again..
Perhaps he needs a little more clue.
YOUR HYPERVISOR IS SHUTTING OFF YOUR VM.
Your options are:
1) Do as you suggest and toss out your pricey server (your suggestion, incidentally, not mine, don't put words in my mouth, I get mean about it).
2) Randomly thrash around trying random remediations.
3) Follow my suggestion and simplify the scenario by ditching the hypervisor.
See, FreeNAS can be installed on a USB thumb drive, and if you follow the design principles in the guide I linked to, you can boot a bare metal version of FreeNAS very easily, basically for the cost of a thumb drive.
Now this probably won't FIX your NAS but it will probably help to highlight what the underlying problem is. Perhaps your HBA is baked, if you didn't provide sufficient airflow over the heatsink. Perhaps the heatsink became detached. Perhaps the heatsink grease needs to be replaced. Given the error I'm really thinking your HBA is baked, but it could be other things. Putting FreeNAS on the bare metal gives FreeBSD a better chance of continuing to run and bringing out a more familiar set of failure symptoms. It doesn't mean that you can't pull the USB key out once it's fixed and go back to a virtualized setup, once the underlying problem is fixed. I actually wrote that sticky EXACTLY FOR YOUR PROBLEM CASE. Once you are running on bare metal, you are much more likely to get useful responses from the userbase here in the forums.
See, you walked in here and the person who wrote all the stickies about virtualization (that'd be me!) gave you a suggestion, because I developed the remediation strategy for your situation well more than half a decade ago. I do this stuff professionally. I gave you some really good advice. There's no need to get snarky and eyeroll'y. You either follow the guidance and it will probably be much easier to resolve the underlying issue, or you can randomly try random things hoping to strike upon the problem by dumb luck. And the guidance is really simple: go back to bare metal and do the problem solving there.
My strong feeling is that there's a problem with the HBA. A lesser possibility is that something has changed in the environment, BIOS update, ESXi update, FreeNAS update, firmware update, added or removed vCPU's, etc.