Research · Updated 2026-10-16

FPS Drops on a Gaming Laptop: How to Fix (2026)

FPS drops ruin games — and the causes range from trivial (unplugged charger) to serious (thermal throttling). This systematic guide walks through every fix in order, from the obvious to the advanced.

The UK FPS troubleshooting guide.

FPS Drops on a Gaming Laptop: How to Fix (2026)

Illustrative stock photo (Pexels / Unsplash)

The obvious checks

The obvious checks (fix 80% of cases): is the charger connected? (unplugged laptops throttle hard — always game plugged in); is the correct adapter used? (a 65W USB-C charger cannot feed a gaming laptop — use the stock brick); is Windows in Best Performance mode? (Settings → Power — Balanced throttles); is the game using the dGPU? (not integrated graphics — verify in Task Manager).

These sound insulting — they fix most FPS complaints. Check them first, every time.

Driver fixes

Driver fixes: update GPU drivers from NVIDIA/AMD directly (Windows Update drivers are outdated — the #1 FPS fix), perform a clean install (tick the option — removes corrupted profiles), use DDU if problems persist (Safe Mode wipe for stubborn driver corruption), and try Game Ready vs Studio (gamers want Game Ready).

Driver discipline: update for new games, not reflexively — but when FPS drops appear after a Windows update, the GPU driver is the prime suspect.

Thermal fixes

Thermal fixes: monitor temperatures (HWiNFO — throttling tanks FPS), clean vents (dust is the gradual FPS killer), elevate the rear (airflow), repaste if 2+ years old (degraded paste throttles), and undervolt (less heat, sustained clocks). Thermal throttling is the most common cause of FPS that "used to be fine."

The pattern: FPS fine for 10 minutes, then drops = thermal throttling (cooling cannot sustain). FPS low from boot = configuration (drivers, GPU selection, settings).

Configuration fixes

Configuration fixes: close background apps (Chrome with 50 tabs eats CPU/RAM — close it), disable overlays (Discord, GeForce Experience overlays cost FPS — disable for testing), check in-game settings (a settings reset fixes corrupted configs), verify dual-channel RAM (single stick hobbles performance — CPU-Z confirms), and check storage (full SSDs slow down — keep 15%+ free).

Background apps are the silent FPS killer — Task Manager → Startup, be ruthless.

The stutter: the micro

Micro-stutter: the causes — the background (the apps — the scans — the interrupts); the storage (the slow — the HDD — the hitching); and the drivers (the bad — the version — the rolled back).

The stutter truth: the frametime (the graph — the spikes — the diagnosed); the average (the fine — the misleading — the ignored); and the fix (the cause — the addressed — the smooth). The diagnoser (the Afterburner — the graph — the informed); the guesser (the settings — the lowered — the still stuttering). The stutter (the found — the fixed). The smooth (the frametime — the flat).

The shader: the compilation

Shader compilation stutter: the cause — the shaders (the compiled — the first-run — the hitching); the games (the UE — the notorious — the known); and the fix (the precompiled — the updated — the waited).

The shader truth: the first (the stuttery — the compiling — the normal); the after (the smooth — the cached — the fine); and the updates (the recompile — the drivers — the re-stutter). The patient (the warmed-up — the smooth); the returner (the frustrated — the informed). The shaders (the compiled — the cached). The stutter (the temporary — the understood).

The network: the online

Network fps issues: the cause — the lag (the mistaken — the fps — the network); the online (the server — the tick — the perceived); and the distinction (the fps — the local — the measured).

The network truth: the fps (the GPU — the local — the unaffected); the lag (the network — the teleporting — the different); and the diagnosis (the offline — the tested — the distinguished). The diagnoser (the separated — the correct); the confuser (the blamed-GPU — the lesson). The network (the known — the distinguished). The fps (the local — the true).

The detective's log: the Afterburner

The fps detective's log is the Afterburner: the overlay (the enabled — the fps — the 1% lows); the frametime (the graphed — the spikes — the seen); and the culprit (the identified — the temps — the background). The fps drop diagnosed is the half fixed — the Afterburner reveals. The 5-minute log shows the truth — the thermal, the app, the driver.

The log method: the install (the Afterburner — the free — the configured); the play (the 10 minutes — the logged — the captured); and the read (the graph — the studied — the understood). The logged fps is the honest fps — the average lies, the 1% tells. The detective logs; the culprit confesses.

The silent thief: the background cull

The fps fix's background is the culprit: the antivirus (the scanning — the gaming — the paused); the browser (the 50 tabs — the RAM — the closed); and the updaters (the Windows — the scheduled — the deferred). The 20fps lost to the background is the common — the clean boot restores. The 5-minute cull recovers the frames — the background is the thief.

The cull method: the Task Manager (the sorted — the CPU — the judged); the startup (the pruned — the kept — the lean); and the game mode (the on — the focused — the prioritised). The background is the silent thief — the culled is the caught. The clean system games; the cluttered crawls.

The exorcism: the DDU cure

The fps fix's drivers are the DDU: the corrupted (the updated — the broken — the suspected); the clean (the DDU — the safe mode — the purged); and the fresh (the installed — the tested — the fixed). The driver-caused fps drop is the DDU'd — the clean install cures. The 20-minute DDU is the definitive — the suspected driver, the purged.

The DDU method: the download (the prepared — the new — the ready); the safe (the booted — the minimal — the run); and the install (the fresh — the clean — the verified). The DDU is the driver exorcism — the corrupted, the cast out. The clean driver is the fast driver.

The silent throttle: the thermal fps

The fps fix's thermals are the throttled: the 95°C (the clocked down — the fps — the lost); the dust (the 2 years — the clogged — the cause); and the cool (the cleaned — the repasted — the restored). The thermal fps drop is the gradual — the 6 months, the 10fps, the unnoticed. The cooled laptop restores — the 10°C, the clocks, the frames.

The thermal method: the monitor (the HWiNFO — the temps — the watched); the clean (the vents — the 6-monthly — the maintained); and the repaste (the 3-yearly — the due — the done). The thermal throttle is the silent — the monitored is the caught. The cool laptop is the fast laptop.

Advanced fixes

Advanced: BIOS/firmware updates (manufacturer fixes sometimes address performance), Windows reinstall (the nuclear option for persistent issues — fixes everything software), and hardware faults (failing GPU/CPU — rare, but persistent FPS issues after all software fixes warrant professional diagnosis).

Work through the order: obvious → drivers → thermals → configuration → advanced. Most FPS drops die in the first two stages.

Frequently Asked Questions

Why is my FPS suddenly low?

The most common causes: outdated GPU drivers (update from NVIDIA/AMD directly), thermal throttling (check temperatures — overheating tanks FPS), background apps (close browsers, Discord overlays), wrong GPU in use (ensure the game uses the dGPU, not integrated), and Windows Game Mode/power settings.

How do I make sure games use the dedicated GPU?

Check NVIDIA Control Panel → Manage 3D Settings → Preferred graphics processor (set to High-performance NVIDIA), or Windows Settings → Display → Graphics (set the game to High performance). Verify with the game's overlay or Task Manager (GPU 1 should show activity).

What causes FPS drops over time?

Thermal throttling (cooling — clean vents, elevate, repaste if old), power throttling (plugged in? correct adapter? performance mode?), and single-channel RAM (one stick — add a second for dual-channel). Check HWiNFO for throttling flags.

What is the FPS troubleshooting order?

Update GPU drivers (clean install), verify dGPU usage, close background apps, check thermals (HWiNFO), ensure the charger is connected (performance mode), and reset in-game settings (a corrupted config can tank FPS — delete and reconfigure).