ON THIS PAGE
The quick answer
Investigate the crash without weakening security.
If the blue screen references vgk.sys, collect the stop code and crash timestamp, install Windows and device-driver updates, and test whether another monitoring/overlay driver is involved. A module name in a dump is not proof that the module caused the crash.
Jump into the guide01Keep kernel protection enabled while diagnosing
Windows Security — status check
Device Security → Core isolation. Note whether Memory Integrity or stack protection is enabled.
Crash timeline
Record the stop code, event timestamp, recent Windows updates, and whether a new driver or utility was installed.
02How to inspect a Windows minidump
Find the newest crash
Windows may save files in
C:\Windows\Minidump. Do not publish raw dumps containing personal data.Open the file with Microsoft WinDbg
Start with the built-in analysis view and review the stop code, probable cause, and loaded modules.
Compare more than one crash
Repeated reference to a particular third-party driver is a clue, but requires corroboration.
Export only relevant details to support
Send Riot the event time and diagnostic logs using their official ticket route.
03Check likely driver interactions
MSI Afterburner / RTSS
If RTCore64.sys or a monitoring utility appears, use the vendor’s official update/uninstall path. Do not delete a random .sys file in isolation.
Overlays or peripheral utilities
Temporarily exit optional overlays, recording tools, or RGB utilities; reboot and test one at a time.
- Update Windows and chipset/GPU drivers from the relevant manufacturers.
- Use Windows clean boot to identify which third-party startup component causes the conflict.
- If problems persist, repair Vanguard using Riot’s documented workflow.
Frequently asked questions
Does vgk.sys in a dump prove Vanguard caused the BSOD?
No. A stack trace may include Vanguard while the crash was triggered elsewhere. Correlate logs and repeated events.
Should I permanently turn off kernel stack protection?
No. Prefer updated compatible drivers and official support, while retaining Windows protections.
Sources & update notes
Original Walker Bex explanations. Technical guidance checked October 15, 2026; follow the current linked support instructions if they change.