BF6 black-screen crash corrupts save and resets settings

I have experienced this issue approximately 8 times over the past month and a half.

Battlefield 6 will sometimes begin starting or loading normally, then the game or display suddenly goes completely black. It appears to happen during or shortly after the game initializes graphics.

When this happens, I cannot recover the game normally and eventually have to perform a hard reboot of the PC.

After restarting Windows and launching Battlefield 6 again, I receive the following message during Checking Data:

WARNING: Your save file(s) are corrupt and could not be read by the game. Continuing will overwrite the corrupt save file.

After continuing, Battlefield 6 resets my settings and I have to configure the game again.

Typical sequence:

Launch Battlefield 6.

Game begins startup or loading.

Screen suddenly goes completely black.

Normal recovery is unsuccessful.

PC must be hard rebooted.

Restart Windows.

Launch Battlefield 6 again.

Checking Data appears.

Battlefield reports that the save file is corrupt.

Continuing overwrites the corrupted save.

Battlefield settings are reset.

Frequency:

Approximately 8 occurrences over about 6 weeks.

Expected result:

Battlefield 6 should start and load normally without causing a black-screen graphics failure, corrupting local save or configuration data, or resetting player settings.

Actual result:

The game or display goes black, a forced reboot is required, and the next Battlefield launch reports corrupted save data and resets the game settings.

System:

Windows 11 Pro

NVIDIA GeForce RTX 4070 Ti SUPER 16 GB

32 GB RAM

I am attaching a screenshot showing the Battlefield 6 Checking Data and save file corrupt warning.

Because this has happened repeatedly after the black-screen failure, there may be an issue where Battlefield 6 is writing to the local save or configuration file when the graphics failure occurs. If the crash interrupts that write operation, it may leave the file incomplete or corrupted.

This is a recurring issue and not an isolated save corruption event.