Subject: Persistent BSOD (BEDaisy+0x35364) — Isolated to DayZ, Reproducible After Full OS Reinstall (BattlEye Ticket #933110)
Hello,
I'm reporting a persistent, reproducible crash that is preventing me from playing DayZ entirely. I've already opened a ticket with BattlEye support (Ticket #933110) but wanted to flag this here as well, since the crash may point to a compatibility issue between BattlEye and my specific hardware configuration that your team should be aware of.
Issue:
Recurring BSOD (Windows bugcheck 0x7E, ACCESS_VIOLATION / 0xc0000005) at the exact same instruction offset every time: BEDaisy+0x35364. This has now happened repeatedly across multiple play sessions.
Important: this issue is isolated to DayZ only. I regularly play several other demanding games on this same system with zero crashes, stuttering, or any stability issues whatsoever. The system runs flawlessly everywhere except when BattlEye/DayZ is running, which strongly points to something specific to BEDaisy.sys rather than a general hardware problem.
Additionally: I performed a full, clean reinstall of Windows on my system drive, then reinstalled DayZ completely from scratch. The exact same crash still occurs at the exact same offset. This rules out any leftover configuration, corrupted files, driver conflicts, or third-party software as the cause.
Prior troubleshooting completed (before and after the OS reinstall):
- Clean reinstall of BattlEye
- Clean GPU driver reinstall via DDU + latest NVIDIA driver
- Removed a conflicting Denuvo Anti-Cheat kernel driver (from another game, For Honor) that was also loaded at kernel level
- Disabled Killer Network software features
- Ran sfc /scannow with no unresolved corruption
- Ran a full 30-minute OCCT CPU/Memory stability test with zero errors detected
- Full OS reinstall + fresh DayZ install — crash still occurs identically
System specs:
- CPU: Intel Core i9-13950HX
- GPU: NVIDIA GeForce RTX 4070 Laptop GPU
- OS: Windows 11 Pro (fresh install)
- RAM: 32GB
Given that the issue is isolated to DayZ/BattlEye specifically, occurs at the exact same code offset every time, and persists even after a completely clean OS and game installation, this strongly suggests a bug within BattlEye's driver itself when running on this specific CPU/GPU combination, rather than a hardware fault. I have four Minidump files showing the identical crash signature, ready to share.
Could your team please look into this, or coordinate directly with BattlEye given the ticket number above? I'd appreciate any guidance, as I'm currently unable to play at all.
Thank you for your time.
Best regards