GamePP Frequently Asked Questions - Professional Hardware Monitoring Software FAQ Knowledge Base

The memory management in this game is a total disaster. After about two hours, the RAM usage rockets past 15GB and the game just vanishes without a word. My 16GB of Corsair Vengeance DDR4 3200 just couldn't handle the massive memory leak, and the system would force-close the app once physical RAM was maxed. I tried limiting memory usage via launch options, but that just caused textures to disappear—a pathetic 'fix' that I immediately regretted. I went into Advanced System Settings and manually expanded the virtual memory to a fixed 32GB and killed every high-usage background process in Task Manager. The 0x0000005 memory access violation errors in Event Viewer completely stopped, and I can now play for six hours straight without a crash. I actually put the page file on my HDD first, and the loading times were abysmal until I moved it to the SSD. RAM temps are 46-52℃ and VRMs are 60-65℃. Frame times are now stable at 14-19ms, but the game's leak is still a mess. Last updated onApril 8, 2026 7:18 PM.

Stalking through dense forests was a nightmare, with FPS jumping between 60 and 30—I honestly wanted to throw my keyboard. The quad-channel setup on this Jginyue X99 board has great bandwidth but terrible signal interference, causing latency to swing wildly between 90-110ns. I tried adding 32GB of virtual memory, but that was a total waste of time as the latency didn't budge. I went into the BIOS, crushed the timings from 16-22-22-42 to 14-18-18-38, and bumped the VTT voltage from 1.1V to 1.2V to stabilize the signal. AIDA64 showed latency drop from 102ns to 72-78ns, and the random drops mostly vanished. My first attempt at aggressive timings caused a hard freeze, and I only got it stable after relaxing tRFC to 600. RAM stays at 45-52℃ and VRMs at 60-68℃. I backed up the BIOS profile so I don't have to do this again, and the input response is finally snappy. Last updated onMarch 24, 2026 11:12 AM.

Every time a big patch hits, my write speed plunges from 7000MB/s to 800MB/s, which is just pathetic. The Zhitai TiPro9000's SLC cache fills up, and then the TLC performance reveals its true, slow self, leaving me stuck at 99% loading for ages. I tried formatting and repartitioning the drive, which was a total waste of an hour and a huge pain to back up data—I was honestly fuming. I eventually went into Device Manager, set the disk power plan to 'High Performance', and used the manufacturer tool to kill redundant background scans. CrystalDiskMark showed the sequential write swing improved from 800-7000MB/s to a more stable 2500-6800MB/s, cutting load times by 35%. The power plan made the SSD run 4℃ hotter, so I had to tweak my fan curves to keep it at 48℃. It now runs at 45-58℃ with 0.04ms latency. I exported the config via a system image tool just in case. Last updated onApril 1, 2026 8:59 PM.

Walking through the center of Heidel was a gamble; the game would just crash to desktop without any warning. 8GB of Kingston FURY DDR3 is just not enough for the Remastered high-res textures, with physical RAM pinned at 7.2-7.8GB. I tried using a 'low memory' launch parameter, but that just gave me hideous texture pop-in—a complete joke of a solution. I eventually went into Advanced System Settings and manually set the page file to a fixed range of 16384-32768MB and killed every single background app. In Task Manager, my committed memory peak jumped from 12GB to 24GB, and the crashes stopped entirely. I made the mistake of putting the page file on an HDD at first, and the loading was painfully slow, but moving it to the SSD fixed everything. RAM temps are 48-55℃ at 1.5V. Event Viewer shows the memory overflow errors are gone, and the game finally feels responsive. Last updated onApril 11, 2026 10:53 AM.

Riding through towns in Norway was a nightmare, with frames jumping wildly between 60 and 35. The optimization is just bad. While this MSI board has decent compatibility, the default JEDEC timings are way too conservative, leaving me with a latency of 85-92ns that choked the CPU's instruction scheduling. I tried adding 16GB of virtual memory first, but while usage dropped, the latency stayed exactly the same—a totally useless effort. I eventually dove into the BIOS and tightened the primary timings from 18-22-22-42 down to 16-18-18-38 and bumped the memory voltage from 1.2V to 1.35V. AIDA64 confirmed latency dropped from 88ns to a much better 64-68ns, and the city stutters are mostly gone. I did blue-screen trying 16-16-16 at first, but loosening tRFC to 560 stabilized everything. RAM temps are now 42-48℃ and VRMs are at 52-58℃. I've backed up the BIOS profile to keep these settings. Last updated onMarch 31, 2026 6:38 PM.

Back to Top