Persistent BSOD (BEDaisy.sys) – BattleEye Crash on New High-End Setup

Community Technical Support
1

Hello,

I’m experiencing repeated BSODs caused by BEDaisy.sys while running War Thunder since upgrading to a new PC build.

Crash Info:

Bug Check Code: 0x000000BE (ATTEMPTED_WRITE_TO_READONLY_MEMORY)

Faulting Driver: BEDaisy.sys +290003

System Crashes after launching the game or a few hours into gameplay

System Specifications:

CPU: Intel Core i9-14900KF (24 cores, 32 threads @ 3.2GHz)

GPU: Nvidia RTX 4070

RAM: 64 GB Corsair DDR5

OS: Tested on both Windows 11 (clean install) and Windows 10 – no difference

Storage: OS and War Thunder are installed on two separate NVMe SSDs

What I’ve tried (with no success):

Ran DISM /Online /Cleanup-Image /RestoreHealth → no corruption detected

All drivers, firmware, and BIOS are up to date

VT-d & Resizable BAR disabled in BIOS

Hyper-Threading disabled

XMP profile disabled, RAM running at base frequency

Full reinstall of BattleEye (manual deletion of all related folders)

Clean boot (no background apps, no overlays)

Minimal setup: only mouse, keyboard, and headset connected

MemTest86 → No errors

Additional Notes:

The crash consistently points to BEDaisy.sys, indicating an issue with BattleEye’s interaction with my hardware or OS.

No overclocking is applied.

No third-party antivirus or security software running (only Windows Defender, with BattleEye excluded).

If any War Thunder dev or BattleEye representative can provide insight or debugging steps, I’d really appreciate it.
I can provide .dmp files or full system reports if needed.

Thanks in advance for your help.

Capture_decran_2025-05-20_201857
Capture_decran_2025-05-20_2018572537×1250 163 KB

Capture_decran_2025-05-20_201307
sddefault
image
Capture_decran_2025-05-20_201034

1 Like
2

Try resetting the BIOS. You’ll have to look up how to do it for your exact motherboard but usually if you have a CMOS battery on it just unplug your computer and then take out the battery for around a minute or so and then put it back in and turn on the computer. I’ve had many issues with this game that I couldn’t resolve at first but just doing that fixed them.

Looking at this Microsoft Answers thread a user says that for them the issue was being caused by a faulty CPU, if you have one spare it might be worth it to swap it over to check.

It might be worth asking Microsoft Support since just having a quick look on their forums there’s quite a few threads about BEDaisy.sys error recently.

3

same issue here