FPS Suddenly Dropped: How to Find the Cause

Reproduce
the problem in the same game and scene

SAFE

Reproduce the problem in the same game and scene. Verify resolution,
render scale, ray tracing, graphics preset and frame caps.

If the same scene now uses a higher render scale, ray tracing setting or different cap, restore the previous setting and compare again. If settings match but sustained average FPS is lower, investigate background load and clocks. If average FPS remains normal but delivery hitches, use the Stuttering guide.

Restart the PC and use Task Manager to check for unexpected CPU, memory
or disk load

SAFE

Restart the PC and use Task Manager to check for unexpected CPU,
memory or disk load.

If an unexpected process consumes resources during the slow scene, identify it and retest after it finishes or is safely closed. If background use is ordinary, this check does not explain the drop; move to temperatures and clocks.

Monitor CPU/GPU
temperatures and clocks

CAREFUL

Monitor CPU/GPU temperatures and clocks. Intel documents thermal
throttling as clock reduction at thermal limits and lists reduced
speed/stuttering as symptoms.

If clocks fall as the exact model reaches its documented thermal limit, throttling is a plausible performance cause; use the relevant CPU or GPU heat guide. If clocks and temperatures stay broadly consistent, investigate power mode and recent changes rather than assuming overheating.

Check Windows power behaviour and, on laptops, confirm the intended
charger and mains/battery mode

CAREFUL

Check Windows power behaviour and, on laptops, confirm the intended
charger and mains/battery mode.

If the laptop performs differently on battery or with an unsuitable charger, compare again using its intended supported power setup. If power mode is unchanged, note that and move to the timing of game, Windows and driver changes.

Review recent game, driver and Windows changes if the performance drop
began immediately afterwards

CAREFUL

Review recent game, driver and Windows changes if the performance
drop began immediately afterwards.

If the drop began immediately after a specific change, check official release notes and supported rollback or settings paths, changing one thing at a time. If several games show the same loss, look beyond one game’s patch; timing is evidence, not proof of cause.

Check free storage and startup/background apps; Microsoft identifies low
storage and background activity as performance factors

CAREFUL

Check free storage and startup/background apps; Microsoft identifies
low storage and background activity as performance factors.

If storage is critically full or a startup app is busy, free appropriate space or isolate the app and repeat the same comparison. If neither changes the result, this branch is less likely; preserve the baseline before considering hardware.

Only consider an upgrade after confirming the existing PC is operating
normally for its specification

ADVANCED

Only consider an upgrade after confirming the existing PC is
operating normally for its specification.

If the PC again performs as expected for its exact configuration, an upgrade is not a fix for a sudden regression. If a sustained limitation remains across comparable workloads after the safe checks, use measured needs to plan an upgrade rather than guessing.

Still not fixed?

Not sure whether you’re seeing a steady FPS drop or intermittent stutter? Use the PC//FIX symptom checker to choose the right troubleshooting path.

Stop repeating the same fixes. Record the hardware configuration,
exact symptom, temperatures or debug codes where relevant, and every
test already completed. Use that evidence to move into the related
PC//FIX guide or contact the component/system manufacturer when
controlled substitute testing or warranty support is required.

How to reduce repeat
problems

Keep Windows and appropriate drivers maintained, keep the PC clean
with sensible airflow, leave storage headroom, use stable settings and
make one hardware or tuning change at a time. A known-good baseline
makes future faults much easier to diagnose.

Frequently asked questions

Should I buy
replacement parts to test the problem?

Not as an early step. Known-good substitute hardware is useful when
you already have it, but buying components at random is expensive
diagnosis.

Should I update the
BIOS as a general fix?

No. Firmware updates should have a specific compatibility, stability
or security reason and must follow the motherboard or system maker’s
instructions.

Can
XMP, EXPO, overclocking or undervolting cause problems?

Yes. Returning to stock is a useful diagnostic test, but it does not
prove the feature or component is permanently faulty.

Should I reinstall Windows?

Only when evidence points to an operating-system problem and less
disruptive checks have been exhausted. A reinstall cannot repair
hardware that fails before POST.

When should I stop
troubleshooting?

Stop for electrical hazards, physical damage, data-loss risk you do
not understand or work beyond your confidence level. Never open a
PSU.