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

4

Same here. Tried wiping all HDD:s and windows, but after fresh install I got BSOD within minutes.

5

13 or 14h gen of cpu ?

6

Intel i9 13900 KF

7
1 Like
8

@FR_SUKHOI Double check that your RAM is seated properly. Ensure XMP is enabled. Additionally, look in BIOS for your RAM frequency and ensure it is set properly. If that doesn’t work, drop ~100Mhz off your freq (Ex. if 6400Mhz set to 6300Mhz and so on)

9

Voici comment tu peux répondre clairement et poliment en anglais, en expliquant que le problème ne vient pas de la RAM mais du processeur :

Thanks for the suggestion! 😊

I actually double-checked all RAM-related settings:

RAM is properly seated XMP is enabled Frequency is correctly set according to specs

However, the issue was not RAM-related. The real cause turned out to be the CPU — specifically, the high stock or overclocked frequency on Intel 13th/14th gen processors.

BattleEye (bedaisy.sys) seems to crash when the CPU runs at max boost clocks like 5.7 GHz. After lowering the frequency to 4.7 GHz and disabling features like Hyper-Threading, DMB, RMF, and SA GV in the BIOS, the game became completely stable with no more BSODs.

So in this case, it’s definitely a CPU issue — probably related to how BattleEye interacts with kernel-level hardware drivers under high load or tight timing.

1 Like
10

Not sure if this will work for everyone, but I noticed after you press play in the WarThunder launcher, BattlEye’s own launcher starts up and checks for updates. Previously I had tried everything to try and fix the problem, BIOS update, turning off OC settings, even a reset. What worked for me was I deleted everything involved with battle eye off my drive, then ran the launcher as Administrator. DO NOT VERIFY THE FILES! Press Play and let the Battle Eye launcher do its thing, it should install, update and launch the game. It seems the Gajin files may not be up to date with the BE launcher. Don’t know if this will work for steam but worth a try.

11

That is dangerously idiotic advice. Telling someone with an i9-14900K to reset their BIOS to factory defaults shows you either don’t understand this CPU or aren’t aware of the massive hardware failure scandal surrounding it. I know because I already changed my i9-14900k.
The i9-14900K is notorious for physical degradation due to high voltage. Intel and motherboard manufacturers specifically released the 0x12B microcode and ‘Intel Default’ profiles to stop these CPUs from literally frying themselves with 1.55V+ spikes. By resetting the BIOS, you are removing those essential safety ‘brakes’ and putting a $600 processorat immediate risk of permanent hardware death.
Furthermore, a CMOS reset won’t fix a 0xBE (BEDaisy.sys) kernel panic. This is a coding conflict between BattlEye and Windows memory protection, not a ‘bad setting’ in the BIOS.

Please stop giving dumb advice that can result in someone’s hardware being destroyed. If you don’t know the specifics of the 14th Gen voltage issues, you shouldn’t be telling people how to configure their motherboards.

12

To all of you experiencing these BattlEye crashes:

Stop looking for a “fix” in your own settings. This is strictly a BattlEye problem, not a hardware one.
I have spent hundreds of hours—and many late nights researching until I was exhausted—reading forums that prove BattlEye is failing not just in War Thunder, but in multiple other games. I’ve seen reports from users with AMD CPUs, mid-range builds, and even those still on Windows 10 experiencing the exact same 0xBE kernel panic.
The irony is that Gaijin replaced their old system with an anti-cheat so poorly coded that it treats legitimate Windows memory security as a threat, blocking honest players while actual cheaters continue to play. Gaijin is mostly banning those cheaters because of manual player reports, not because BattlEye is actually doing its job.
We are being punished for having modern, secure systems while a broken driver fails to catch the very people it was meant to stop. This isn’t a “you” problem; it’s a Gaijin and BattlEye failure. Stop wasting your time with “Clean Boots” and “BIOS resets”—the fix has to come from their side, not ours.

Here is the proof that other games have same problem with Battleye.