Why do I get micro-freezes mid-match in Warzone?

Three causes, in order of frequency. Shader compilation that has not finished, after a game or driver update. Texture streaming going past your video memory. And a background program waking up at the worst moment, an automatic update for instance. Hitching does not show in average FPS. Look at your 1 % lows: that is the measurement matching what you feel with a mouse in your hand.

Should I disable Secure Boot or TPM to gain FPS?

No, and definitely not. Activision requires TPM 2.0 and Secure Boot to launch Call of Duty: Warzone. Disabling them gains no frames, it simply stops the game from starting. Same answer for virtualization in the BIOS. We leave it alone. The FPSDoctor BIOS assistant only reports its state, it will never push you to switch it off.

Do I need an SSD for Warzone?

In practice, yes. Activision lists 116 GB on an SSD in both the minimum and the recommended spec. On a hard drive, texture streaming cannot keep up: you get textures arriving late and hitching every time you change area. If you have both, put Warzone on the SSD, even if that means uninstalling something else. It is the best trade on this list.

How much RAM does Warzone need?

Activision lists 8 GB minimum and 12 GB recommended. In real life, with Windows, a browser and Discord open, 16 GB is the comfortable floor. Quantity is not everything. An XMP or EXPO profile that was never enabled runs your memory below the speed you paid for. The FPSDoctor BIOS assistant flags it and shows you where to turn it on.

Can FPSDoctor cause a problem with Warzone's anti-cheat?

FPSDoctor does not inject into the game, does not read its memory and does not modify any of its files. It acts on Windows, on your graphics driver panel and on what runs in the background. It will also never ask you to turn off Secure Boot or TPM, which are exactly what the anti-cheat checks at launch.

More FPS on
Call of Duty: Warzone

Without FPSDoctor

112FPS

+53%

With FPSDoctor

171FPS

Measured on RTX 4070, Ryzen 5 7600, 16 GB

You have the hardware, the game sits on an SSD, and Warzone still hitches the moment the circle closes in. Your graphics card is almost never the first thing to give up.

Most of what you can get back is not in the game menu. It is in Windows, in your graphics driver panel, and in two settings your BIOS has probably left switched off since day one.

What really holds Warzone back

Warzone runs on the IW 9.0 engine and requires DirectX 12. Activision lists 116 GB on an SSD, 12 GB of RAM in the recommended spec and 8 GB of video memory. Those numbers are not decoration: the game streams textures continuously during a match. The moment it runs short of VRAM or disk bandwidth, it does not show up in your average FPS, it shows up as hitching.

Second trap, a Call of Duty classic: shader compilation. The game redoes it after a major update and after a graphics driver change. Until it finishes, you play with micro-freezes you would happily blame on your connection.

Third trap, the most common and the dumbest: everything running next to it. Warzone wants the whole machine. A browser with twenty tabs, a peripheral suite, a streaming client and six programs launched with Windows cost you more frames than the shadow setting you keep lowering.

One last thing, worth knowing before you follow a guide found elsewhere: Warzone requires TPM 2.0 and Secure Boot. Those are launch conditions, not performance options. Turning them off gains you nothing and simply stops the game from starting.

What FPSDoctor fixes for Warzone

FPSDoctor never touches the game. It works on Windows and on your graphics driver, where the frames are lost before Warzone even opens.

The FPSDoctor power plan stops your CPU from dropping its clocks mid-match. The gaming tweaks and the network latency optimization take over system scheduling and the network stack. Cleaning up startup programs hands back the RAM and CPU time Warzone is asking for, and on this game specifically that is often where most of the gain comes from.

The GPU optimization applies a profile in your driver panel, NVIDIA, AMD or Intel depending on your card, after saving whatever was there. Nothing is one way.

Game mode closes or drops to low priority whatever runs next to the game when you launch Warzone, then puts everything back when you quit. That is exactly what a machine with enough power but not enough free capacity is missing.

The BIOS assistant checks what your motherboard left switched off, starting with the XMP or EXPO memory profile, and walks you through enabling it yourself. It never writes anything to your firmware, it tells you where to go.

Finally, the built-in counter measures your average FPS and your 1 % lows before and after. On Warzone, the 1 % low is the number that tells the real story.

The average gain we measured on Warzone

On your machine it will move, in both directions. A well tuned PC will gain less. A PC with fifteen startup programs, a balanced power plan and a memory profile that was never enabled will gain more, sometimes a lot more.

The only number that truly matters is yours. Start the built-in counter, play a match, apply, play another one. You have your answer in ten minutes.

DOWNLOAD IT FREEFree version, no card required

What this is based on

Activision, configuration PC requise pour Call of Duty: Warzone2026-08-27

What players actually ask us about Warzone

Your questions

Because power is useless if it is not available. Warzone wants VRAM, disk bandwidth and free cores at all times. A recent PC that spends half its resources on background programs will deliver fewer frames than a modest, clean one.

Look in this order: what launches with Windows, your power plan, then your motherboard's memory profile. That is where the gains are, not in the game's graphics menu.

The Doc is online

You

My PC beats the recommended spec, so why does Warzone run badly?

The Doc

Look in this order: what launches with Windows, your power plan, then your motherboard's memory profile. That is where the gains are, not in the game's graphics menu.