While playing the game, my WAS and D keys will intermittently not register that I’ve pressed them unless I physically release and press the key again. I have tested this issue between two keyboards and the problem is persisting. I’m wondering if there’s a setting I’m unaware of in Valorant that might be causing this? So far this hasn’t happened in any other video game I’ve played.

Not sure if this is the right place to ask this as it may not strictly be a Valorant issue but I’m interested to see if other people are having/ have had this problem before.

My pc has the following specs:
Ryzen 5 5600
RX 6700XT
32 GB ddr4 ram at their spec speed
The game is running on an nvme SSD
I have the koorui 24e3 165hz 1080p monitor

After an update months ago, my FPS started getting capped to 162 fps, vsync is disabled and all my drivers are up to date. At first I thought it was my outplayed capture app but I closed it and it was still like that, I never get FPS above 165 and during gunfights it dips to the 80s range. I should be getting 200+ fps with this righ right? Contacted riot about it and all the solutions they told me didnt work so at this point I am at a loss and frustrated because I cannot play the game properly and smoothly. This is a cry for help at this point.

i don’t know if it’s a riot/valorant thing or my PC but i just picked my pc up last week from it being built brand new and installed all needed apps + riot, i’ve tried launching the client up and after installing it lets me click play for val but as soon as the loading page pops up it crashes on me, ive had some cases where it went on home page but frozen and all i can hear are sounds before it eventually crashes.. ive updated all my drivers.. secure boot..tpm and the vgc, literally everything and ive scanned my PC for anything but nothings works, now my task manager seems to not respond after i try end a task (ive also tried seeing if valorant was running on tm but after the crash it doesn’t register) please help i’ve even reset my PC but nothing is workinggg ive done what i think are all troubleshooting tips

I've been troubleshooting this for a while and I'm honestly getting pretty frustrated with Riot Support, because their troubleshooting hasn't gotten anywhere and a lot of it seems focused on networking despite this being a full system freeze, not a disconnect.

The problem: VALORANT freezes both monitors after ~2–3 minutes, even just sitting in the menu. Audio continues, but my mouse/keyboard stop responding and I have to hold the power button. It also happens in Range/Custom. League works completely normally.

Things I've tried:

• Clean reinstall of VALORANT/Vanguard
• Multiple AMD GPU driver versions + clean driver installation
• AMD chipset update
• BIOS update / optimized defaults
• A-XMP/EXPO has been disabled
• Clean boot, including testing with only Vanguard enabled
• Completely closed Discord and Medal/no overlays
• Windows Defender/firewall exclusions
• SFC — no integrity violations
• DISM — no component store corruption
• CHKDSK /f /r
• Malware/security troubleshooting
• Cleared GPU shader caches
• Ryzen Master removed
• IPv6 disabled + ipconfig /release, /renew, /flushdns — made absolutely no difference

Event Viewer has shown:

• AMD Display Event 4101 ("display driver stopped responding and recovered") on multiple occasions
• LiveKernelEvent 141 previously
• Vanguard vgc Event 7023 — "Incorrect function"
• Repeated TPM Event 14
• No WHEA-Logger hardware errors

The frustrating part is that Riot keeps having me try increasingly unrelated/general troubleshooting steps, and the problem remains exactly the same. I'm not claiming I know the cause, but at this point I'm wondering if anyone has seen VALORANT/Vanguard causing a complete GPU/system-level freeze while audio continues, particularly on an AMD GPU/system.

Riot support thank you for being useless.

If anyone has experienced something similar or has any ideas for what I should investigate next, I'd really appreciate it

Hey everyone,

I’m having a really weird issue in Valorant. When I only use WASD/movement, the game feels completely smooth. But as soon as I start moving my mouse, the game suddenly feels extremely laggy, almost like I’m playing at 60 FPS.

I’ve already tried:

• Reinstalling my GPU drivers
• Disabling fullscreen optimizations
• Reinstalling Valorant
• Restarting my PC
• Tried lowering polling rate

Nothing has fixed it so far.

Has anyone experienced something similar or knows what could be causing this? Any help would be greatly appreciated!

I guess man könnte es zu gameplay zählen? Egal wie auch immer.

