Can clearing the memory pool fix Returnal crashes on Kingbank DDR5?
It's honestly ridiculous that a game can swallow 64GB of RAM and still crash to desktop in the late game. My Kingbank 6000 MHz usage climbed steadily from 12GB to a staggering 61.2GB—a textbook memory leak. I tried restarting the game, but the relief only lasted thirty minutes; the cycle of frustration was almost comical. I fired up a memory analyzer and saw a mountain of redundant texture data that wasn't being flushed. I ended up using a script to force-clear the DirectX cache every hour. In Resource Monitor, the usage finally leveled off into a stable valley between 35-45GB instead of a vertical climb. I actually messed up and deleted some pre-compiled shader files during the process, which added two minutes to my next load time—lesson learned. Memory temps hovered at 52-58℃ at 6000 MHz. After exporting the usage logs, the leak is effectively suppressed, and fans are humming steadily at 1400-1600RPM.
