Quick Answer

Most FPS drops on an RX 9070 XT build come from driver leftovers, shader cache rebuilds, power limits, ReBAR state or CPU scheduling, not from a broken game. Prove it with DDU, RTSS, CapFrameX, PresentMon and HWiNFO; 1% lows should sit within about 70% of average FPS.

Find The Real Limit

Use one repeatable test scene and record average FPS, 1% lows and frame time. For RX 9070 XT build, the useful tools are DDU, RTSS, CapFrameX, PresentMon and HWiNFO. Do not judge by feel alone: 60 fps equals 16.7 ms, 144 fps equals 6.94 ms, and 240 fps equals 4.17 ms.

Checks For This Setup

For RX 9070 XT build, start here: clean install the driver, check HAGS or Adrenalin settings, confirm PCIe width, rebuild shader cache, and retest one scene. Keep RX 9070 XT in mind because its driver, firmware or control software can change how the system behaves after an upgrade. Use broad price context as a sanity check: high-end CPUs and GPUs run from about R8,000 to well above R40,000.

If the setup uses online play, separate network stutter from frame pacing. RTSS shows the frame-time graph; ping and jitter tools show the connection. A router change can affect online movement, but it should not reduce local benchmark FPS unless software or USB services changed too.

Settings To Verify

Confirm monitor refresh rate, in-game FPS cap, VRR or FreeSync/G-Sync state, and overlay recording. On GPU builds, check ReBAR, PCIe link width and driver state. On laptops or handhelds, match charger, TDP profile and performance mode to the FPS target.

FAQ

Why did my RX 9070 XT build start showing FPS drops?

The likely cause is driver leftovers, shader cache rebuilds, power limits, ReBAR state or CPU scheduling. Use DDU, RTSS, CapFrameX, PresentMon and HWiNFO so you can see whether the limit is GPU load, CPU scheduling, storage, USB, audio, thermals or network jitter.

Should I replace hardware first?

No. Many fixes cost R0 because they come from drivers, firmware, FPS caps, refresh settings or power profiles. Buy hardware only after the same test proves the part cannot meet target.

What number proves the fix worked?

Watch 1% lows and frame time, not only average FPS. A good fix makes the graph flatter: 144Hz should sit near 6.94 ms and a 60 fps cap near 16.7 ms.

TIP

Troubleshooting Check

Save one before-and-after result from RTSS or CapFrameX, then keep the setting that improves 1% lows without reducing image quality more than needed.