@SavageCDN The virtual memory number you are seeing is what A3 detects - I'm guessing JetFox limits the memory available to 2GB no matter what you set in your server.cfg. This is not uncommon with regards to game hosts (as they will have multiple instances on one server) and will not be the cause of the issue.

Is it the same symptoms with the new server? Non-alive missions run fine but anything that loads @alive hangs on startup?

No. Different symptoms. Game will run fine for 30 min to 1.5 hours most of the time. Then the same thing will occur. No message received followed by desync/crash. Hugely frustrating as this has been a constant issue for...6 months now?