Valorant Error van-37 relates to Windows' Core Isolation / Memory Integrity feature, which protects system memory from being modified by malicious code. When certain drivers are incompatible with Memory Integrity, it can also affect Vanguard's kernel operations.
Usually client-sideLast verified: 2026-08-19
Check Memory Integrity
Go to Windows Security > Device Security > Core Isolation > Core Isolation Details. If Memory Integrity shows a driver incompatibility warning, update or remove that driver. Then try re-enabling Memory Integrity and restarting.
Driver incompatibility
An incompatible driver (often an older GPU, audio, or networking driver) can trigger this conflict. Windows Security will often name the incompatible driver — update it from the manufacturer's website.
How to fix step by step
- 1Go to Windows Security > Device Security > Core Isolation Details and check for incompatible drivers
- 2Update the driver listed as incompatible via Device Manager or the manufacturer's website
- 3Restart your PC after updating the driver
- 4If Memory Integrity remains problematic, temporarily disable it, launch Valorant, then consider re-enabling after verifying driver compatibility
How VAN-37 differs from related codes
- Error VAN-81: Valorant lost connection to Riot services during login or queue. (server or client)
- Error VAN-51: Riot Vanguard detected a conflicting application or driver that interferes with its kernel-level anti-cheat protection. Vanguard blocked Valorant's launch as a result. (usually client-side)
- Error VAN-33: The Riot Vanguard anti-cheat service failed to start or initialize. Without Vanguard running, Valorant cannot launch. (usually client-side)