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

Every time I step into a dense forest, my FPS plummets from 50 to 12. It's an absolute cliff-dive and honestly pathetic. The 8GB on the Zotac RTX 2060 Super is just not enough for modern 4K textures, forcing the system to use slow system RAM as virtual VRAM, causing massive 150-300ms spikes. I tried setting everything to Low, but the game looked like something from 20 years ago, which just made me angry. I went into the NVIDIA Control Panel, manually set the Shader Cache Size to 10GB, and optimized the Windows page file size. In random R/W tests, the stuttering from VRAM swapping dropped by 60%, and load times were 25% faster. The first time I tweaked the cache, the game took 10 seconds longer to boot, but moving the cache path to an NVMe SSD fixed that. GPU temps sit at 72-80°C with fans at 1800 RPM. Backed up all driver configs via system snapshot. Last updated onApril 1, 2026 5:46 PM.

This drive is barely hanging on with modern 4K textures; entering a new area felt like watching a puzzle piece itself together, which was honestly pathetic. The Intel 760P's sequential reads peak around 2000MB/s, causing severe I/O bottlenecks with the remake's massive asset streams. I tried capping the graphics settings, but the game looked like a blurry mess from the 90s—a useless fix that left me speechless. I used a partition tool to verify 4K alignment and ran a system-level storage optimization. CrystalDiskMark showed random reads climbing from 35-42MB/s to 48-55MB/s, shaving about 4 seconds off loading screens. After the first cleanup, disk usage spiked to 100% for a while, but disabling the background antivirus scan fixed that. Temps are stable at 35-42℃ with a response time of 0.08ms. I backed up the partition parameters, and the overall system response finally feels snappy. Last updated onApril 11, 2026 5:47 PM.

Riding through the streets of Novigrad was a disaster, with FPS jumping wildly between 70 and 40. The optimization is so bad it makes me want to throw my keyboard. While the Gloway kit is generally compatible, the XMP timings were hitting 88-95ns latency with the Next-Gen high-res textures. I tried adding 16GB of virtual memory, but it was a pointless exercise—usage went down, but latency didn't budge. I went into the BIOS, tightened timings from 36-36-36-76 to 32-34-34-72, and pushed voltage from 1.25V to 1.35V. AIDA64 showed latency drop to 68-72ns, and the city stuttering improved significantly. I hit a wall trying 30-30-30 which caused a hard lock; loosening tRFC to 580 finally stabilized it. RAM temps stay at 48-55℃ and VRMs at 58-63℃. I've backed up the BIOS profile, but this game is still a resource hog. Last updated onApril 9, 2026 4:12 PM.

Every time I entered a large-scale dogfight, my CPU clock would dive from 4.8GHz to 3.2GHz—a total cliff-dive that left me speechless. The default fan curve on the RT620P is way too slow to react to instant load spikes, letting the core temp hit 95℃ in about 3 seconds and triggering a hard thermal wall. I tried enabling 'High Performance' mode in Windows, but that was a rookie mistake—it did nothing for the spikes and just raised my idle temps by 10℃, which honestly pissed me off. I eventually tore the cooler off, swapped to top-tier phase-change thermal paste, and set a stepped fan curve that jumps to 90% speed at 75℃. In AIDA64, the peak temps dropped from 95℃ to a manageable 78-82℃, and the clock fluctuations stopped. I actually didn't tighten the bracket enough on the first try, which made temps climb by 5℃, but a re-mount fixed it. Now the CPU runs between 68-76℃. I've exported my BIOS profile as a backup, though the fans are definitely louder now. Last updated onApril 2, 2026 9:07 PM.

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.

Back to Top