Over the last few weeks, I’ve been getting more and more BSODs during gameplay. As of today, I can no longer go longer than 1 match of Ground Battles without suffering a BSOD. The error message is entirely consistent:
ATTEMPT_TO_WRITE_READONLY_MEMORY
In Windows Debug, it always points to BEDaisy.sys as the culprit.
One thing I suspect is it due to my laptop utilizing an Intel i9-14900HX CPU, which has a record of being faulty, however if this were the case I’d expect to be crashing throughout the entire game. Instead I am only receiving crashes when playing Ground Battles, in the Ground Vehicle Hangar, or Test Driving with Ground Vehicles. Air and Naval game modes and Hangars seem entirely unaffected. (for now)
I have run various tests- Windows Memory Diagnostic, memtest, OCCT Extreme, Scan File Checker (SFC) and DISM. None of them resulted in any issues with RAM or CPU.
I do not have a custom hangar or anything, and the BSOD occurs even with vehicles and lineups that contain no custom skins or decals.
Laptop specifications:
Nvidia RTX 4090 Laptop GPU
32GB DDR5 RAM
4TB NVMe SSD (2x 2TB SSDs)
Intel i9-14900HX CPU
Windows 11 24H2 OS
Windbg analysis of last BSOD: ******************************************************************************* - Pastebin.com
I already tried Community Bug Reports, but the ticket was already canned and blamed on my hardware/drivers, which I’ve already tested and work for literally everything else. It is just War Thunder and whatever is going on with BattleEye.
Bug Report Ticket: Community Bug Reporting System
( https://support.gaijin.net/hc/en-us/articles/21638218281362-BattlEye-anti-cheat-troubleshooting#h_01J90RX2YM0JBQGN5E1VJCTYN2 )
You can write to support to get help with those types of issues, the bug reporting site is for bugs within the game itself, Support is for other technical issues (like crashes/stuttering etc). You can find support and instructions on how to contact them here: https://support.gaijin.net/hc/en-us/articles/360000262858-How-to-submit-a-support-request
If support can’t help you then i recommend contacting the Battleye support after that.
Are you using Avast as antivirus? Try to uninstall it.
Hey so I had this same issue. I went into the files and went to the properties of the BELauncher config settings file. I right clicked and checked the properties of the file, and it was checked as read only in the General tab. After unchecking this and then going to security and giving every user listed there full control.
Another thing that may have contributed. The Xbox PC version of the game has the Uninstall BattleEye file. I ran that as well after the above mentioned.
So just to trace the steps that worked for me.
- Check if the BELauncher config files are checked as read only in properties general
- Give BELauncher Full Control in all profiles.
- Install the Xbox version of the game (if your version doesn’t have ethe Uninstall BattleEye File) and run that.
- Run the game and cross your fingers
Hope this helps!
1 Like
Man, you are 100% right, you are not alone, and you are being hit by a textbook case of corporate denial. Do not let Gaijin Support convince you that your i9-14900HX is dead. The fact that your machine passes OCCT Extreme, memtest, and DISM with zero errors proves your hardware integrity is solid. If it were a hardware degradation issue, your system would trigger a blue screen under the massive multi-threaded loads of OCCT, or while playing other heavy titles. Instead, it only happens when BattlEye tries to access protected memory regions during War Thunder ground assets loading.
Here is the harsh reality Gaijin doesn’t want you to look at:
- The Cross-Game Epidemic
Gaijin love to claim this is a ‘local hardware/driver issue,’ but BEDaisy.sys is currently causing the exact same ATTEMPTED_WRITE_TO_READONLY_MEMORY (0xBE) and PAGE_FAULT_IN_NONPAGED_AREA (0x50) kernel crashes across the entire industry. It doesn’t matter if it’s Intel or AMD.
Look at what is happening outside of War Thunder right now:
- Grand Theft Auto V (Enhanced): Players are getting instant BSODs on launch, traced directly to the BattlEye driver.
- Escape from Tarkov & Rainbow Six Siege: Months of community complaints detailing the exact same
0x50 and 0xBE errors caused by BEDaisy.sys.
- Albion Online: Giving players
KERNEL_SECURITY_CHECK_FAILURE the second the launcher triggers BattlEye.
- Even BattlEye’s Own FAQ: They explicitly acknowledge that their driver can cause immediate system blue screens upon launching games.
- The “Technical Neutering” Script
When you open a ticket, Gaijin Support follows a copy-paste protocol designed to shift liability away from their software. They will tell you to downclock your high-end CPU, disable core Windows security layers, or delete your peripheral software (like Logitech or Razer). They are literally asking you to neuter your premium PC to hide the fact that their mandatory anti-cheat driver doesn’t respect Windows memory protections.
- The April 30th PR Smoke Screen
Just days ago, on April 30, 2026, Gaijin published an article titled ‘Clarifying the Facts’ to pose as the guardians of fair play. In it, they admitted they still rely on manual player reports to catch cheaters. Think about the sheer technical impotence of that: they force a highly intrusive, kernel-level driver onto your operating system that destabilizes your entire PC environment, yet they still need human eyes to police the game.
Your ticket was canned because admitting your hardware is fine means admitting their software is fundamentally non-conforming. You’ve done the forensics, you have the WinDbg logs, and you have the hardware certificates. Keep that Pastebin link safe—the data doesn’t lie, even if Gaijin support does.
You’re talking about a Battleye issue, not a War Thunder issue.
Try this:
(
Source )
If that doesn’t work then contact the BE support: ( BattlEye – The Anti-Cheat Gold Standard » Contact )
