[SOLVED] Error 01 / crash when starting the game/campaign (on AMD GPU)

[Star]

Sharing what worked for me in case it helps someone.

Specs: Ryzen 5 5600X | 32 GB RAM | RX 9070 XT | Windows 11

Problem:
- On launch, a warning said my AMD driver had "known issues with D3D12" and recommended 26.3.1.
- Then I got "Out of video memory" or the game closed with Error 01 when starting the campaign, no log generated.

What did NOT work:
- Downgrading to driver 26.3.1 (the one the game recommends): still crashed.

What fixed it:
1. Went back to the current driver (26.8.1) and ignored the warning on launch.
2. Increased Windows virtual memory (page file) to 32800 MB:
System Properties > Advanced > Performance Settings > Advanced > Virtual memory > Change
Uncheck "Automatically manage", select your SSD, set initial and maximum size to 32800, click Set and reboot.
3. Launched again and the campaign started fine, running smooth with no lag.

The game seems to use a lot of memory when loading the campaign and crashes with the default page file, even with 32 GB of RAM.

Warning: there's an "Error 01 fix patch" going around on GitHub (.exe from an unknown account). Don't download it, it looks like malware. The fix above is just a Windows setting.

[Mono'sono]

This definitely helped me with my gameplay I haven't had any issues since

[.]

Yes, finally. I tried to mess around with the page file yesterday, but I set to 16. Apparently it wasn't enough. Setting it to 32 is the only thing that got me past the second cutscene.

[Skwangtang]

There is a new OPTIONAL Radeon patch out as of 9/29 that fixed my issue. Go to their website and download the new optional driver. Thats what fixed my issue.

[Emperor_Kane40k]

Is this for desktop only or steamdeck as well?

[MS-06Fb]

Same Can't open Game . Error 01 on PC .
i7-13700
32.0 GB
GeForce RTX 4060 Ti (8 GB)

[MARCH-10]

Thanks, this seems to be the fix for me. It has been 6 hours without a crash so far.

[Star]

Originally posted by Skwangtang:

There is a new OPTIONAL Radeon patch out as of 9/29 that fixed my issue. Go to their website and download the new optional driver. Thats what fixed my issue.

Are you talking about 26.9.2?
When I went through this process, that driver hadn't been released yet, but that's good to know—I'll test it out and see how it performs.

EDIT: I tested 26.9.2, and it is indeed running better.