The problem is that the graphics driver is crashing for an unkown reason.
The attached crash logs show a stack trace which only contains AMD graphics driver related code.
So it seems to be an issue with the AMD driver it self, not even Unity or WFTO.
When searching the web for the drivers involved in the crash, I find similar issues of other people having similar crashes in other games (including Witcher 3, Farcry 3, Batman Arkham Knight and even World of Warcraft).
See some fellows:
(which can be found by searching one of the items in stack trace eg "AmdLiquidVrD3D11WrapDeviceContext" or "AmdDxGsaFreeCompiledShader")
https://community.amd.com/thread/196520
https://community.amd.com/thread/200731
http://steamcommunity.com/app/265550/discussions/0/613935404114338338/
https://steamcommunity.com/app/292030/discussions/0/613958868368558837/
http://us.battle.net/forums/en/wow/topic/18300092113
https://forums.wildstar-online.com/forums/index.php?/topic/128360-cant-launch-the-game/

On a quick look, none of them got a decent answer and thus I don't know how to help.
It looks like it's either an issue with newest AMD drivers or a system specific issue with your configuration.
There is no pointer that it would be related to the War for the Overworld code.

If anyone has found a solution to this problem, please leave us a message here.

Cheers

This is not a "Crash" but the game shuts down because Steamworks can not initialize.
The problem comes from an issue where Steamworks fails to realize that Steam is running and thus fails to initialize so the game can not work and shuts down with this message.
Many Steam games might not suffer from this issue because only some games on Steam actually use Steamworks.
Do you have games which use Steamworks that actually work?

This problem pops for some people from time to time.
Like here:
http://brightrockgames.userecho.com/topics/4-critical-error-steam-initialize/

However in almost all cases it was resolved by:
- Either simply rebooting your system
- Reinstalling Steam client (and not the game)
- In rare cases by resetting TCP/IP because any program(or user) modified it so Steam ports coouldn't be used

However we also have an issue with OSX startup crashes for some people due to an Unity issue.
If you suffer from this please read:
http://brightrockgames.userecho.com/topics/1256-os-x-crash-on-startup-v140/

I hope this helps!
Let us know how it goes.

The crash stack trace contains only system internal stuff and not anything which would relate to War for the Overworld:

0x00007FFC9AD48316 (atidxx64) AmdDxGsaFreeCompiledShader

0x00007FFCC1D48102 (KERNEL32) BaseThreadInitThunk

We got some known issues with Unity crashes in the version we used to build most recent patch.
However this one looks different and if you look at above dlls causing the issue,
you see AMD specific drivers involved, which suggests an issue with your graphics drivers which obviously did crash.
"AmdLiquidVrD3D11WrapDeviceContext" do you even use LiquidVR ?
You might want to check if your graphics card settings are correct and maybe try to reinstall/update the drivers.

Cheers

This issue has been already fixed internally and the fix will be included in coming Patch v1.4.2.
Thanks for reporting anyway :)

We did update CoherentUI to the newest version internally and will be releasing a new patch containing it soon.
We hope this will fix these issues for you guys.

I thought this one would be fixed but I encountered it myself again.
Seems to kind of always happen when loading a save game.