Game won't launch at startup

Summary:

Just downloaded the game on steam and tried to run it after download. And the game won’t launch with a windows crash window “Stonehearth has stopped working”.

Here is the detailed report:
Problem signature:
Problem Event Name: APPCRASH
Application Name: Stonehearth.exe
Application Version: 0.18.0.663
Application Timestamp: 57e2f2cb
Fault Module Name: atio6axx.dll
Fault Module Version: 6.14.10.12337
Fault Module Timestamp: 52202fcc
Exception Code: c0000005
Exception Offset: 0000000000a34bc1
OS Version: 6.3.9600.2.0.0.256.48
Locale ID: 1033
Additional Information 1: d414
Additional Information 2: d414d52713c282c56000d176db9f89fb
Additional Information 3: 2856
Additional Information 4: 2856881de00cfb181cc66c7a753bc201

Stonehearth.log:

2016-10-18 22:11:33.777011 | server | 1 | app | Stonehearth Version 0.18.0.663 (x64)
2016-10-18 22:11:33.780012 | server | 1 | core.config | user id is 5474dc46-9532-11e6-af78-4851b752c86b
2016-10-18 22:11:33.780012 | server | 1 | core.config | session id is c63b4c48-953c-11e6-89bc-4851b752c86b
2016-10-18 22:11:33.785013 | server | 0 | core.system | Initializing crash reporter
2016-10-18 22:11:33.785013 | server | 0 | lua.code | lua jit disabled in 64-bit builds. set force_lua_jit to override
2016-10-18 22:11:33.790013 | server | 0 | lua.data | lua jit is disabled
2016-10-18 22:11:33.831015 | server | 1 | resources | Module rayyas_children_ui version 3 is deferred load)
2016-10-18 22:11:38.643327 | server | 1 | resources | Modules are verified pristine.
2016-10-18 22:11:38.699326 | server | 1 | app | Running Stonehearth server on port 13755
2016-10-18 22:11:38.699326 | client | 1 | renderer.renderer | Initializing OpenGL
2016-10-18 22:11:38.699326 | server | 0 | physics.navgrid | subspace pathfinder is enabled
2016-10-18 22:11:38.705327 | client | 1 | renderer.renderer | Determining window placement
2016-10-18 22:11:38.705327 | client | 1 | renderer.renderer | Selecting monitor at 8, 52
2016-10-18 22:11:38.705327 | client | 1 | renderer.renderer | Creating OpenGL Window
2016-10-18 22:11:38.733298 | server | 1 | mod radiant | lua controller lifetime tracking set to "nil"
2016-10-18 22:11:38.768330 | server | 0 | mod stonehearth.ai.service | [] enable_cpp_compound_action is on
2016-10-18 22:11:39.021348 | server | 1 | lua.memory | lua shared heap size: 8.084 MB.
2016-10-18 22:11:39.021348 | server | 1 | lua.memory | o: outstanding allocs
2016-10-18 22:11:39.021348 | server | 1 | lua.memory | 64 bytes (o: 13108) : ########################################
2016-10-18 22:11:39.021348 | server | 1 | lua.memory | 40 bytes (o: 9827) : #############################
2016-10-18 22:11:39.021348 | server | 1 | lua.memory | 48 bytes (o: 5560) : ################
2016-10-18 22:11:39.021348 | server | 1 | lua.memory | 72 bytes (o: 3036) : #########
2016-10-18 22:11:39.021348 | server | 1 | lua.memory | … remaining allocs are each < 5% of the count
2016-10-18 22:14:22.970704 | server | 1 | lua.memory | lua shared heap size: 8.084 MB.
2016-10-18 22:14:22.971719 | server | 1 | lua.memory | o: outstanding allocs
2016-10-18 22:14:22.971719 | server | 1 | lua.memory | 64 bytes (o: 13108) : ########################################
2016-10-18 22:14:22.971719 | server | 1 | lua.memory | 40 bytes (o: 9827) : #############################
2016-10-18 22:14:22.971719 | server | 1 | lua.memory | 48 bytes (o: 5560) : ################
2016-10-18 22:14:22.971719 | server | 1 | lua.memory | 72 bytes (o: 3036) : #########
2016-10-18 22:14:22.971719 | server | 1 | lua.memory | … remaining allocs are each < 5% of the count

Attachments:

There seems to be no crash.dmp file in my installation directory.

Versions and Mods:

Stonehearth Version 0.18.0.663 (x64)
No mods installed

System Information:

Windows 8.1
AMD A10-6790k APU with AMD Radeon HD670D
Radeon R7 200 series GPU (also tried running with dual graphics off)

Have you attempted basic troubleshooting steps here: http://discourse.stonehearth.net/t/crashing-on-start-read-this-updated-october-28/13297:

Tried every fix I could find. Updated drivers, modifying the user_settings.json, running on administrator and compatibility mode. And I don’t have any of the problem 3rd party apps installed.

Hi @junec , sorry to hear you’re having problems.

I was going to suggest deleting manually the game’s folder and reinstalling, but then I saw this:

This seems related to graphics (in your log I don’t see that the OpenGL context has finished initialization, and cef also didn’t get to start).

Did you update your drivers from here: Desktop or did you use an auto-updater?

Did you try running in windowed and fullscreen modes (you can switch between them in the user_settings.json) ?

Yes, any kind of booster or more than one card can cause problems. In the past there have been users that had trouble getting the game to pick/use the card they wanted. Not sure how to troubleshoot that for AMD…

Edit: @junec, did you try the recent workaround of resetting the firewall etc via these commands? :

netsh advfirewall reset

netsh int ip reset c:\resetlog.txt

netsh winsock reset

Also disabling analytics, just in case…

1 Like

Yes, updated my drivers via all three ways I could find. Windows automatic update, AMD’s auto detector, and manual download. Nothing worked, and for some reason, when I used the auto detector and manual download. I got a warning of graphics card incompatibility, which is weird though, as it’s clearly stated in the download page that my hardware is compatible with the driver. But I tried it anyway and installed the driver, which didn’t do anything besides crash my amd catalyst. :dizzy_face:

Yes, I also tried resetting the firewall as you’ve stated and doing a reinstall and local file integrity check for steam.

What did you mean by ‘disabling analytics’ though?

Just figured out the issue. The problem was with the AMD drivers. Seems that they have a history of corrupt OpenGL files. So I just got myself a copy of the last working dll files from an old version amd driver and used that to replace the ones I have now. I can finally play the game! Yeeeessss! hahahaha.

Here is the link to the thread in the AMD forum where I found the fix.
https://community.amd.com/thread/194721

2 Likes

Awesome, glad you found the issue, and thanks for sharing the solution!

1 Like