What actually happens to your PC when you game

Your PC doesn't just "show images"

When you game, your PC is doing thousands of things per second: reading your keyboard and mouse, calculating game physics, deciding what's visible on screen, rendering every pixel, and sending it all to the monitor. All of that has to happen in order, and all of it has to happen fast.

Most of these stages are invisible. You can't see them, and your FPS counter doesn't measure all of them. But each one can add time between what you do and what appears on screen.

The journey of your click to the screen

Imagine you press the left mouse button to shoot. Here's what happens, step by step, before you see the shot on screen:

1. Your mouse detects the click and sends it via USB to the processor. This takes less than 1 ms on a modern gaming mouse.
2. Windows receives the signal and passes it to the game. This is where the OS steps in: it has to decide which process gets the signal and when to deliver it.
3. The game engine processes the action: it calculates the trajectory, physics, animations, and which objects are visible from your position.
4. The CPU prepares the draw calls and sends them to the GPU.
5. The GPU renders the complete frame: geometry, textures, lighting, shadows, post-processing.
6. The finished frame is stored in a buffer and sent to the monitor at the next refresh window.

Each step is an opportunity for something to take longer than it should. The sum of all those times is what you perceive as "lag" or "lack of smoothness".

The CPU: conductor and musician at the same time

The CPU doesn't just run the game — it also runs Windows, drivers, background services, telemetry, networking, and everything else on your PC. It has to split its time between all of them.

A modern game can need one or two CPU cores almost exclusively for the main render thread. If those cores are also running system processes, the game has to wait its turn.

That wait doesn't show up as "high CPU usage". Your processor can be at 40% total usage and still make the game wait, because the bottleneck is on a single core, not the entire processor.

The GPU: fast, but waiting for instructions

Your graphics card might be capable of rendering hundreds of frames per second, but it can only work with what the CPU sends it. If the CPU is slow to prepare draw calls, the GPU sits idle — and that dead time is invisible.

This is what's called a CPU bottleneck: the GPU finishes its work and waits until the CPU gives it the next frame to draw.

The result isn't always low FPS. It can be high but irregular FPS: the GPU produces frames quickly when it receives instructions, and holds them back when it doesn't. That irregularity is stuttering.

The operating system: referee and player at the same time

Windows isn't a simple intermediary between the game and the hardware. It's an active participant that consumes resources:

• The task scheduler decides every few milliseconds which process uses each CPU core.
• Hardware drivers manage communication with GPU, audio, network, and USB — each with its own interrupts.
• System services (updates, indexing, telemetry, Defender) can activate at any moment.
• The Desktop Window Manager (DWM) handles how windows are presented on screen, even in fullscreen mode.

None of these tasks are unnecessary — the system needs to function. But Windows' default configuration doesn't prioritize gaming, and each of them can introduce microseconds of latency that add up frame after frame.

All of this happens thousands of times per second

At 60 FPS, this entire process — from input to screen — repeats 60 times per second. At 144 FPS, 144 times. At 240 FPS, 240 times. The margin for each frame shrinks as you go higher.

At 60 FPS, you have 16.6 ms to complete the entire pipeline. At 144 FPS, 6.9 ms. At 240 FPS, 4.1 ms. Any interruption that lasts longer than that margin produces a visible stutter.

That's why what happens between your GPU and the screen matters so much: it's not that your hardware is slow, it's that the path between your click and the image has stops nobody has reviewed.

Knowing what happens is the first step to fixing it

Most gaming performance problems aren't hardware problems. They're configuration problems: how Windows distributes work, which drivers are installed, which services run without you asking, and how processor power is managed.

Measuring these times — frametime, DPC latency, CPU scheduling — is what separates a real diagnosis from a list of tweaks copied from the Internet. It's the first thing we do in every LATENT session.