ACTUAL fix to crash on start screen

[Typhoon]

After a lot of troubleshooting, debugging and deliberations regarding the crash when loading in to the main menu, I believe the bug can be fixed by following the steps below:

1. Open the system environment variables options in Windows. either via
- right clicking "This PC/My Computer" > Properties > Advanced > Environment Variables...
or
- open start menu > start typing "environment variables" > open the dialog from there
2. Under the SYSTEM variables (NOT "USER" variables above them), add a new variable by clicking "New..."
3. Enter the variable name "OPENSSL_ia32cap" without the quotes
4. Enter the variable value "~0x200000200000000" without the quotes
5. Click OK

If needed, close said windows and repeat step 1 to check if your new variable mentioned above is now in the list of SYSTEM variables. If so, boot your game and give it a try.

Don't forget to disable or delete your firewall rule if you previously used the "block all connections" workaround for offline play.

More technical details

Since the blocking of outgoing connections seemed to allow offline play, most signs obviously pointed towards this being an issue with network calls somewhere within the call stack.

Initially I tried intercepting the calls via a local proxy, however nothing obvious appeared in those requests - interesting...

Packet-sniffing didn't yield too much info, either - although I'm not an expert in that field by any means.

I then managed to find some crash dumps at "C:\Users\your-user\AppData\Local\CrashDumps" (great naming there, Codemasters...) which I analysed.

The stack trace pointed to an issue at "MicroMachines::GetMonoScriptManager" which again wasn't too helpful.

I then loaded the Unity debugging symbols within WinDbg which pointed me towards "_sha1_block_data_order".

After some searching online, it seemed to be related to an OpenSSL SHA bug. From there, the initial fix mentioned above was found and thankfully, it seems to have done the trick.

Obviously you can replace the system environment variable with a one-off command in a custom script or the launch args of the game in Steam if you prefer, although I'm trying to keep the initial fix steps easy for the average user.

[JamsGame]

Thanks this worked first time!

[WookieWaffle]

Originally posted by Typhoon:

After a lot of troubleshooting, debugging and deliberations regarding the crash when loading in to the main menu, I believe the bug can be fixed by following the steps below:

1. Open the system environment variables options in Windows. either via
- right clicking "This PC/My Computer" > Properties > Advanced > Environment Variables...
or
- open start menu > start typing "environment variables" > open the dialog from there
2. Under the SYSTEM variables (NOT "USER" variables above them), add a new variable by clicking "New..."
3. Enter the variable name "OPENSSL_ia32cap" without the quotes
4. Enter the variable value "~0x200000200000000" without the quotes
5. Click OK

If needed, close said windows and repeat step 1 to check if your new variable mentioned above is now in the list of SYSTEM variables. If so, boot your game and give it a try.

Don't forget to disable or delete your firewall rule if you previously used the "block all connections" workaround for offline play.

More technical details

Since the blocking of outgoing connections seemed to allow offline play, most signs obviously pointed towards this being an issue with network calls somewhere within the call stack.

Initially I tried intercepting the calls via a local proxy, however nothing obvious appeared in those requests - interesting...

Packet-sniffing didn't yield too much info, either - although I'm not an expert in that field by any means.

I then managed to find some crash dumps at "C:\Users\your-user\AppData\Local\CrashDumps" (great naming there, Codemasters...) which I analysed.

The stack trace pointed to an issue at "MicroMachines::GetMonoScriptManager" which again wasn't too helpful.

I then loaded the Unity debugging symbols within WinDbg which pointed me towards "_sha1_block_data_order".

After some searching online, it seemed to be related to an OpenSSL SHA bug. From there, the initial fix mentioned above was found and thankfully, it seems to have done the trick.

Obviously you can replace the system environment variable with a one-off command in a custom script or the launch args of the game in Steam if you prefer, although I'm trying to keep the initial fix steps easy for the average user.

You Sir are a Genius

[Wudds]

thank you for this, it worked perfectly

[Hawk X]

wow this worked perfectly!!

Took so long to find this thread!!
So much for having a "too powerful" computer! :)

MANY thanks for the author for the detailed explanations!

[daNsKah]

<3

[chown -R us base]

Completely irrelevant game, ended up here searching for GetMonoScriptManager (<3 windbg, also ♥♥♥♥ windows for not telling me it did crash dumps by default)

I love you OP, you're my MVP of the day.