Constant Crashing - 0xc0000005

Keeps calling "ffxFsr2ResourceIsNull"

I saw your list in the big thread. 

Can you / Did you disable your E-Cores in the Bios

and

can you / did you try a user.cfg to limit (after disabling the ecores) the used cpu cores?

Thread.ProcessorCount 6

Thread.MaxProcessorCount 6

Thread.MinFreeProcessorCount 0

Thread.JobThreadPriority 0

GstRender.Thread.MaxProcessorCount 12

I have tried the cfg file one also, yes.

I am not going to start disabling cores of my CPU to appease a horrifically incompetent dev team, though.

Especially considering the crash dump points at a graphical problem (calling FSR modules) which have nothing to do with the CPU.

does it hurt to test? 

you are in the 0.00001% who have the problem on more then 10 million sells. 

imho the fsr module gets called because of something in your specific hardware configuration.

in the mainboard / bios and might be related to the early Intel cpu e-cores & AMD CCDs. 

Take it or leave it.

I'll leave it, thanks.

Not doing any further messing about with my hardware to make this game work. I can play literally everything else without issue. Messing about with CPU settings will do nothing to fix what is clearly a problem intrinsic to the game's engine. I've done more troubleshooting on this game than I have even with software and hardware configurations in my actual job.

13th gen is not considered to have early e-cores (introduced in 12th gen) and, again, this is not relevant to FSR calls. Also irrelevant considering a large number of people having the same problem are using Ryzens.

imho the fsr module gets called because of something in your specific hardware configuration.

It shouldn't be called at all considering FSR is not even turned on.

battlefield is capable of scheduling to ecores properly, and removing them nukes performance, and always did

engine is forcefully loading all upscaling solutions, which you can test by removing amd and intel dlss completely, and then the game will not launch at all. it's either tragic implementation (assuredly, given how utterly broken DLSS/Reflex is in this game) or AMD being bad at software (also assured)

i know everything you are saying. 

BUT

doesnt change the fact that he is not able to play the game with his specific hardware configuration does it?

If this is the only game that is problematic then surely one would presume that my specific configuration is not the problem.

You still haven't explained how my CPU using e-cores is relevant when other users have the same problem using Ryzens (which do not have e-cores), or older than 12th gen Intels (also no e-cores).

Please stop pushing the process down a dead end.

ok mate, good luck.