GamePP Frequently Asked Questions

Right in the middle of a sandstorm fight, my FPS would suddenly tank from 80 down to 40, which is an absolute rollercoaster of frustration. It turns out the default profiles for the Asgard Thor DDR5 6400 have some compatibility quirks with certain boards, causing the memory controller to jump wildly between 5600MHz - 6400MHz. I tried lowering the in-game settings, but while the FPS went up, the game looked terrible, and that was a compromise I wasn't willing to make. I went into the BIOS, locked the frequency at a steady 6000MHz, and bumped the voltage from 1.35V to 1.38V for absolute stability. Monitoring with RTSS, the frame times tightened from 18-38ms to a smooth 12-16ms, and the drops disappeared. Interestingly, locking it at 6000MHz actually cost me about 2 FPS at first, until I fine-tuned the secondary timings to get the performance back. Memory temps stayed stable between 52-58℃. I verified the frequency lock in the driver panel, and temps held at 52-58℃. Last updated onApril 25, 2026 4:05 PM.

I can't believe this game is actually maxing out 32GB of RAM; it felt like my PC was trying to breathe through a straw. Loading a large map would push memory usage above 95%, turning the game into a slideshow, which is just ridiculous. I tried closing every single background app, but it only saved about 1GB, which felt like a waste of time. I finally went into the Advanced System Settings and manually set the virtual memory to a fixed block of 32768MB - 49152MB on my NVMe drive. In Resource Monitor, the commit charge dropped from 45GB to a more manageable 32-38GB, and the stuttering frequency plummeted. I did notice a slight delay during system boot after the first change, but I fixed that by disabling a bunch of useless startup items. Memory temps were hovering around 50-56℃, which is barely acceptable. I used a performance analyzer to export the memory curves for archiving, with fans screaming at 1400-1600 RPM. It's playable now, but the memory management in this game is a mess. Last updated onApril 19, 2026 2:58 PM.

It was infuriating seeing crisp building textures suddenly turn into these bizarre, glitchy color blocks, and it only got worse as my base expanded. Digging into the root cause, I found that with the default XMP profile, the memory controller voltage was bouncing between 1.32V - 1.35V, which was causing occasional bit flips during data transfer. My first instinct was to drop the texture quality to Medium, but while the flickering slowed down, the game looked like a blurry mess, which was a total dealbreaker for me. I rebooted into the BIOS and nudged the frequency down from 6000MHz to 5800MHz, while locking the DRAM voltage at a steady 1.38V. After running AIDA64, my memory latency stabilized from 88-96ns down to 82-85ns, and the flickering vanished completely. I actually pushed the voltage to 1.4V at first, but the system triggered an overheat protection shutdown, so I had to back it off to 1.38V to find the sweet spot. Temps settled between 48-54℃. Four passes of MemTest86 confirmed zero errors, with temps holding steady at 48-54℃. Last updated onApril 4, 2026 9:14 AM.

Exploring those fantasy realms was a nightmare because the screen would just freeze for a fraction of a second, making the controls feel completely unresponsive. My Crucial DDR4 2400MHz 8GB was hitting a hard ceiling, with Resource Monitor showing commit charges swinging wildly between 7.2GB - 7.8GB, forcing the system to lean on the sluggish HDD swap file. I tried killing every single background browser tab, but that only clawed back about 300MB, which felt like a joke given the level of stuttering. I eventually dove into Advanced System Settings and locked the virtual memory to a fixed range of 16384MB - 24576MB on my fastest SSD partition. Once I rebooted, the memory pressure curve flattened out, and my frame times tightened from a messy 25-48ms down to a rock steady 16-22ms. Interestingly, setting it to 8GB initially didn't fully kill the stutters in dense areas; I had to double it to 16GB to finally stop the fluctuations. Memory temps stayed around 41-47℃. Checking the performance counters confirmed the page file read/write frequency dropped significantly, keeping the frame time locked at 16-22ms. Last updated onApril 2, 2026 1:59 PM.

Rotating the camera in the village hallways caused these tiny, annoying screen tears. The default 36-36-36-76 timings on the Kingbank Yin Jue DDR5 6000 were causing latency to swing between 75-90ns. I tried adding more virtual memory, but that just added 2ms of input lag—a total fail. I went into the BIOS, manually dropped the tRFC to 480, and locked the voltage at 1.35V. In AIDA64, the read latency tightened from 82ns to a smooth 65-71ns, and the jarring transitions disappeared. I did get a Blue Screen during the first attempt, but loosening tRAS to 80 stabilized everything. RAM temps are 52-58℃ and VRMs are 60-65℃. Five rounds of MemTest86 confirmed zero errors, and the RAM stays around 54-58℃. Still, some high-load scenes might push the heat slightly higher. Last updated onMay 15, 2026 5:54 PM.