I've to say that I've never had  Poser crashed at render time, since at least Poser 11 (even before that was with another PC). During summer, I've replaced my 2080Ti with a 4070OC that needs at most 20W less than the 2080TI, so that I've no problems with the power supply.
And I'm using nvidia's Studio version since so long that I can't remember when I switched off from the Games Ready version, but clearly at the time that meant more stability from my personal point of view.

The only times Poser crashes are because of Python:
- taking its time to load a pose that references bitmaps too
- taking its time to do... mysterious things allover the scene when I'm just replacing a bitmap of a character (hint: the same operation on an empty scene is really faster)

My conclusion is the same with any not-compiled langages including Java (no: Python isn't really compiled, it's pre-compiled and needs somewhere a kind of interpreter): at one moment, the resources are so off that you have two options: wait for a crash or save, quit, launch and reload the program.

Now I know that when I need to work on a resource-heavy scene: I work on different elements separately. Once all is included in the final scene: save.

I still trust the Studio version for the moment.

𝒫𝒽𝓎𝓁

---

(っ◔◡◔)っ

👿 Win11 on i9-13900K@5GHz, 64GB, RoG Strix B760F Gamng, Asus Tuf Gaming RTX 4070 OC Edition, 1 TB SSD, 6+4+8TB HD
👿 Mac Mini M2, Sonoma 14.6.1, 16GB, 500GB SSD
👿 Nas 10TB
👿 Poser 13 and soon 14 ❤️