BattlEye Crash Report

Community Technical Support
1

I am writing to report a recurring Blue Screen of Death (BSOD) that is consistently caused by the BattlEye kernel driver (BEDaisy.sys). I have exhausted all user-side troubleshooting steps without success, so I am submitting this report together with the crash dump files for your investigation.

1. System Information

  • Operating System: Windows 11 24H2 (x64), Build 10.0.26100.8457

  • Note on OS Name: WinDbg labels this as “Windows 10” in legacy fields because Microsoft has locked the kernel major version to 10.0 since Windows 10. However, build 26100 definitively identifies this system as Windows 11 24H2 (or Windows Server 2025).

  • BIOS Revision: 5.27.0.0

  • Game: War Thunder (Steam version, executable aces.exe)

  • BattlEye Driver Path: Z:\SteamLibrary\steamapps\common\War Thunder\BattlEye\BEDaisy.sys

2. Crash Details

  • Bug Check Code: 0xBE (ATTEMPTED_WRITE_TO_READONLY_MEMORY)

  • Faulting Module: BEDaisy.sys (base + 0x343926)

  • Attempted Write Address: fffff80052cf8da9

  • PTE Contents: 09000006fbb78121 (page marked Read-Only / Execute)

  • Process at Time of Crash: aces.exe

  • Dump File: 062726-11156-01.dmp (Kernel Generated Triage Dump)

3. Key Stack Trace

plain

复制

nt!KeBugCheckEx
nt!MiSystemFault
nt!MmAccessFault
nt!KiPageFault
BEDaisy+0x343926

The crash is reproducible and always points to BEDaisy+0x343926 attempting to write to a memory page that is marked read-only by the system page tables.

4. Troubleshooting Already Performed

  • Completely deleted the BattlEye folder and reinstalled the component via Steam’s “Verify Integrity of Game Files” function.

  • Disabled Memory Integrity (HVCI) under Windows Security → Core Isolation.

  • Performed a Windows Clean Boot with all non-Microsoft services disabled.

  • Confirmed that no other anti-cheat software (e.g., Riot Vanguard, Easy Anti-Cheat, PunkBuster) is running concurrently.

  • Verified hardware stability: CPU and RAM are running at stock frequencies; XMP / EXPO is disabled; no memory overclocking is applied.

5. Additional Analysis The crash occurs during BattlEye execution. The faulting instruction at BEDaisy+0x343926 attempts to write to a kernel address whose PTE attributes are strictly read-only/execute. This suggests either:

  • A logic error within the driver’s memory protection or hooking routines, or

  • A compatibility issue between the current build of BEDaisy.sys and Windows 11 24H2 (Build 26100).

Given that the issue persists after a clean reinstall of BattlEye and with HVCI disabled, this appears to be a driver-level compatibility defect rather than a user-configuration problem.

6. Attachments

  • 062726-11156-01.dmp (and other related minidumps from C:\Windows\Minidump\)

  • A full MEMORY.DMP or an msinfo32 system information export can be provided upon request.

Please let me know if this is a known issue with Windows 11 24H2 Build 26100. I am happy to provide any additional logs or diagnostic data you may need.