How to fix RICOCHET BSOD and hard PC resets in Call of Duty
This means RICOCHET's kernel-level driver is hitting a stability conflict with Windows security, drivers or memory. Removing the conflict stops the crashes. Jump to your situation below or work through the methods in order.
By Neeraj Singh ~6 min Updated Jun 2026 83% found this helpful
Error message
Blue Screen of Death or hard reset when launching Call of Duty (RICOCHET driver).
Summary
Blue screens and hard PC resets when launching Call of Duty usually trace to RICOCHET's kernel-level driver hitting a stability conflict with Windows security features, graphics or chipset drivers, or an unstable memory overclock. Because RICOCHET loads at the kernel level, small instabilities that a normal app would tolerate can trigger a full crash. The most effective first step is to disable Hardware-enforced Stack Protection in Windows Security (Device Security, Core Isolation), which is a known trigger for the RICOCHET driver crash on some systems. Then update your GPU and chipset drivers to current versions, and stabilise your RAM by testing with XMP or EXPO disabled, since an aggressive memory profile is a frequent cause of Call of Duty blue screens. Keeping your BIOS updated and adding the Call of Duty folder to your antivirus exceptions so it does not fight the kernel driver rounds out the fix.
What this error means
RICOCHET runs a kernel-mode driver, so it interacts directly with low-level Windows security and hardware. A blue screen or hard reset on launch means that driver is conflicting with a Windows security feature, another driver, or an unstable overclock, rather than a normal game bug.
Removing the conflict fixes it: disable Hardware-enforced Stack Protection, update GPU and chipset drivers, and test with memory overclocking off. An updated BIOS and antivirus exceptions for Call of Duty prevent the driver being destabilised or blocked.
Common causes
Hardware-enforced Stack Protection conflicts with the RICOCHET driver.
Outdated or mismatched GPU or chipset drivers.
An unstable RAM overclock (XMP or EXPO).
Antivirus interfering with the kernel-level anti-cheat.
Expert insight
“A kernel anti-cheat blue-screening a PC is almost always a conflict, not the game being broken. The one that catches people out is Hardware-enforced Stack Protection, turning it off in Core Isolation stops the RICOCHET driver crash on a lot of rigs. After that I update GPU and chipset drivers, and I always test with XMP or EXPO disabled, because an aggressive memory profile throws blue screens under a heavy kernel load. Update the BIOS, exclude the Call of Duty folder in your antivirus so it is not fighting the driver, and it settles down.”
Manager, Tech Support & Operations · 19+ years fixing Windows and system errors
✓ How to fix it
Method 1
Disable Hardware-enforced Stack Protection
1Open Windows Security, Device Security, Core Isolation.
2Turn off Kernel-mode Hardware-enforced Stack Protection, a known RICOCHET crash trigger.
3Restart and test.
Method 2
Update GPU and chipset drivers
1Install the latest graphics drivers (NVIDIA or AMD) and your motherboard chipset drivers.
2A clean GPU driver install helps if crashes began after an update.
3Restart and launch the game.
Method 3
Stabilise RAM (disable XMP / EXPO)
1In BIOS, disable XMP or EXPO to run RAM at stock speed and test.
2An unstable memory overclock is a common cause of Call of Duty blue screens.
3If stable, re-apply a milder profile or update the BIOS.
Method 4
Update BIOS and add antivirus exceptions
1Update the motherboard BIOS to the latest version.
2Add the Call of Duty install folder to your antivirus exceptions so it does not block the RICOCHET driver.
3Relaunch.
RICOCHET BSOD and hard resets are a kernel-driver conflict. Disable Hardware-enforced Stack Protection in Core Isolation, update GPU and chipset drivers, and test with XMP or EXPO disabled. Update the BIOS and add the Call of Duty folder to antivirus exceptions.
Frequently asked questions
Why does Call of Duty blue screen with RICOCHET?
RICOCHET loads a kernel-level driver, so a conflict with a Windows security feature, another driver, or an unstable memory overclock can cause a full blue screen or hard reset on launch rather than a normal crash.
How do I stop the RICOCHET BSOD?
Disable Hardware-enforced Stack Protection in Windows Security Core Isolation, update your GPU and chipset drivers, and test with XMP or EXPO disabled. Update the BIOS and add Call of Duty to antivirus exceptions.
What is Hardware-enforced Stack Protection?
It is a Core Isolation security feature that protects the kernel stack. On some systems it conflicts with the RICOCHET driver and causes blue screens, so turning it off in Device Security resolves the crash.
Could my RAM overclock cause it?
Yes. An aggressive XMP or EXPO memory profile is a common cause of Call of Duty blue screens, especially under a kernel-level anti-cheat. Disable it to test at stock speed, then apply a milder profile if needed.
Should I disable my antivirus?
Do not disable it, but add the Call of Duty install folder to its exceptions. Overly strict antivirus can interfere with RICOCHET's kernel driver and contribute to instability or crashes.
Hard reset with no blue screen, is it the same fix?
Often yes. A hard reset with no BSOD usually points to a power or memory stability issue, so test with XMP or EXPO off, update the BIOS, and check your power supply before anything else.
Still not working?
If crashes continue after disabling Stack Protection and stabilising memory, capture the minidump and check which driver is named; a clean reinstall of that driver, or of RICOCHET via a game repair, usually clears the last conflict. You can also submit your error to us for a tailored fix.
