FSR2 Implementation Causing Sudden Crash

Yup I was on Bios defaults both before and after the update. Will try downgrading the Bios to the version I had, however I noticed that its not only related to fsr2 but in general to upscaling and anti aliasing because after changing in game options i've got different results with the same error code:

• Upscaling - DLAA - Ends with FSR2 related error 0xc0000005 Access Violation
• Upscaling - OFF, Anti-Aliasing - DLAA - Ends with Nvidia error related to 

  nvwgf2umx.dll file (same error code)

• Upscaling - OFF, Anti-Aliasing - TAA - Ends with the same error code but it doesn't even show now what it is related to, only this gibberish:

CONTEXT: (.ecxr)

rax=0000000001e2f89c rbx=0000000000000000 rcx=0000000000000000 rdx=000000004a545080 rsi=0000000001e2f89c rdi=000000004a545080 rip=0000000000000000 rsp=000000007217f918 rbp=000000007217f968 r8=0000000000000000 r9=000000004a6b7b30 r10=000000004a5dd5c0 r11=000000004a6b7b30 r12=0000000000000000 r13=000000004a5d8480 r14=0000000000000000 r15=0000000000000000 

iopl=0 nv up ei pl zr na po nc cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010246 00000000`00000000 ?? ???

Resetting default scope

EXCEPTION_RECORD: (.exr -1)

ExceptionAddress: 0000000000000000

ExceptionCode: c0000005 (Access violation)

I also noticed  that the same error is happening when I run a multi core stress test on Cinebench r23 with a CTD, but I managed to fix(?) that and perform full test without any CTD by doing as follows:

• manually setting power limits of PL1 and PL2 to 253W
• setting IccMax to 307A
• manually setting CPU Temp Protection to 100 degrees celsius
• changing CPU Vcore Loadline Calibration from "Auto" to "Medium"
• changing CPU V core from "Auto" to "Normal"
• changing dynamic V Core to -0.050V (undervolting)

Unfortunately these BIOS settings only worked out with Cinebench. In BF6 the problem still persists.