Community ManagerCheck the following post, there is potentially helpful info and troubleshooting steps there:
Thanks @SteveJackson
@ozzygamer275 it’s best if you add a dxdiag
think @EA_Barry is mainly referring to the frame rates bits. When you have kit that can murder the frame rate it’s sometimes counter intuitive to fix it.
Problem is, a lot of people run the game on older kit so it’s default setting is to raise frame rates.
You probably have issues with the setup if you get CTDs, Could be RAM, board issues or drivers/settings, best to check it all out. OCs aren’t advised either, just in case you are.
Anyway, post that dxdiag 👍
@ozzygamer275 wrote:
@SteveJackson@EA_BarryAdded DxDiag, knew i forgot something.
Already checked everything else to do with setup, especially RAM as i had an unrelated mem_management BSOD the other day so did a memtest which passed, being a PC technician, this all comes naturally to me.
It seems to crash only in multiplayer with cross-play enabled, I have not had the game crash with cross-play disabled, however I am in a cross-play League so turning it off is not an option.
another error code I've had is PTDK-SAGT-SGXK-XCVE
The session codes are unique so they do help the devs if they deign to track your sessions given the code histories.
Often another pair of eyes is useful - sometimes you can overlook things, sometimes there is confirmation bias that isn’t present from a detached viewpoint.
I’ll get on the dxdiag and, umm….whisper 😂
