The two stop codes point most strongly to drivers or hardware, not normal app behavior.
- Stop errors are most often caused by third-party drivers, and much less often by Microsoft code.
-
KMODE_EXCEPTION_NOT_HANDLED (0x1E)can be caused by a faulty device driver, system service, hardware incompatibility, BIOS incompatibility, memory conflicts, or IRQ conflicts. -
HYPERVISOR_ERROR (0x20001)means the hypervisor encountered a fatal error.
Since the crashes also happen at the sign-in screen and while browsing, this does not look like Valorant alone. However, similar cases in the context show Valorant or Vanguard can be involved in some systems, so it is reasonable to test that path without immediately removing the game permanently.
Recommended troubleshooting path:
- Remove or disconnect any recently added hardware If any USB devices, controllers, RGB devices, storage, or other hardware were added before the crashes started, remove them and test again.
- Boot into Safe Mode If Windows is unstable, start in Safe Mode and continue the remaining checks there.
- Check Device Manager for driver problems
- Right-click Start > Device Manager.
- Look for devices with an exclamation mark.
- Right-click the affected device > Update driver.
- If that does not help, disable or uninstall the device/driver and test.
- Update Windows fully Go to Start > Settings > Windows Update > Check for updates.
- Make sure the system drive has enough free space Keep roughly 10% to 15% free space available.
- Update BIOS and hardware drivers from the PC or motherboard manufacturer
This is especially relevant for
KMODE_EXCEPTION_NOT_HANDLED, because BIOS incompatibility and faulty drivers are documented causes. - Check Event Viewer and manufacturer hardware diagnostics
For
0x1E, check System log entries in Event Viewer for device or driver errors around the crash time. Also run the hardware diagnostics provided by the system manufacturer, especially memory diagnostics. - Test the Valorant/Vanguard path without committing to permanent removal Similar cases show Valorant or Vanguard can trigger crashes on some systems. A practical test is to temporarily uninstall Vanguard/Valorant, confirm whether the BSODs stop, then reinstall and retest. This is the fastest way to confirm whether it is a contributing factor while still keeping the game as an option.
- If a driver name appears on the blue screen, target that driver first
For
0x1E, if a driver is named in the bug check message, disable or remove that driver and get an updated version from the manufacturer. - If the issue continues, use System Restore or recovery options If the crashes started recently and the earlier steps do not help, restore Windows using a restore point or another recovery option.
If advanced analysis is needed, Windows can write memory dump files for debugging, and those can be analyzed with debugger tools.