Steam Community :: Guide :: [Fix] Game crashes after 1-3 minutes

Store Page

Battlefleet Gothic: Armada 2

All Discussions Screenshots Artwork Broadcasts Videos News Guides Reviews

Battlefleet Gothic: Armada 2 > Guides > Juuken's Guides

165 ratings

[Fix] Game crashes after 1-3 minutes

By Juuken

Your game crashes after a few minutes, despite you having the best PC on this motherfifing planet?
This guide has got you covered ...

Award

Created by

Juuken
Offline

Category: Modding or Configuration

Languages: English

Posted

Updated

15 Sep, 2022 @ 3:30am

29 Sep, 2022 @ 6:54am

11,539	Unique Visitors
263	Current Favorites

Guide Index

Overview

How to fix it

Comments

How to fix it

Since there is more demand for this than I had anticipated, and the forum seems to be a place that is hard to search, I decided to mold this workaround into a guide. For reference, here is the forum entry with a bit more information/context: https://steamhost.cn/steamcommunity_com/app/573100/discussions/0/3196993316877456645/

Disclaimer: This workaround was not discovered by me. I merely convey the message. See the forum for more information on this.

The problem occurs on 10th-12th generation Intel processors and is caused by old methods the game uses. To prevent the crash from happening we have to circumvent a OpenSSL SHA check.

The following steps will prevent the crashes from happening for all games that suffer the same issue - even those outside of Steam.

Open "Control Panel" by searching for it in Windows search bar, by pressing the Windows button or key.
Go to "System & Security"
Go to "System"
Press "Advanced system settings"
Press "Environmental Variables"
Create a new "System Variable" (NOT USER VARIABLE)
Enter the following into the Variable name box: OPENSSL_ia32cap
Enter the following into the Variable value box: ~0x20000000
Now press OK.

Note: In the same window there is also a button for deleting this setting. Just click on the entry you just created, then on delete and you are done. Make sure you do not delete the wrong entry. If you accidentally did, click on cancel and everything should be fine again.

For your convenience, you can also try these alternatives.

Orig. referred to by Koala 4peace and Imnuktam in the comments & the forum:
This will prevent the crashes only for one specific game - in our case Battlefleet Gothic Armada II.

Open Steam and go to your library.
Right click on the game in your library and click on properties.
Under General -> Launch Options copy & paste this line:
cmd /c "set OPENSSL_ia32cap=:~0x20000000 && %command%"
Start the game.

Note: If you are using e.g. Skalgrim's mod the -NoEAC flag needs to be placed after the command. So, it has to look like this:

cmd /c "set OPENSSL_ia32cap=:~0x20000000 && %command%" -NoEAC

Orig. written by Devren in Bloodstained: Ritual of the Night forum:
If you do not give a damn about anything, just fire off this here.

Open CMD as Administrator (use the Windows search if you are unsure).
Copy this into the prompt: "setx OPENSSL_ia32cap ~0x20000000"
Hit enter.
Restart the PC, then start the game.

There is more information about what is happening on Intels side. You can look it up here:
https://www.intel.com/content/www/us/en/developer/articles/troubleshooting/openssl-sha-crash-bug-requires-application-update.html

56 Comments

< >

X-K@l1ber 14 Jul @ 10:59am

Thanks for the tip, I confirm that it worked for me in July 2025 on a new laptop with Intel Core Ultra 9 275, Windows 11 and RTX5080.

More precisely, my windows environment was already containing all what is indicated. What actually fixed the issue for me was to add the following prompt in the Steam Launch Options of the game:

"setx OPENSSL_ia32cap ~0x20000000"

The real key here is the "x" collated to ''set''. Typing only "SET" as suggested in some comments of this thread does not work and generate an error message in Steam when launching the game. But the above prompt (without the brackets of course) did work and finally allowed me to enjoy the game without any crash.

Ace Hazume VTuber 31 May @ 1:41am

All good, I reversed the changes if I'm not playing by deleting the System Variable. I was using the second steam launch option, didn't realize it was a CMD command woops

Juuken [author] 30 May @ 12:46am

@Ace Hazume YT
What do you mean by that?

Ace Hazume VTuber 29 May @ 7:28pm

Will this affect future games?

scorryuk 24 Feb @ 4:19am

Thanks, fixed it.

gristterry604 19 Oct, 2024 @ 10:40pm

i dont know why the alt launch option worked for me when i tried creating a var and that didnt

my specs are 14th gen i9 14900k
and an rtx 4080 super

Grindbakken 6 Jul, 2024 @ 3:36pm

Som additional info: the change made with cmd /c "set OPENSSL_ia32cap=:~0x20000000 && %command%" will not persist after a restart. Here's why: Command Prompt Scope: This command is executed within the current command prompt session. Environment variable modifications made this way only affect that specific session. System-wide Variables: To make changes to environment variables that persist across restarts, you'd need to modify them in your system's environment settings.

Eye_of_Truth 29 Jun, 2024 @ 12:08am

I don't have any other games made in Unreal Engine 4 that had this issue, so I was looking for a fix that I could apply just to this game alone without adding environmental vars or messing with my computer too much. Thx for the alt launch option!

Juuken [author] 25 May, 2024 @ 2:42am

Don’t mention it.

Asbjourn 24 May, 2024 @ 5:54pm

Thank you so much for this.

< >