BattleEye triggers BSOD during uPlay game launches (R6:Siege/Quarantine...)
BattleEye triggers BSOD during uPlay game launches (R6:Siege/Quarantine...)
Hello All! Recently I purchased a new game from Ubisoft called Tom Clancy's Rainbow Six Quarantine. After that, I simply let it download and install using the Ubisoft launcher. Once everything was set up, I pressed play and saw a dialog from BattleEye asking for some info like IP addresses and more—clicked OK. Suddenly, a BSOD appeared with the message "Kernel Security Check Failure." I had played R6:Siege before, but it never happened. Now only the BSOD with that same message shows up. I searched online, but nothing helped. So here’s what I did:
- Ran memory diagnostics – everything normal
- Executed sfc /scannow on all drives – no issues
- Checked disk health – everything fine
- Updated Windows and GPU-related drivers – no success
- Uninstalled BattleEye via the game's uninstaller in its folder
I also managed to grab a Minidump from the crash, which indicated that BEDaisy.sys was involved. Still, I don’t know how to fix it.
KERNEL_SECURITY_CHECK_FAILURE (139) – A kernel part has damaged a vital data structure. This could let someone malicious take control of the system.
Arguments:
- 0000000000000003 – A list entry was corrupted (double removal)
- ffffe102c839f280 – Address of the trap frame for the exception causing the bug
- ffffe102c839f1d8 – Exception record for that issue
- 0000000000000000 – FailFast type
- 0000000000000000 – Debugging details
Warning: Can’t verify the checksum for win32k.sys.
Key values:
- Analysis.CPU.mSec: 4030
- Analysis.DebugAnalysisManager: Create Key with value 1
- Analysis.Elapsed.mSec: 13551
- Analysis.Init.CPU.mSec: 421
- Analysis.Init.Elapsed.mSec: 50994
- Analysis.Memory.CommitPeak.Mb: 82
Other notes:
- Reset default scope
- Exception details point to a corrupted list entry
- Stack trace shows a trap frame but not all registers are intact
Please let me know if you need more help. Thanks!
BEDaisy.sys is associated with BattleEye, a game anti-cheat tool. Possible fixes include removing the BattleEye folder from your game installation directory and checking Steam for valid game files. Reinstalling BattleEye may resolve the problem. Ensure no conflicting antivirus programs like AVG are active. Turn off overclocking or hardware monitoring features that could interfere. Use System File Checker to detect and repair corrupted system files on your computer.
This thread remains unresolved after three years. I’ve faced similar BSOD issues, usually linked to Battle Eye and hardware drivers. For me: -Focusrite Scarlett 4i4 3rd gen works; for others: any Scarlett model plus ASIO devices -Fanatec Direct Drive Racing Wheels -certain wireless laptop adapters -some graphical drivers. If you own any of these, they might be causing the problem. I’ve shared a complete breakdown with Battle Eye, Focusrite, Rockstar, Gaijin, and Reddit, but no fixes have appeared. Hopefully, your setup is working fine. Did some last-minute testing? It’s not ASIO—it’s MIDI, and Battle Eye doesn’t handle it well in my case. Analysis and links.txt are attached.
I was browsing that discussion last week trying to find solutions for the same problem. Focusing on your point about the Focusrite MIDI drivers and Battle Eye, I tested a modification myself and it seems to have fixed the issue. It probably wasn’t just the MIDI drivers, though I might be mistaken about that. Here are the details:
- Device used: Focusrite Scarlett 4i4 4th Gen
- Game causing crashes: Destiny 2 on Steam
- BSOD trigger: Running Adobe Audition while the game was active
- What I did to resolve:
• Removed Focusrite Control 2 (not in use)
• Deleted all other audio drivers except Focusrite and Realtek
• Deleted Focusrite MIDI drivers (refer to Screenshot_1.png for files/locations)
- Extended steps: I went further than necessary, but if it helps others, I included them.
- Minidump reference: The files I analyzed (including Tris The’s .dmp’s) look similar; the attached file shows the stack.
I don’t think my symbol setup was correct, so this might not be perfect for others.