The freeze is not actually a crash - it's still running. I am not getting any crash dumps in \Documents\Battlefield 2042\CrashDumps
I've had the 'freeze' during loading going into a match (mainly) or mid-game.
To diagnose, by running Process Monitor (sysutils) - the game is very much working - still - it's griding through a lot of I/O (seems to be verifying game files, reading .cas files, and finishing with reading the BF2042.exe fully - which is odd since the game is fully loaded already, so I suspect some kind of pre-game binary validation or the game spawns itself).
It then moves to doing some minmal local network coms (looking like a tiny bit of UDP traffic, 384 bytes), then talks to an aws server (ec2-34-248-202-243.eu-west-1.compute.amazonaws.com:https).
This is where it gets interesting - it tries that connection to the AWS server three times (before I gave up and killed the process), at exactly two minute intervals (see attached picture). At this stage (even before the aws server connection, the game appears to the user to have crashed already (the loading spinner (4 green cubes) stops moving)
I'm not sharing the PWL file publicly, it contains potentially private information, will only do via direct message or other non public channel.
This is fairly new behaviour, I noticed it first around the time of the new patch. I've had minimal issues with stability until recently.