Tomb Raider keeps crashing due to virtual memory overflows and weird space scheduling on my S910PRO 2TB.

The game would just crash without warning whenever I loaded into the deeper ruins, which was honestly driving me crazy. Even though the Fanxiang S910PRO 2TB has insane bandwidth, the way the independent cache and system page file interacted caused a massive conflict when usage hit 16.5-18.2GB. I first tried setting the virtual memory to half of the remaining disk space, but that actually made the read/write conflicts worse in high-action scenes, and the stuttering got even more frequent. I eventually switched from automatic management to a custom size, locking it between 16384-32768MB and moving the page file to a non-system partition. In Task Manager, I saw disk active time plummet from 85% to a steady 25-35%, and the crashes stopped completely. I did notice a brief hang during boot-up after locking the size, but disabling the indexing service smoothed it right out. SSD temps stayed between 55-62℃ with a load of 12-20%. Event Viewer confirmed the 0x0000005 memory errors are gone, and the input response feels way more immediate.