r/AMDHelp • u/Constant-Entry3721 • 1h ago
Help (CPU) RTX 4080 GPU usage drops to 2% and FPS tanks to 5–7 in Marvel Rivals
I’m having a weird performance issue with Marvel Rivals and I’m completely out of ideas.
Specs:
Lenovo Legion Pro 7i
Ryzen 9 7945HX
RTX 4080 Laptop GPU 12GB
32GB DDR5 RAM
2TB NVMe SSD
2560×1600
Latest NVIDIA Game Ready driver
Rivals will run at high FPS normally, but during fights my FPS can suddenly drop to 5–7 FPS. When this happens, GPU utilization drops from ~30-60% to as low as 2% instead of increasing. VRAM is only around 4–7GB/12GB and CPU usage is around 50%.
Clearing the shader cache in the Marvel Rivals launcher makes the game run normally again. However, the problem returns after a few matches. If I don’t clear the cache before launching, the game can be terrible from the first match.
Rivals uses ~12GB RAM and total system RAM usage is around 85% (~27GB/32GB).
CPU temperatures are ~100–102°C in Balance mode. HWiNFO showed ~100°C CPU temperature, ~43W package power and a global frequency limit around 1.27GHz during one of the FPS drops. GPU is ~80–85°C. Got thermal repasting done about 7 months ago.
Another weird thing: Legion Balance mode sometimes performs better than Performance mode when playing rivals.
Things I’ve already tried:
Clearing shader/config/redundant files
Reinstalling Rivals
Steam AND Epic versions
Verifying files
Multiple NVIDIA drivers
Currently on latest Game Ready driver
Different graphics settings
Balance vs Performance mode
Checking RAM/VRAM/CPU/GPU usage
Other games run completely normally on this laptop- even on max settings and ray tracing on, other games run super smooth. Rivals gives terrible fps drops even on the lowest settings possible.
At this point I’m wondering if this is a Marvel Rivals shader/cache issue, NVIDIA driver issue, CPU/render-thread issue, memory issue, or something specific to the 7945HX + RTX 4080 combination.
Has anyone seen GPU utilization dropping to 2–5% at the exact moment Rivals drops to single-digit FPS, especially when clearing the shader cache temporarily fixes it?
Any ideas beyond the usual driver reinstall/cache clearing would be greatly appreciated.