Hey everyone,
I'm trying to figure out a persistent Blue Screen of Death (BSOD) issue that only happens when I launch Rainbow Six Siege. The crash seems to be linked to BattlEye, specifically the BEDaisy.sys file.
I've spent a lot of time troubleshooting this and would really appreciate any help from those familiar with Windows kernel failures or conflicts with anti-cheat drivers.
Here are my system specs:
- CPU: Ryzen 5 7600X
- GPU: ASUS GTX 1070 8GB
- Motherboard: Gigabyte B650M D3HP
- RAM: 16GB Kingston Fury Beast DDR5 5200 (2x8GB)
- Power Supply: Gigabyte Gold 850W
I'm running Windows 11 Pro, Build 26200.
The problem is that every time I try to start Rainbow Six Siege, my system freezes and then I get a BSOD.
The bug check code is: 0x139 KERNEL_SECURITY_CHECK_FAILURE, Subcode: FAST_FAIL_CORRUPT_LIST_ENTRY
WinDbg analysis consistently points to:
BEDaisy.sys (BattlEye)
Here's an example stack:
nt!KeInsertQueueApc → BEDaisy+0x7744a6
Things I've already tried:
- Updated the BIOS to the latest version
- Clean reinstall of Rainbow Six Siege
- Completely removed and reinstalled BattlEye
- Disabled Hyper-V/virtualization features
- Turned off core isolation and memory integrity
- Clean installed the GPU driver
- Updated AMD chipset drivers
- Set RAM to stock (no EXPO)
- Removed startup services and overlays
Despite all of this, the crash still occurs at the same point with BEDaisy.
I've provided a minidump link here:
[https://files.catbox.moe/lldujs.zip](https://files.catbox.moe/lldujs.zip)
Minidump info:
Error check: 0x139
Failure bucket: CORRUPT_LIST_ENTRY_BEDaisy
Driver: BEDaisy.sys
Offset: +0x7744a6
Has anyone experienced a BattlEye driver causing this specific quick failure before? Could it be triggered by another kernel driver interfering with it?
I'd greatly appreciate any ideas or suggestions on troubleshooting this issue.
Thanks in advance!
5 Answers
Make sure that your drivers, particularly the video card and chipset drivers, are completely up to date. Sometimes outdated drivers can conflict with anti-cheat software and cause BSODs like the one you're experiencing.
If none of that works, you could try running a memory diagnostic test to rule out any RAM issues. Just to be thorough. Windows has a built-in tool you can use for that.
It sounds like you've done quite a bit of troubleshooting already! To further analyze BSODs, try checking for dump files in the C:WindowsMinidump folder if you can access Windows. Those crash logs are essential for a deeper dive into what might be causing the issue. If you find any dump files, you can zip them and upload them to a file sharing service like catbox.moe or mediafire.com. Having multiple dump files can really help pinpoint the cause better. Let me know if you need help with that!
You might also want to make sure your Windows updates are all current. Occasionally, the latest patches can fix underlying issues that cause crashes, especially related to drivers like BattlEye. Just a thought!
Sometimes resetting your BIOS to its default settings can resolve odd compatibility issues. Have you tried that? It might help clear up any misconfigurations that could be causing your BSOD.
I tried resetting the BIOS, but it still gave me the 0x139 blue screen.
Thanks for the suggestion! I’ll check for dump files and get them uploaded.