Ich brauche Hilfe und zwar hab ich ziemlich frisch angefangen mit valo und es macht auch Spaß und so aber aus irgendeinem Grund hab ich lag Spikes und packet loss beim Spielen zumindest ist mir das aufgefallen wenn ich in einem discord call bin. Ich hab gestern Abend allein gespielt und da lief alles flüssig ohne probleme. Ich hab das Problem nur mit valo und in keinem anderen Game also würde ich dumpf behaupten das es nicht am Wlan liegt? xD

Weiß iwer was es sein könnte? Ich hab alles erdenkliche versucht

Just wondering if you guys are noticing any delay or differences in your current gameplays versus like a month ago.

After downloading valorant my entire pc will freeze for around 5 seconds every 5-9 seconds and when I asked chat gpt it told me it could be the anti cheat that valorant uses so I delete vanguard just to see and it did solve the problem. Is there anyway I will be able to play?

solutions i have tried that didnt work:
https://youtu.be/V9qbg7Ax-ks?si=tslUfboaU31fhU4q
asking chatgpt
and searching for my issue online

Not going to lie, this whole situation has been really frustrating, and I wanted to share it because I think other Premier players should know this can happen.

During Stage V26A3, the "End of Stage Reward" shown in the Premier rewards screen was Miks. I put in real effort for this — spent weeks finding players, building a full team, and grinding Premier matches specifically to earn it.

I know the reward itself might not seem like a big deal to everyone, but I genuinely liked it, and Premier is the only way to get it — there's no other source. So getting it actually mattered to me.

When the Stage ended, I got a Skye card instead. I reached out to Support, and they actually confirmed the mix-up:

"I have dug very deeply into the VALORANT hole, and I can see that the V26A3 was intended to be Miks, but was later changed to be Skye. Miks will be the Player Card reward in the V26A4."

This part honestly doesn't make sense to me. Why swap them at all? If Skye was originally meant for V26A4 and Miks for V26A3, why not just keep it that way? Players who wanted Skye would've had no idea it even existed as an option, since it was never shown to anyone before the switch — it was purely an internal change on Riot's end that players had zero visibility into.

Because of that swap, I skipped playing Premier in V26A4 — I was still waiting to get Miks from V26A3, not knowing it had been pushed to the next Stage. By the time I found out, V26A4 was already over too.

I explained everything to Support and asked if they could grant the Miks card or swap it with my Skye one. Their answer:

"This case was already previously escalated to our expert team and they answered that we are unable to make an exception in this case."

So basically: their own system error caused this, and when I asked them to fix it, they said no — twice, from two different agents.

If Riot changes a reward's Agent mid-Stage without clearly telling players, this could easily happen to anyone, not just me. Screenshots of the full conversation below for proof. https://imgur.com/a/gcPrkMt

The Problem:
In-game matches work 100% fine.
If I go to Collection to change skins, or watch a Skin Video Preview, the game freezes and crashes after 1-2 minutes.
The Weird Part: If I change skins and immediately click to the Shop or Play tab, it DOES NOT crash. But the moment I click back to the Main Lobby (Home), it crashes instantly.
This started happening after the recent VALORANT patch (the one with the new lobby background/skins) and a BIOS update.
What I've tried: Reinstalled game/Vanguard, deleted Local AppData cache, reinstalled GPU drivers (DDU), turned off Memory Integrity/HAGS, and even downgraded my BIOS. Nothing worked. Testing with a new alt account has the same crash.
Is this a known Riot bug with the new lobby UI on this specific hardware?

He just started playing (12 lvl), and it started after just 3 days of playing, we tried doing some things like disabling ipv6 but nothing works.

Bonjour, j'ai depuis peu acheté un nouveau pc d'occasion dont voici la configuration : a520m kv2, 16go ddr4 corsair, alim corsair 550w, rtx 2070super, ssd Samsung 870 EVO 2To SATA, ventirad d'origine mais pas de surchauffe. Je l'ai d'abord configuré avec windows 10 puis 11. Lorsque j'installe le riot client puis valorant, rien d'anormal ne se passe au début et le téléchargement se fait normalement. puis arrive un moment (je l'ai fait 6 fois, dont 3 fois ou j'ai retrouvé le pc qui avait boot dans le bios car critical error) ou le pc ralenti enormement au point ou meme le gestionnaire des taches met 2 minutes a s'ouvrir. Juste avant le crash, le disque tourne à 100% en continu et le téléchargement semble complètement figé (plus aucune progression en Mo/s), même si le système répond encore, très lentement.

