An early version of the base code for Star Trek Online was burning 100% clock cycles doing nothing, causing gpu and cpu to overload, overheat and crash. Betting they left a process open here that's not actually doing anything, causing this crashing issue. It's funny that a game would need to hard code a cap on utilization... Should be an "easy" fix.I am coming to the same conclusion. The game is running CPUs and possibly GPUs at 100%+ and causing them to crash. I have returned my CPU clock to 3.6GHz from the 3.9GHz I usually run, and the game is suddenly stable.
I wonder if I limit the CPU power state maximum to like 95% or 98% in windows power management if the problem will resolve even with an overclock?
However, with all the software trying to run overlays at the same time, that could be another issue splitting gpu cycles, and the root of my alt-tab crashing issue as it's trying to initialize said multiple overlays when bringing the game back to active.