bsod fest while i'm doing random stuff after playing valo. Every single instance involved vgk.sys
kmode_exception_not handed, clock watchdog timeout, there was one more error too i can't rember the exact phrase but they all had vgk.sys involved. The crash happens literally anytime vanguard is running, if i'm playing terraria, using google, or getting into a match of valorant. it has literally rendered my pc unusable, as I have to exit vanguard before i do anything important in fear my pc might crash (this might be confirmation bias but pc hasn't crashed while vanguard was turned off)
5 Replies
I'm sorry to hear about the BSOD issues involving vgk.sys, which is related to Riot Vanguard, the anti-cheat system for VALORANT. Here’s what you can do to potentially resolve the problem:
1. Update System Drivers: Make sure all your drivers (especially GPU and chipset) are up to date.
2. Reinstall Riot Vanguard: Uninstall Riot Vanguard via the Control Panel or Riot Client, then relaunch VALORANT to reinstall Vanguard.
3. Check for Windows Updates: Ensure that your Windows OS is fully updated.
4. Scan for Corrupt Files:
- Open Command Prompt as an administrator.
- Run
sfc /scannow and chkdsk /f.
5. Check for Conflicting Software: Ensure no background software conflicts with Vanguard. This includes any other anti-cheat programs or monitoring software.
6. Memory and Hardware Check: Run a Memory Diagnostic Test (Windows Memory Diagnostic) and check if your RAM or other hardware components are functioning properly.
7. Disable Overclocking: If you have overclocked your hardware, try reverting to default settings.
If the issue persists, consider submitting a support ticket to Riot for personalized assistance.
I am an AI and I can make mistakes, please verify my answer. If my response solved your issue or answered your question please right click this message -> Apps -> ✅ Mark Solution. Thank you!ran sfc /scannow and it did find some corrupted files and repaired them, ran it again and it returned 'no integrity violation'
hardware is not overclocked, at least I haven't enabled overclocking to my knowledge
Did you run the memory diagnostic?
yeah did mem test
says no problem found
disk is 99% health
for background i dualboot on this pc with arch linux
is that prolly why this is happening?
Did anyone find a fix for this or what the pattern is for people getting this issue is?