Crash to desktop
Starting another thread, have had no luck with anyone responding in my previous thread.
BF6 Crash to desktop. | EA Forums - 13757745
I've posted multiple crash dumps with some WinDBG discussion.
Begging someone from EA to have a look at them please?
Another request. Please do not tell me to test my RAM, run sfc, dism, windows updates, chkdsk, check my bios, DDU and clean install graphics drivers - I've done it all, my system is rock stable on memory torture tests and I'm not having crashes in other games.
I believe I have crash dumps showing an internal Frostbite code fault, that needs an engine fix and really want someone to look.
This new crash dump confirms that the engine is still hitting the exact same underlying failure signature ({265cbc3d-0f53-afc4-26f5-62f7bba0764f}).
Identical Failure Bucket: Exception Code: 0xC0000005 (Access Violation - Read)
Failure Hash: {265cbc3d-0f53-afc4-26f5-62f7bba0764f} (Matches all previous dumps line-for-line).
Offset: bf6!ffxFsr2ResourceIsNull + 0x29e8670
Instruction: mov rax, qword ptr [r14+70h]
Target Address: 0x0000040014545a70 (derived from r14 = 0x0000040014545a00 + 70h).
WHAT THIS MEANS -
A worker thread executing within Frostbite's FSR2 / resource pipeline (ffxFsr2ResourceIsNull) attempted to read a pointer at offset +70h of a data structure (r14). However, that memory handle was already freed, unmapped, or invalid, causing an immediate access violation.
Even if I have DLSS enabled or upscaling completely turned off, the Frostbite engine is still initializing and referencing internal FSR2 resource hooks in the background. I just can't change any settings in the game to stop it happening. I've tried, a lot.
