Invalid Pointer and Access Violations (CRASH)

HyroPlay​ it appears EA anticheat files might be corrupted. If you have issues playing BF6 I would try to repair EA anticheat or uninstall/reinstall it.

If you do uninstall EA anticheat, make sure to reboot the PC after uninstall in order to uninstall the kernel driver fully.

https://help.ea.com/en/articles/platforms/pc-ea-anticheat/

I don't want to celebrate prematurely, but... after some BIOS adjustments, I managed to play several matches and haven't had any problems, at least not yet. I'll continue testing and come back to this post to report whether it worked or not.

I manually changed some settings from auto to match my RAM:
System Memory Multiplier: Auto -> 3200MHz
Memory Ref Clock: Auto -> 100Hz
Gear Mode: Auto -> Gear 2
Memory Boot Mode: Auto -> Normal
DRAM Voltage: 1.20 -> 1.25

Interestingly, I noticed that every time I start Windows, a "Windows Error Report - Blue Screen" event appears in the event viewer. The system works normally, but these warnings continue to appear occasionally...

Checking the crash dump, it says it's related to "eaanticheat.sys".

Could you tell me anything about this? Should I worry about these warnings or can I simply ignore them? From my research, it could be eaanticeheat interfering with something in my system, but since it hasn't presented any problems on my system so far, apparently...

Crashdump:

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)

 A device driver attempting to corrupt the system has been caught. This is because the driver was specified in the registry as being suspect (by the administrator) and the kernel has enabled substantial checking of this driver. If the driver attempts to corrupt the system, BugChecks 0xC4, 0xC1 and 0xA will be among the most commonly seen crashes.

Arguments: 

1. Arg1: 00000000000000c5, Thread APC disable count changed by driver dispatch routine.
2. Arg2: fffff80bf2477880, Driver dispatch routine address.
3. Arg3: 000000000000ffff, Current thread APC disable count. Arg4: 0000000000000000, 

• Thread APC disable count before calling driver dispatch routine. 
• The APC disable count is decremented each time a driver calls KeEnterCriticalRegion, FsRtlEnterFileSystem, or acquires a mutex.
• The APC disable count is incremented each time a driver calls KeLeaveCriticalRegion, FsRtlExitFileSystem, or KeReleaseMutex.
• Since these calls should always be in pairs, this value should be zero when a thread exits.
• A negative value indicates that a driver has disabled APC calls without re-enabling them.
• A positive value indicates that the reverse is true. 

Debugging Details:                                                                                                                                                                           ------------------                                                                                                                                                                        Unable to load image eaanticheat.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for eaanticheat.sys

Okay, I'll try that, but... curiously, I ran Memtest86 last night to check the memory, and surprisingly, it passed without errors...
I'll send the complete file, but here's the final part ->

"2026-01-04 03:33:46 - get_mem_ctrl_timings - [0-0-0] 3192 MT/s (16-22-22-52)
2026-01-04 03:33:46 - Current mem timings: 3192 MT/s (16-22-22-52)
2026-01-04 03:33:46 - Current CPU temperature: 35C
2026-01-04 03:34:03 - RunHammerTest - Running hammer test on 4 CPUs (512MB each) [0x800000000 - 0x880000000]
2026-01-04 03:34:41 - MtSupportRunAllTests - Test execution time: 387.499s (Test 13 cumulative error count: 0, buffer full count: 0)
2026-01-04 03:34:41 - Finished pass #4 (of 4) (Cumulative error count: 0, buffer full count: 0)
2026-01-04 03:34:41 - Cleanup - Unlocking all memory ranges...
2026-01-04 03:34:41 - All memory ranges successfully unlocked
2026-01-04 03:34:43 - Test result: PASS (Errors: 0)"

thanks the attention

HyroPlay​ try lowering memory frequency to 2400MHz. Keep the memory timings at their current value of 16-22-22-52 and don't change them.

See if BF6 stops crashing.

Error Code: 0xC0000005 is usually caused by memory errors due to unstable memory.

If I don't reply to your post then personal message me. Sometimes the forum fails to notify me when someone replies.

I've noticed that several people are experiencing similar problems... I'm eager to know if this is already being investigated.