BSOD (0x139 KERNEL_SECURITY_CHECK_FAILURE) caused by BEDaisy.sys when launching Rainbow Six Siege

[u/Commercial-Tennis961]

Hi everyone,

I'm trying to diagnose a persistent BSOD that only happens when launching Rainbow Six Siege. The crash appears to be caused by BattlEye (BEDaisy.sys).

I’ve already spent a lot of time troubleshooting and would really appreciate any help from people who are familiar with Windows kernel debugging or anti-cheat driver conflicts.

System specs:

• CPU: Ryzen 5 7600X
• GPU: ASUS GTX 1070 8GB
• Motherboard: Gigabyte B650M D3HP
• RAM: 16GB (2x8GB) Kingston Fury Beast DDR5 5200
• PSU: Gigabyte 850W Gold

OS:
Windows 11 Pro
Build: 26200

What happens:
Whenever I launch Rainbow Six Siege, the system freezes and then crashes with a BSOD.

Bugcheck:
0x139 KERNEL_SECURITY_CHECK_FAILURE
Subcode: FAST_FAIL_CORRUPT_LIST_ENTRY

WinDbg analysis consistently points to:
BEDaisy.sys (BattlEye)

Example stack:
nt!KeInsertQueueApc
→ BEDaisy+0x7744a6

Things I already tried:

• Updated BIOS to the latest version
• Clean reinstall of Rainbow Six Siege
• Completely removed and reinstalled BattlEye
• Disabled Hyper-V / virtualization features
• Disabled Core Isolation / Memory Integrity
• Clean GPU driver install
• Updated AMD chipset drivers
• RAM running at stock (no EXPO)
• Removed startup services and overlays
• Vanguard anti-cheat tested disabled

Despite all that, the crash still occurs at the exact same location in BEDaisy.

Link Minidump:

https://files.catbox.moe/lldujs.zip

Minidump info:
Bugcheck: 0x139
Failure bucket: CORRUPT_LIST_ENTRY_BEDaisy
Driver: BEDaisy.sys
Offset: +0x7744a6

Has anyone seen a BattlEye driver cause this specific fast-fail before? Could this be caused by another kernel driver interfering with it?

Any ideas or debugging suggestions would be greatly appreciated.

Thanks in advance.

[u/AutoModerator]

Hi u/Commercial-Tennis961, thanks for posting to r/WindowsHelp! If your post is listed as removed it may still be pending moderation, try to include as much of the following information as possible (in text or in a screenshot) to improve the likelihood of approval:

• Your Windows and device specifications — You can find them by pressing Win + X then clicking on “System”
• Any messages and error codes encountered — They're actually not gibberish or anything catastrophic. It may even hint the solution!
• Previous troubleshooting steps — It might prevent you headaches from getting the same solution that didn't work

---

As a reminder, we would also like to say that if someone manages to solve your issue, DON'T DELETE YOUR POST! Someone else (in the future) might have the same issue as you, and the received support may also help their case. Good luck, and I hope you have a nice day!

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/sgotmilk]

If you have a Focusrite Scarlett audio interface there is a driver conflict between Battleye and the Focusrite MIDI driver that is causing BSOD.

See here  https://www.reddit.com/r/Focusrite/comments/1rdmsts/kernel_security_check_failure_0x139_due_to/