Battle Eye causing BSOD

Question

While playing War Thunder Battle Eye has started crashing my computer and gotten progressively worse over the last couple weeks. Now the game won't run for more than a couple minutes before crashing. What should I be looking for to figure out the issue?

I have done the basic memory and file tests. All are returning no issues.

I am on a laptop, have owned it for about two years so I ordered a new battery just in case that is it but the system is telling me the battery is healthy.

I have reinstalled windows updates, GPU and CPU drivers.

Here is the dump file:

ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)

An attempt was made to write to readonly memory. The guilty driver is on the

stack trace (and is typically the current instruction pointer).

When possible, the guilty driver's name (Unicode string) is printed on

the BugCheck screen and saved in KiBugCheckDriver.

Arguments:

Arg1: fffff8005d948e8b, Virtual address for the attempted write.

Arg2: 0900000820378121, PTE contents.

Arg3: fffff983659af160, (reserved)

Arg4: 000000000000000b, (reserved)

Debugging Details:

---

*** WARNING: Unable to verify timestamp for BEDaisy.sys

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec

Value: 2281

Key  : Analysis.Elapsed.mSec

Value: 4774

Key  : Analysis.IO.Other.Mb

Value: 0

Key  : Analysis.IO.Read.Mb

Value: 1

Key  : Analysis.IO.Write.Mb

Value: 0

Key  : Analysis.Init.CPU.mSec

Value: 500

Key  : Analysis.Init.Elapsed.mSec

Value: 10240

Key  : Analysis.Memory.CommitPeak.Mb

Value: 87

Key  : Analysis.Version.DbgEng

Value: 10.0.29507.1001

Key  : Analysis.Version.Description

Value: 10.2511.5.1 amd64fre

Key  : Analysis.Version.Ext

Value: 1.2511.5.1

Key  : Bugcheck.Code.LegacyAPI

Value: 0xbe

Key  : Bugcheck.Code.TargetModel

Value: 0xbe

Key  : Dump.Attributes.AsUlong

Value: 0x21008

Key  : Dump.Attributes.DiagDataWrittenToHeader

Value: 1

Key  : Dump.Attributes.ErrorCode

Value: 0x0

Key  : Dump.Attributes.KernelGeneratedTriageDump

Value: 1

Key  : Dump.Attributes.LastLine

Value: Dump completed successfully.

Key  : Dump.Attributes.ProgressPercentage

Value: 0

Key  : Failure.Bucket

Value: AV_BEDaisy!unknown_function

Key  : Failure.Hash

Value: {36b04c21-521f-babb-382f-2a12c3ddef17}

Key  : WER.System.BIOSRevision

Value: 5.27.0.0

BUGCHECK_CODE: be

BUGCHECK_P1: fffff8005d948e8b

BUGCHECK_P2: 900000820378121

BUGCHECK_P3: fffff983659af160

BUGCHECK_P4: b

FILE_IN_CAB: 020726-14140-01.dmp

DUMP_FILE_ATTRIBUTES: 0x21008

Kernel Generated Triage Dump

FAULTING_THREAD: ffff8509eb9eb040

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1 (!blackboxwinlogon)

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: aces.exe

STACK_TEXT:

fffff983659aeef8 fffff800a4540250 : 00000000000000be fffff8005d948e8b 0900000820378121 fffff983659af160 : nt!KeBugCheckEx

fffff983659aef00 fffff800a452d356 : fffff983659af070 ffff800000000000 fffff8005d948e8b 0000007ffffffff8 : nt!MiSystemFault+0x6b0

fffff983659aeff0 fffff800a48b12cb : 000000375e11e0b2 fffff983659af1e0 0000000028600410 00003451637e4842 : nt!MmAccessFault+0x646

fffff983659af160 fffff8005db13926 : 0000000140178e16 0000000000040287 fffff8005d9d2c21 00000000fffffe5c : nt!KiPageFault+0x38b

fffff983659af2f0 0000000140178e16 : 0000000000040287 fffff8005d9d2c21 00000000fffffe5c 66bf3fa0feb314c6 : BEDaisy+0x343926

fffff983659af2f8 0000000000040287 : fffff8005d9d2c21 00000000fffffe5c 66bf3fa0feb314c6 000000000000005c : 0x00000001`40178e16

fffff983659af300 fffff8005d9d2c21 : 00000000fffffe5c 66bf3fa0feb314c6 000000000000005c ffffffffffff0000 : 0x40287

fffff983659af308 00000000fffffe5c : 66bf3fa0feb314c6 000000000000005c ffffffffffff0000 0000000000000001 : BEDaisy+0x202c21

fffff983659af310 66bf3fa0feb314c6 : 000000000000005c ffffffffffff0000 0000000000000001 0000000000000000 : 0xfffffe5c

fffff983659af318 000000000000005c : ffffffffffff0000 0000000000000001 0000000000000000 0000000000000001 : 0x66bf3fa0`feb314c6

fffff983659af320 ffffffffffff0000 : 0000000000000001 0000000000000000 0000000000000001 000000000000005c : 0x5c

fffff983659af328 0000000000000001 : 0000000000000000 0000000000000001 000000000000005c 0000067e456da6c8 : 0xffffffff`ffff0000

fffff983659af330 0000000000000000 : 0000000000000001 000000000000005c 0000067e456da6c8 0000000000000000 : 0x1

SYMBOL_NAME: BEDaisy+343926

MODULE_NAME: BEDaisy

IMAGE_NAME: BEDaisy.sys

STACK_COMMAND: .process /r /p 0xffff8509c96c5040; .thread 0xffff8509eb9eb040 ; kb

BUCKET_ID_FUNC_OFFSET: 343926

FAILURE_BUCKET_ID: AV_BEDaisy!unknown_function

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {36b04c21-521f-babb-382f-2a12c3ddef17}

Followup: MachineOwner

---

I have been trying to understand it but just don't know enough about internal systems to figure it out.

Answer 1

Hi Ryan Clark

Thanks for posting in the Microsoft Q&A Forum!

I’m really sorry you’ve been dealing with these constant crashes. Issues involving BattlEye’s BEDaisy.sys driver can be especially frustrating because they often look like hardware problems even when the hardware is fine.

What your crash indicates:

Your dump shows an ATTEMPTED_WRITE_TO_READONLY_MEMORY (0xBE) fault, and the module responsible is BEDaisy.sys. This is BattlEye’s kernel‑level anti‑cheat driver. When it malfunctions, Windows stops the system to prevent further damage. This same pattern has been widely reported by players in War Thunder, GTA V, ARK, and others. It’s normally caused by a conflict between BattlEye and system drivers, BIOS settings, CPU behavior, or corrupted game/anti‑cheat files.

What you should do next:

1. Fully reinstall BattlEye
   • Go to your War Thunder BattlEye folder and run the uninstall script, then reinstall. This resolves many BSOD cases.
2. Verify your War Thunder installation
   • Use Steam’s Verify Integrity function to fix corrupted game files.
3. Update BIOS and chipset drivers
   • Multiple users have eliminated this BSOD simply by updating the BIOS to the latest manufacturer version. This is one of the highest‑success fixes.
4. Use the Windows Power Saver plan
   • Some players resolved the issue by switching to the Power Saver plan before launching the game, reducing CPU boost spikes that trigger BattlEye.
5. Temporarily disable Windows security features
   • Features such as Memory Integrity and hardware‑enforced stack protection have caused conflicts for some users. Test with them off to see if stability improves.

Hope these can help. Feel free to update here if there's any progress!

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.