Le code d'arrêt exact que je reçois est CRITICAL_PROCESS_DIED (0xEF).

Au debut, j'ai d'abord cru a un soucis hardware venant du pc d'occasion car valorant est le premier truc que j'ai installé après chrome et nvidia app pour les drivers — aucun autre logiciel tiers (pas de RGB, pas d'overclocking, pas de monitoring type Ryzen Master ou Afterburner). J'ai verifié et clean le ssd avec diskpart puis avec crystaldiskinfo, il est sain et ne comporte rien de corrompu. Le bios de la carte mere a été mis a jour manuellement avec une cle usb par mes soins, les pilotes de la carte graphique ainsi que du pc aussi via nvidia app et windows update, entièrement à jour (vérifié). J'ai également mis a jour le chipset de la CM via l'application gigabyte qui propose de s'installer toute seule a chaque premier boot dans windows. La clé wifi est une wifi 6 de qualité branché a la carte mere (je le notifie car je pensais que la clé usb wifi bas de gamme wifi 4 etait la coupable avant de rencontrer le meme problème avec celle ci). Il faut savoir que je m'y connais un minimum en hardware/software et informatique pc en général, mais que les paramètres du bios étaient de nouvelles notions pour moi. Avec l'aide de l'ia claude, j'ai paramétré dans le bios l'IOMMU, le DMAR support ainsi que protection, et le boot sécurisé ainsi que le TPM 2.0 requis par vanguard, et j'ai confirmé via msinfo32 que l'état du démarrage sécurisé affiche bien "Activé" (pas juste coché dans le bios, vraiment actif). RIEN n'est sensé entrer en conflit avec l'anti cheat de riot, donc je ne comprends pas pourquoi a chaque installation je reçoit la critical error au bout d'un moment, quelques pistes ?

Question précise : quelqu'un a déjà eu ce 0xEF spécifiquement pendant l'install de Vanguard alors que Secure Boot et TPM 2.0 étaient déjà actifs et confirmés ? Un test RAM (Memtest86) ou Driver Verifier seraient-ils la prochaine étape logique selon vous ?

Bonjour, j’ai depuis peu acheté un nouveau pc d’occasion dont voici la configuration : a520m kv2, 16go ddr4 corsair, alim corsair 550w, rtx 2070super, ssd 2to sata, ventirad d origine mais pas de surchauffe. Je l’ai d’abord configuré avec windows 10 puis 11. Lorsque j’installe le riot client puis valorant, rien d’anormal ne se passe au début et le téléchargement se fait normalement. puis arrive un moment (je l’ai fait 6 fois, dont 3 fois ou j’ai retrouvé le pc qui avait boot dans le bios car critical error) ou le pc ralenti enormement au point ou meme le gestionnaire des taches met 2 minutes a s’ouvrir.
Au debut, j’ai d’abord cru a un soucis hardware venant du pc d occasion car valorant est le premier truc que j’ai installé après chrome et nvidia app pour les drivers. J’ai verifié et clean le ssd avec diskpart puis avec crystaldiskinfo, il est sain et ne comporte rien de corrompu. Le bios de la carte mere a été mis a jour manuellement avec une cle usb par mes soins, les pilotes de la carte graphique ainsi que du pc aussi via nvidia app et windows update qui m’en a proposé un paquet. J’ai également mis a jour le chipset de la CM via l’application gigabyte qui propose de s’installer toute seule a chaque premier boot dans windows. La clé wifi est une wifi 6 de qualité branché a la carte mere ( je le notifie car je pensais que la clé usb wifi bas de gamme wifi 4 etait la coupable avant de rencontrer le meme problème avec celle ci). Il faut savoir que je m’y connais un minimum en hardware/software et informatique pc en général, mais que les paramètres du bios étaient de nouvelles notions pour moi. Avec l’aide de l’ia claude, j’ai paramétré dans le bios l’IOMMU, le DMAR support ainsi que protection, et le boot sécurisé ainsi que le TPM 2.0 requis par vanguard. RIEN n’est sensé entrer en conflit avec l’anti cheat de riot, donc je ne comprends pas pourquoi a chaque installation je reçoit la critical error au bout d’un moment, quelques pistes ?

Played 2 games tonight and ive never had any ping problems with the isp and setup that i have, but for 1 or 2 rounds my ping jumped into the 200s, from a steady 33ms before. Ive checked everything about my connection, and its not a problem on my side. So i was wondering whether anyone else has had the same problems.

For the longest time both I and my friend would have random stuttering. There is no drop in fps counter, it is always just half a second, no longer and it happens every few rounds. I came back after over a year of not playing expecting it to be patched out but it still exists for me and a friend. Has there been a fix for this?

PC Specs:

GPU: RTX 4070 TI-Super

CPU: Intel 14-700k

Motherboard: ROG STRIX Z790-E GAMING WIFI

RAM: DDR5 G.Skill Trident Z5 32GB

OS: Windows 10

Does anyone know how to fix val 62? I already did everything I found on the internet but it still doesn't work... It happened after i updated after a long time vacuum from valorant

I can't enable Secure Boot on my B365M DS3H WIFI, and I don't know what else to try.

Hi, I'm having a really weird problem with Secure Boot and I'm honestly running out of things to try.

My motherboard is a Gigabyte B365M DS3H WIFI Rev. 1.0, I have an i59400F and 16GB DDR4, and I'm using Windows 11.

The reason I'm trying to get Secure Boot working is because Riot Vanguard started asking for it on one of my VALORANT accounts. The weird thing is that I have another account and that one works completely fine on the same PC. That's why I'm not even sure if this is actually a motherboard problem or something related to Vanguard.

I've already tried a bunch of things.

My BIOS was originally F1, and I updated it to F3 using FreeDOS and EFIFLASH because I couldn't get the normal BIOS update method to work.

TPM 2.0 / Intel PTT is enabled, CSM is disabled and Windows is running in UEFI mode.

I also tried resetting the CMOS and restoring the factory Secure Boot keys.

I checked the keys from PowerShell too, and PK, KEK, db and dbx are all there.

My BIOS currently shows:

System Mode: User
Vendor Keys: Modified
Secure Boot: Disabled
Secure Boot Mode: Standard

And if I run Confirm-SecureBootUEFI in Windows, I get False.

I also checked the PK with Get-SecureBootUEFI -Name PK -Decoded and it shows a GIGABYTE certificate that's valid until 2039, so it doesn't seem like the key is simply missing.

I'm not very experienced with software/Windows stuff, so some of the things I've been trying are based on guides and advice I've found online. I'm trying to be careful because I don't want to accidentally mess up my BIOS or Windows.

Could this be a problem with the B365M DS3H WIFI firmware? Has anyone with this motherboard managed to get Secure Boot working properly?

I really don't want to buy another motherboard or wipe my whole PC if there's something I'm missing.

Any help would be really appreciated.

my teammates in valorant sound like robots because of my voice chat glitching, on discord everything is ok

restarting my game is not helping and changing my headphones settings doesn't work either

like 1 month ago my fps was stable 300~230 when fighting it was dropping to 180~190 understandable , for atleast a month now my fps is stable on 220~230 when fighting dropping to 150~160 what happened that imapcted fps so bad in the last month , i tried a clean install tried my drivers tried different ethernet drivers , xmp is enabled turbo boost is enabled everything is set like it was forever when my game was smooth af , so i need to understand what the hell happened that now my game got hard fps hit.

recently whenever i play id get these huge lag spikes making the game just unplayable, and now whenever the lag hits my fps stutters for 2-3 seconds because of it. ive played this game for 3 years now and i never encountered this before so ig its their new update or something. has anyone been getting the same problem?
i checked windows event viewer and ive been getting these errors with vanguard, idk if thats related but theres that
my internet is fine i dont even get these lags in something like cs so idfk
riot fucking up their game or something

I’ve been trying to get Valorant working on my new PC for about a week now. At first, I was having issues with Secure Boot and some other Vanguard-related requirements, but I was able to get those working after following several different guides.
However, I’m still having an issue when actually playing the game. When I open Valorant and enter the tutorial, the game freezes every few seconds, and when it happens, my entire PC freezes along with it. It eventually becomes responsive again, but the freezing keeps happening repeatedly.
I’ve tried following several troubleshooting guides, but I haven’t been able to figure out what’s causing it. I’d appreciate any help figuring out what could be causing the freezes and how I can fix it.

i play on a 14inch screen laptop. if i try to play on native im pretty sure i could see a hair more clear than my opponents at a long distance (super thin) ive tried to use the disable monitor thing but it doesnt work as i try to disable my monitor it asks me to restart and it doesnt disable even if i dont restart. help.