jozefpodlecki
New member
- Local time
- 7:05 PM
- Posts
- 3
- OS
- Windows 11
Winver: 25H2 ( OS Build 26200.8655 ) Windows 11 Home
Hello,
I suddenly started getting a BSOD while launching the game, and it looks like something is going wrong in Easy Anti-Cheat. Unfortunately, WinDbg's bugcheck analysis didn't pinpoint where the problem might be occurring.
The error only appeared today, so any reasonable conclusion would be that it's related to either a recent Windows update or a device driver. Naturally, once the BSOD started happening, I went through the usual troubleshooting steps: updating my graphics driver, removing the game folder containing the binaries, and then triggering Steam's integrity verification to download them again.
My conversation with AGS was fruitless and, at times, it felt like I was talking to an AI assistant or someone with very little technical knowledge.
I cannot rule out another possibility: that my hardware is simply getting old. I ran MemTest64 for a few iterations, but it didn't detect any issues.
I've attached a link to the v2 log via Google Drive, as I was unable to upload it directly to the forum. Perhaps the file size is too large, although it's only around 3 MB, or maybe I don't have enough forum reputation yet.
As requested, I performed the additional steps.
TuneUp tool has been running for quite a while.
Logs:
TuneUp Plus
Application.evt
System.evt
BSOD V2
Ran Enable_automatic_backup_of_system_registry_to_RegBack_folder.reg
Created Restore Point with pwsh
I've also attached some console output from WinDbg.
Some interesting keywords that stood out to me are PAGE_FAULT_IN_NONPAGED_AREA and MiVisibleState.
Thanks in advance!
Hello,
I suddenly started getting a BSOD while launching the game, and it looks like something is going wrong in Easy Anti-Cheat. Unfortunately, WinDbg's bugcheck analysis didn't pinpoint where the problem might be occurring.
The error only appeared today, so any reasonable conclusion would be that it's related to either a recent Windows update or a device driver. Naturally, once the BSOD started happening, I went through the usual troubleshooting steps: updating my graphics driver, removing the game folder containing the binaries, and then triggering Steam's integrity verification to download them again.
My conversation with AGS was fruitless and, at times, it felt like I was talking to an AI assistant or someone with very little technical knowledge.
I cannot rule out another possibility: that my hardware is simply getting old. I ran MemTest64 for a few iterations, but it didn't detect any issues.
I've attached a link to the v2 log via Google Drive, as I was unable to upload it directly to the forum. Perhaps the file size is too large, although it's only around 3 MB, or maybe I don't have enough forum reputation yet.
As requested, I performed the additional steps.
TuneUp tool has been running for quite a while.
Logs:
TuneUp Plus
Application.evt
System.evt
BSOD V2
Ran Enable_automatic_backup_of_system_registry_to_RegBack_folder.reg
Created Restore Point with pwsh
Checkpoint-ComputerI've also attached some console output from WinDbg.
Some interesting keywords that stood out to me are PAGE_FAULT_IN_NONPAGED_AREA and MiVisibleState.
Thanks in advance!
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: ffff9382f500001c, memory referenced.
Arg2: 0000000000000000, X64: bit 0 set if the fault was due to a not-present PTE.
bit 1 is set if the fault was due to a write, clear if a read.
bit 3 is set if the processor decided the fault was due to a corrupted PTE.
bit 4 is set if the fault was due to attempted execute of a no-execute PTE.
- ARM64: bit 1 is set if the fault was due to a write, clear if a read.
bit 3 is set if the fault was due to attempted execute of a no-execute PTE.
Arg3: fffff8038ec4c192, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)
TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b
DUMP_FILE_ATTRIBUTES: 0x31808
Kernel Generated Triage Dump
FAULTING_THREAD: ffff9382e77e5080
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffff9382f500001c
READ_ADDRESS: fffff803c41c44d8: Unable to get MiVisibleState
ffff9382f500001c
MM_INTERNAL_CODE: 2
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
IP_IN_PAGED_CODE:
EasyAntiCheat_EOS+efc192
fffff803`8ec4c192 8b09 mov ecx,dword ptr [rcx]
STACK_TEXT:
ffffa582`87e83898 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
SYMBOL_NAME: EasyAntiCheat_EOS+efc192
MODULE_NAME: EasyAntiCheat_EOS
IMAGE_NAME: EasyAntiCheat_EOS.sys
STACK_COMMAND: .process /r /p 0xffff9382bb50f040; .thread /r /p 0xffff9382e77e5080 ; kb
BUCKET_ID_FUNC_OFFSET: efc192
FAILURE_BUCKET_ID: AV_EasyAntiCheat_EOS!unknown_function
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {220d5b3d-33fc-4c8e-6484-ebd7c9e905b8}
Followup: MachineOwner
My Computer
System One
-
- OS
- Windows 11
- Computer type
- Laptop
- Manufacturer/Model
- Lenovo




