Valorant Hitreg Desync Fixed

[ptaylor54]

Fixed my Valorant "bullets pass through" hit reg issue — turned out to be P-core saturation from background apps

System: i5-13600KF, RTX 5080, 32GB DDR5

The symptom
Bullets would visually land on target but not register as hits — the classic "shot went straight through them" feeling. I noticed it correlated with having Chrome open, got worse if any videos were played, which I intially chalked up to internet but after upgrading my router to the glinet flint 3 and getting A+ bufferbloat scores with rock solid up and down speeds with no packet loss I began to rule that out. Closing everything made it noticeably better, but things would always feel a little delayed or off. This is due to certain other apps I always had to have running as they are essentials: Discord, Apple Music, etc...

What I ruled out

Before landing on the real cause, I checked and ruled out, in order:
- Chrome hardware acceleration— already off, didn't help (also: this setting only affects page content rendering, not Chrome's own GPU compositor process, which still runs regardless)
- Chrome extensions — disabled all of them, no change
- Network jitter / ping — logged it directly, jitter sat at 0.8-1.6ms and render latency ~4ms whether Chrome was open or closed. Completely ruled out network as the cause.
- Discord overlay — already disabled
- Discord hardware acceleration— already off
- Discord Krisp noise suppression — wasn't even in a voice call, so this wasn't it either

None of these specific features were the cause. But fully closing Chrome or Discord still helped, even with all their "problem" features already disabled. That was the key clue: it wasn't a specific feature in these apps, it was just having them open at all.

The actual cause: P-core contention

I logged CPU utilization with HWiNFO during normal gameplay and found my P-cores running sustained at 88-96% utilization, while the E-cores sat mostly idle at 8-20%. The GPU, meanwhile, was only at 44-51% utilization — confirming the bottleneck was CPU, not GPU, despite having a 5080.

With P-cores already nearly maxed out just from the game itself, Windows' scheduler was apparently placing background app threads (Chrome's renderer/GPU processes, Discord's Electron processes) onto those same P-cores rather than the idle E-cores. Any additional background thread activity — even light, even idle — was enough to occasionally steal a P-core cycle the game needed at that exact moment, causing the click-vs-actual-position mismatch that manifested as "bullets passing through."


The fix: pin background apps to E-cores with Process Lasso

1. Install Process Lasso (free version is enough) from bitsum.com.
2. In Task Manager, identify which CPU numbers are your P-cores vs E-cores. On the 13600KF: **CPUs 0-11 are the 6 P-cores** (2 threads each from hyperthreading), CPUs 12-19 are the 8 E-cores (1 thread each, no hyperthreading).
3. In Process Lasso, right-click a running instance of the background app (e.g. `chrome.exe`, `Discord.exe`) and set its **default CPU affinity by process name (not just the current instance) to only CPUs 12-19. This makes the rule apply automatically to every future process with that name, which matters because Chrome/Discord spawn many separate processes (one per tab, GPU process, helper processes, etc. — this is normal Chromium/Electron architecture, not a bug).
4. Repeat for any other background apps you keep running alongside games — launcher web helpers (Epic, Steam), other Electron-based apps (Spotify, Slack), etc. Just don't touch the game process itself or core Windows system processes (svchost, explorer) — leave those on full affinity.
5. Process Lasso's own footprint is negligible, no need to restrict it too.

Result:
Hit registration became consistent even with a YouTube video playing, music streaming, and Discord open simultaneously — the exact combination that used to cause misses.

Why a frame cap alone might not fully fix this

Worth noting: lowering in-game graphics settings didn't matter here, because the bottleneck was never the GPU (44-51% utilization the whole time). If you're CPU-bound like this, graphics settings won't move the needle much. A framerate cap *can* help independently, since per-frame CPU work (input, game logic, draw call submission) scales with framerate, so capping FPS reduces total CPU demand — but if your real problem is contention from other apps rather than the game's own demand, the affinity fix addresses the actual cause instead of just reducing overall load.

How to check if this applies to you

Download HWinfo and log a session of you playing the game with your usual settings. Then look at the readouts or have an ai agent tell you your cpu utilization percentages. If they are very high consider trying this method.

[DangerAhead710]

And it's been how many days since this fix has been working for u the same?

[ptaylor54]

And it's been how many days since this fix has been working for u the same?

A week now and the hitreg is perfect every game. If I close process lasso and let the affinities reset to stock settings the desync comes back immediately.

[DangerAhead710]

Ok I'll try it tonight and write my experience

[darkbebe]

a really interesting post , can't wait for every intel owners to test it and give us a feedback
i sadly have an amd

[DangerAhead710]

I just realised I don't even have any other apps open when I play and also I have every startup app disabled from task manager. No chrome , no discord, no gaming related apps or anything else. XD

[ptaylor54]

I just realised I don't even have any other apps open when I play and also I have every startup app disabled from task manager. No chrome , no discord, no gaming related apps or anything else. XD

Unfortunate. I do think that it might still be worth looking at your p-core utilization rates when playing valorant. If the desync is cause by the p-cores running up to their limit, you could potentially find other ways to mitigate that problem like a frame caps, cpu overclocks, etc..

[DangerAhead710]

Do I have to set the valorant and it's other related branching processes to P cores ?

[ptaylor54]

Do I have to set the valorant and it's other related branching processes to P cores ?

No I just kept them on all core usage. For my system at least valorant seems to saturate the p-cores predominatly. I do wonder if I completely put them onto p core usage so they are completely seperated from other programs on the e cores it would run even better. But right now I'm happy enough with the results I'm just gonna keep it as is.

[Sz3ypy]

I use process lasso almost year , its help a lot on 12700k , i dont know about desync or hit reg but help with frame times and P1 fps. Also i recommend use affinity for GPU, USB and nic to move from core 0
Edit i talk about cs2 i forgot sat , i dont know nothink about valorant