For the developer:
Crash: Access Violation (0xFFFFFFFFFFFFFFFF) in SoftMaxNormalize
Thread: main
┌─────────────────────────────────────────────┐
│ Caller: ??? (likely AI/ML code) │
│ Parameter invalid / NULL pointer │
└───────────────┬─────────────────────────────┘
│
▼
┌─────────────────────────────────────────────┐
│ SoftMaxNormalize │
│ Function: SoftMax computation on vectors │
│ Faulting instruction: movdqa [rbp-10h], xmm0 │
│ Problem: input pointer is NULL or uninitialized │
└───────────────┬─────────────────────────────┘
│
▼
┌─────────────────────────────────────────────┐
│ ANTICHEAT_VIRTUALIZE_CODEMARKER_SHIELD │
│ Memory / code protection wrapper │
│ May interfere with registers and stack │
└───────────────┬─────────────────────────────┘
│
▼
┌─────────────────────────────────────────────┐
│ Main game / Frostbite engine thread │
│ Event loop / AI processing │
└─────────────────────────────────────────────┘
NULL / 0xFFFFFFFFFFFFFFFF pointer enters SoftMaxNormalize, causing the access violation.
Upper stack shows the AntiCheat wrapper, which might modify registers or pointers before the SoftMax calculation.
The crash is reproducible, indicating that the caller function is receiving invalid data under specific conditions (AI input, network, save files, etc.).
Things to Investigate
Parameters passed to SoftMaxNormalize → check for empty or uninitialized vectors.
AntiCheat sequence → see if it modifies registers/pointers before SoftMax.
AI data / save files → corrupted files or unusual input can produce invalid pointers.