I updated my BIOS several days ago (no longer than a week) with the new ROG BIOS. My verifier is also closed. But unfortunately, it does not work.
The image above implies that the verifier is closed.
I truly believe the root cause for this problem is the implementation logic inside the BattleEye.
I reproduce the error-causing code.
BEDaisy+0x5442eb:
fffff801`936342eb 4431840400dd3e98 xor dword ptr [rsp+rax-67C12300h],r8d
fffff801`936342f3 410fbed9 movsx ebx,r9b
fffff801`936342f7 4a8d8c4932d3b915 lea rcx,[rcx+r9*2+15B9D332h]
fffff801`936342ff 80c916 or cl,16h
fffff801`93634302 5b pop rbx
fffff801`93634303 4981c914929c0e or r9,0E9C9214h
fffff801`9363430a ffcd dec ebp
fffff801`9363430c 0c9b or al,9Bh
fffff801`9363430e 4d63c0 movsxd r8,r8d
fffff801`93634311 4d13d8 adc r11,r8
fffff801`93634314 4c8b843de5f6c1dc mov r8,qword ptr [rbp+rdi-233E091Bh]
fffff801`9363431c 668bb42fedf6c1dc mov si,word ptr [rdi+rbp-233E0913h]
fffff801`93634324 488dbc386fdc3e98 lea rdi,[rax+rdi-67C12391h]
fffff801`9363432c c0f863 sar al,63h
fffff801`9363432f 660fabd1 bts cx,dx
fffff801`93634333 36664289b4000ddc3e98 mov word ptr ss:[rax+r8-67C123F3h],si
From what I see from reverse engineering, there are several problems in the code.
Unsafe Memory Access:
xor dword ptr [rsp+rax-67C12300h], r8d ; High-risk stack write with unvalidated offset.
mov r8, qword ptr [rbp+rdi-233E091Bh] ; Potential dereference of wild pointer (rbp/rdi not verified).
Unchecked Pointer Arithmetic:
lea rcx, [rcx+r9*2+15B9D332h] ; Address generation with untrusted inputs (rcx/r9).
lea rdi, [rax+rdi-67C12391h] ; Large negative offset risks crossing memory boundaries.
Stack/Register Corruption:
pop rbx ; Potential stack imbalance.
sar al, 63h ; Destructive bitwise operation on register state.
The assembly code exhibits poor pointer hygiene and lack of bounds checks , directly correlating to the observed BSOD (0x50 ) presents above.
Then i would contact support for help :)
Looks horrible and hope it be fixed soooooon)))
Thx, I will get to that~
Same problem, and it happened after launch/quit warthunder and during the gaming. The cause including invalid memory and write on read only memory.
Also having the exact same issue for about a week now, nothing I’ve tried, including BIOS update, driver update, uninstall/reinstall, has worked.
Do any of you having this problem have an intel 13th or 14th gen processor. I do and am wondering if that could be the issue.
I’m 14900k with 0x129 microcode BIOS fixed. That doesn’t seem solving the issue.
Hello brother! I have been experiencing the same persistent blue screen issue caused by BEDaisy.sys almost at the same time as you, which has been bothering me for over half a month now. After trying all the obstacle removal operations that I could do, I still sought help from GAIJIN’s technical support, but they have not provided me with any solutions so far. So I want to ask, have you found a solution to this problem?
Hey bro. I reported to Gaijin with a technical ticket. After I sent them a memory dump, there was no positive and detailed technical reply, nor did I have a solution to this problem. I could only shut down the anti-cheat system and just play air realistic battle.
https://answers.microsoft.com/en-us/windows/forum/all/bedaisysys-keeps-crashing-my-computer/10df6fa1-c032-441e-9a81-2abf9b68c0f6
This is an old issue. But up to now there is no technical solution to this problem
Hello gang. I too am having this problem. I have an updated BIOS and don’t use Verifier. This is clearly their problem and I’m worried it is going to turn my PC into a brick.
Hello! Привет! Turn OFF in BIOS Intel Turbo Boost Technology, Turbo Boost 2.0, 3.0 etc и скажи спасибо, что подсказал единственный вариант решения этой проблемы на данный момент 🤫😊
Intel i9-13900KF here.
I also have “Attempting to write to Read only memory” BSOD’s usually linked to a file called BEDaisy.sys
The BSOD’s started around BattleEye’s implementation & have slowly been getting worse since.
The crashes occur when starting the game itself. When entering entering or exiting either a battle or even testdrive and even at random while the game is tabbed.
I’ve also tried updating drivers & turning off turbo boost (3.0) in Bios.
Verified game files more times than I care to count. Driver Verifier was off by default and still is.
So far no possible solutions have resolved the issue.
Would it be better to use Win 10？
Same issue appeared on Linux
Are you using an Intel 13th/14th gen CPU by any chance?
no, I’m not using an intel 13th/14th genCPU; i’m using an amd ryzen 5 3600x