Why does Call of Duty: Modern Warfare II feel stuttery even when the FPS counter looks fine?

Call of Duty: Modern Warfare II can show a decent FPS counter while still feeling weirdly choppy. The usual pattern is smooth movement for a bit, then short spikes when the camera turns or a busy area loads.

What is the cleanest way to test whether this is a shader, CPU, VRAM, or overlay problem? The setup points worth checking here are shader optimization, safe mode, texture streaming, and DirectX crashes. I’m looking for a fix order that does not start with reinstalling the whole game.

Start with a controlled frame-time test instead of dropping every preset.

1. Disable third-party overlays and recording tools for one run.
2. Use exclusive fullscreen if Call of Duty: Modern Warfare II supports it; otherwise test borderless with Windows fullscreen optimizations both on and off.
3. Set a frame cap a few FPS below the refresh-rate limit or below the FPS the PC can hold consistently.
4. Clear only the Windows DirectX shader cache after a driver change, then let the first launch finish rebuilding.
5. Watch GPU usage, VRAM use, and one or two busy CPU cores. High GPU use points to graphics load; low GPU use with one maxed core points to CPU or simulation load.
6. Reduce textures only when VRAM is close to full. Reduce crowd, view-distance, physics, or simulation settings when the CPU is the limit.

For Call of Duty: Modern Warfare II, pay special attention to shader optimization, safe mode, texture streaming, and DirectX crashes. Change one item at a time and retest the same location. A stable cap usually feels better than a higher average with constant spikes.

One extra check: run the same scene twice after a reboot. If pass two is clearly smoother, shader or asset caching is involved. If both passes spike at the same camera angle while GPU usage drops, look at CPU or storage. Keep shader optimization, safe mode, texture streaming, and DirectX crashes unchanged during the comparison so the result means something.