You're barely hitting 144 FPS because your RTX 5070 and Ryzen 7 9700X aren't the bottleneck — the game's graphics menu is. At 1080p and 1440p with all sliders flipped to Low, Black Ops 7's frame rate gets capped by three things a Low preset never touches: the engine's own frame-rate limiter, Windows power and scheduling behavior, and CPU-side driver overhead that the GPU menu can't fix. Until you change those, the card renders frames faster than the game will hand them over. The fixes below are ordered by how often they solve exactly this symptom.
The Low Preset Doesn't Touch the Two Settings That Cap You
The graphics menu is a red herring for this specific complaint. Every slider at Low reduces GPU load, and on an RTX 5070 that means your card finishes each frame well before the CPU needs the next one. Lowering quality further does nothing once you're CPU-bound or limiter-bound, which is why people report identical frame rates at Low and at Extreme.
Two settings outside the quality sliders are the usual culprits. First, Black Ops 7 ships with a frame-rate cap in its Display settings that defaults to your monitor's refresh rate or a "Custom" value; if that cap landed at 144 or slightly under, you'll hover at 140–144 forever. Second, NVIDIA's control panel carries its own "Max Frame Rate" limiter under Manage 3D Settings, and it's applied per application. A cap in either place overrides every quality change you make.
The related concept is CPU-bound versus GPU-bound. Check it directly: open the in-game performance overlay or NVIDIA's overlay and watch GPU utilization. If the GPU sits at 60–80% utilization while your frame rate is stuck near 144, the GPU has headroom and something upstream is gating output. That one reading tells you whether to keep reading this article or look elsewhere.
The low preset also switches off some CPU-side work but leaves others intact, including shadow-cascade and streaming settings that the preset maps conservatively. On a 9700X with eight Zen 5 cores, those settings are rarely the limit at 1080p. The limiter and power behavior almost always are.
Confirm the Cap First: Two Limiters, Three Places to Check
Before touching anything else, verify whether a limiter is holding you. It takes about ninety seconds and saves you from an unnecessary driver reinstall.
1: In Black Ops 7, open Settings, go to Graphics or Display, and find the Frame Rate Limit option. Set it to Unlimited or to a value above your monitor's refresh rate. Apply and close the menu. 2: Right-click the desktop, open NVIDIA Control Panel, and go to Manage 3D Settings. Under the Program Settings tab, select Black Ops 7 from the dropdown and set Max Frame Rate to Off. Do the same under the Global Settings tab. 3: In the NVIDIA app, open Graphics, select the game, and confirm no per-game frame-rate cap has been applied there — the modern app can hold a cap the old control panel no longer shows.
If your frame rate jumps the moment you lift one of these, you're done. If it stays pinned at the same number, the cap wasn't the cause and you should move to the power and scheduling checks.
Watch for a second failure mode: some monitors report a 144 Hz refresh rate but Windows has silently set the desktop to 120 Hz or 60 Hz in Display settings. The game then caps at that lower figure no matter what the in-game slider says. Confirm the refresh rate in Windows Settings, System, Display, Advanced display before trusting any in-game number.
Power Plans and Core Parking Are Costing You Frames
Windows defaults to the Balanced power plan, and on a 9700X that plan lets cores park and clocks fall between frames. In a game that streams assets during play, those micro-sleeps land exactly when the CPU needs to hand work to the GPU. The fix is a power plan that keeps clocks high, plus disabling core parking for the game process.
Open Control Panel, Power Options, and select High Performance or Ultimate Performance (you may need to unhide the latter via the power plan settings). Then open the advanced settings and set Processor power management, Minimum processor state to 100% on the active plan. This stops the scheduler from dropping clocks during short idle gaps between frames.
Core parking is a separate lever. Windows may park half your cores under light load, and Black Ops 7's threaded audio and streaming work can land on a parked core and wait. Third-party tools like ParkControl expose a "disable core parking" toggle, and the same tools let you set the plan's minimum processor state without registry edits. Test with parking disabled for a single session; if frame rate is unchanged, revert it so you don't waste power.
One version-specific detail matters here: on Windows 11 24H2 and later, the power plan that ships as "Balanced" behaves differently from older builds because the scheduler now hands work to preferred cores more aggressively. If you're on an older Windows 11 build, the High Performance plan is the more reliable lever. Check your build under Settings, System, About before assuming the plan names behave the same way.
Game Mode, Hardware-Accelerated GPU Scheduling, and the Scheduler Conflict
Windows Game Mode is designed to give the foreground game priority, and it usually helps. Hardware-accelerated GPU scheduling, on the other hand, is a coin flip depending on driver version and game. The combination is where people get stuck: one helps, one hurts, and you can't tell which did what without changing them one at a time.
Test the pair systematically. Turn Game Mode on, leave scheduling on, and note the frame rate. Then turn hardware-accelerated GPU scheduling off in Settings, System, Display, Graphics, Change default graphics settings, reboot, and note the frame rate again. Do not change both in one session. On RTX 50-series cards with recent drivers, most players report scheduling has a neutral or slightly positive effect, but a minority see a measurable loss.
Game Mode has one documented edge case worth knowing. If you run a capture tool, an overlay, or a streaming app alongside the game, Game Mode can deprioritize it, which sometimes stutters the game as the capture tool fights for scheduling. Disable Game Mode for one session to rule that out.
The scheduler conflict also shows up as uneven frame pacing rather than a flat low number. If your average reads 143 but the game feels like 90, the problem is frame-time variance, not the limiter. Watch the 1% low figure in your overlay; a large gap between average and 1% low points at scheduling or background load, not at the GPU.
Background Load and Storage: The Quiet Frame Thief
At 1080p and 1440p, a 9700X is fast enough that background processes compete for the same cores the game wants. Anything that touches the disk mid-match — a cloud sync client, Windows Update delivery, a browser with many tabs, an antivirus scan — produces frame-time spikes that look like a low average. The average can also fall if the game is waiting on asset streaming from a slow drive.
Storage matters more in Black Ops 7 than in older call-of-duty titles because of the streaming model. Install the game on an NVMe SSD, not a SATA SSD or a mechanical drive. If your SSD is more than about 80% full, its write performance degrades and texture streaming stalls; freeing space is a real fix, not a placebo. Check drive health with the manufacturer's utility before blaming the game.
Run a clean-background test: close every non-essential app, disable startup items in Task Manager's Startup tab, and play one match. If the frame rate rises, add items back one at a time until it falls. This is the only reliable way to find the specific background process responsible.
Antivirus real-time scanning is the most common single culprit. Add the game's install folder and the Battle.net or launcher executable to your antivirus exclusion list, then retest. That one change fixes a meaningful share of "low frames at low settings" reports because the scanner inspects every streamed asset as it loads.
Driver Cleanup and the Version-Specific Pitfall
A driver upgrade does not automatically deliver the best frame rate. Newer drivers occasionally regress on specific titles, and a driver installed over an older one can carry stale configuration. The reliable move is a clean install of a known-good version, done with Display Driver Uninstaller: boot into Safe Mode, remove the current driver completely, reboot, and install the version you want from NVIDIA's site.
The version-specific pitfall is the "Game Ready" versus "Studio" driver split. Game Ready drivers ship with per-title optimizations, and for a new release like Black Ops 7 those optimizations usually help. Studio drivers prioritize stability and can lag behind on day-one game profiles. If you're on a Studio driver, switching to the Game Ready branch is worth testing.
There's also the clean-install checkbox. NVIDIA's installer offers "Perform a clean installation," which wipes your custom 3D settings along with the driver. That's fine if you're chasing a problem, but it means you'll reapply your Max Frame Rate and power settings afterward. Note your settings before you start.
Finally, confirm the driver actually matches the card. A driver installed for a different GPU generation can run but deliver poor performance. Check the adapter name in Device Manager against the model in NVIDIA Control Panel's System Information panel; a mismatch means a reinstall is the first fix, not the last resort.
A Comparison: What Each Fix Actually Buys You
The table below ranks the fixes by the symptom they address and the effort each takes. Values are effort estimates and expected direction of change, not guaranteed frame counts — frame gains vary by resolution, monitor, and driver version.
| Fix | Symptom it addresses | Effort | Expected direction |
|---|---|---|---|
| Lift in-game frame cap | Pinned at 140–144, GPU under 80% utilization | 2 minutes | Large if a cap was set |
| Lift NVIDIA Max Frame Rate | Same as above, cap set per app | 3 minutes | Large if a cap was set |
| High Performance power plan | Clocks dipping between frames | 5 minutes | Moderate to large |
| Disable core parking | Frame-time spikes on threaded work | 10 minutes | Small to moderate |
| Test GPU scheduling toggle | Uneven pacing, version-dependent | 15 minutes, includes reboot | Neutral to moderate |
| NVMe install and drive space | Texture streaming stalls | 30–60 minutes | Moderate if on slow drive |
| Clean driver reinstall | Regression after update | 30 minutes plus Safe Mode | Moderate |
| Background cleanup | Spikes tied to specific apps | 20 minutes | Moderate |
Rank by effort first, symptom second. The two cap checks cost five minutes combined and are the single most common cause of a frame rate that sits just under a round number like 144. Do them before anything else in this table.
Verdict: start with the limiters, then power, then background load. Driver work and storage changes come last because they're slower to test and less likely to be the cause when the symptom is a flat ceiling rather than a stutter.
Resolution and Refresh Rate: Why 144 Is the Number You're Seeing
The specific figure of 144 is a clue, not a coincidence. It's a common refresh rate, and both the game and the driver default their caps to the display's reported refresh rate. If your monitor is a 144 Hz panel and Windows reports it correctly, the game will cap there by default and you'll see 140–144 as your ceiling. The card isn't struggling; it's being asked to stop.
At 1080p, the RTX 5070 should have substantial headroom in Black Ops 7 at Low settings, meaning the GPU is nowhere near its limit. That's exactly the scenario where CPU-side and limiter issues dominate. At 1440p the card works harder but still shouldn't be pinned at a low preset unless something upstream caps it. At 4K, the picture changes and the GPU becomes the limit — but the query specifies Low settings, which points away from a GPU limit at 1080p and 1440p.
If you've raised the cap and the frame rate still won't climb, check the resolution scale setting in-game. A render resolution above 100% silently increases GPU load even at Low quality, and it's easy to leave at 150% after experimenting. Set it to 100% and retest.
Refresh rate and frame rate are different numbers, and confusing them sends people down the wrong path. A 144 Hz monitor can display 200 FPS if the game allows it, and capping at 144 is a legitimate choice for smoothness. But if your goal is to know whether the hardware can go higher, lift every cap first.
FAQ
Does the Ryzen 7 9700X bottleneck an RTX 5070 at 1080p?
At 1080p Low settings in Black Ops 7, the CPU becomes the more likely limit simply because the GPU finishes frames so quickly, but the 9700X is a strong eight-core Zen 5 part and isn't a hardware bottleneck in the usual sense. The practical limit is software: caps, power plans, and background load. If lifting every cap and setting High Performance still leaves you at 144, then the CPU-side path is the ceiling and the fix is scheduling, not a new CPU.
Why does my FPS stay exactly the same at Low and Extreme settings?
Identical frame rates across quality presets is the signature of a frame-rate cap or a CPU-side limit. If the GPU isn't the constraint, changing GPU quality settings can't move the number. Check both limiters first, then confirm GPU utilization is below about 80% while capped — that reading proves the card has headroom and the ceiling lives elsewhere.
Is Windows 11 Game Mode hurting or helping Black Ops 7?
For most players it helps by prioritizing the foreground game, but it can backfire if you run capture or overlay software alongside the game. Test it in isolation: one session with it on, one with it off, no other changes. Don't judge it from a session where you also changed the GPU scheduling toggle, because you won't be able to attribute the result.
Should I disable hardware-accelerated GPU scheduling?
Only test it if you've already ruled out caps and power settings, and change it alone so you can attribute the effect. On RTX 50-series cards with recent drivers, many players see neutral results and some see a small gain from leaving it on. A minority see a loss; if your frame pacing worsens after enabling it, turn it back off and reboot.
Can a driver update actually lower my frame rate?
Yes, and it happens often enough that a clean reinstall of a known-good version is standard troubleshooting rather than superstition. Driver regressions on new titles are documented in community reports each release cycle. If your frame rate dropped right after an update, rolling back one version is a cheaper test than any hardware change.
Does installing the game on an SSD really matter for frame rate?
It matters for frame-time consistency more than for the average. Black Ops 7 streams assets during play, and a slow or nearly full drive produces stalls that show up as 1% low drops rather than a lower average. If your average is fine but the game feels choppy, check drive space and health before touching graphics settings.
What if none of this works and I'm still at 144?
Then the ceiling is genuine for your resolution and settings mix, and the honest next step is measuring where the time goes with a frame-time capture rather than guessing. Confirm your monitor's actual refresh rate in Windows first — a 120 Hz panel set to 144 Hz in the game menu will still cap at the panel's real limit. If the panel is genuinely 144 Hz and every cap is lifted, the system is behaving as configured.
Is 144 FPS actually a problem if my monitor is 144 Hz?
No — matching your refresh rate is the intended behavior and produces the smoothest output. The problem worth solving is a frame rate that sits under 144 because of a cap you didn't set or a power plan that's throttling the CPU. If you're hitting a stable 144 with headroom to spare, you've solved the real issue; chasing a higher number only matters if you're diagnosing the hardware's ceiling.