I'll start with my specs:
Ryzen 3700x
RTX 2080 Super
32gb RAM
Ancient Windows 10
Nvidia drivers from nearly 2 years ago.

I play the game at 1440p, borderless.
Vsync off
Frames capped to 60 in settings
All settings Medium
DLSS Quality

I have well over 90 tabs open in Firefox while I play also. I don't bother closing it.

In cutscenes I don't dip below 30fps, in hangars/plane selection I'm between 45-60, in-game I'm between 40-60, generally 55-60.

I had no issues with the game, until Mission 11.

After the briefing cutscene, then selecting my plane, then take-off, the game would crash at the same point, every time with the dreaded UE Error 0,1, right before it would give me control of my plane back and the mission would start. Event viewer confirmed it was an issue with the Nvidia driver and/or my GPU, so it wasn't an issue with page files, or RAM usage.

I tried a number of different things, including the suggested steam launch option to disable Async compute, restarting my computer and changing from borderless to fullscreen. Nothing changed anything, the async compute command-line switch lowered my FPS in plane selection/hangar by about 10%, but other than that, the exact same crash at the exact same time. Each time I changed a setting, I reverted it back to how it originally was after it didn't work, to ensure I could isolate the issue once I found it.

I was ready to try a different command-line switch to rebuild the shader cache from scratch and then if that didn't work, actually update my drivers, but I decided to try one more thing first.

Opening Nvidia control panel's global settings, I changed shader cache size from "Driver Managed" to "100gb". Launched the game again, nothing different, nothing changed, with one exception. This time, it crashed a few frames later than before, the crash occurred at exactly the moment when it would have given me control of my plane, the Green Box that said "Mission Start" being frozen on my screen behind the error. So I decided to open the game one more time without changing any settings and see what happens.

First, the start-up screen of the game, where it compiles shaders, completed in 5 seconds, the bar zooming across the screen! Whereas every time before, I would have to sit for 2 to 3 mins as the game setup the shaders again, every time I booted the game.

Second... IT WORKED! The cutscenes post-take-off played, control of my plane was given back to me and I finished the mission. Played and beat the next one too! On top of that, the little stutters the first time I would blow up a plane since opening the game or first time I would load into the hangar also disappeared completely.

It seems like the game was compiling and saving more shaders than the driver was allowing it to save, and it wasn't great at figuring out what to do if it needed to use more shaders than it was allowed to even save all for a single scene. So, allowing it more space to save the shaders let it do what it wanted to do, and all is great.

If you're having issues that relate to my experience, give it a try,

Hope this helps!