Hi! I uninstalled and reinstalled Endless Legend and the game is not starting up. It opens up in windowed mode and and goes through the routine up to the Endless Legend logo prior to the intro clip, then crashes. I verified the game cache and reinstalled the game, and have gone through the common issues to try and resolve the matter. The game has given me several files to forward:

crash.dmp  output_log.txt  error.log

2016-10-08_134044.7z - Endless Legend Crash Report

Please excuse me as I am not the most computer-savvy. Above are the three files I have been sent, if they do not work the one below is the 7Zip file. I hope this is alright.

In terms of specs I am not running anything advanced. 

I am running Windows 10, with a 64bit operating system, I have all the DLC and am on the latest version of the game. If there is anything more you need, let me know what I can do.

Thankyou.

    Just wanted to throw my two cents in that I am having what sounds like the same problem as OP.  In fact I was able to play as recently as couple days ago and the only change to my system was the Tempest update.  I've tried the same intital attempts to fix: verify cache, run as admin, run in compatibility mode, disable anti-virus, reinstall vcredists, all to no avail.  I'm going to assume something in the last DLC update impacted my hardware config since I don't see many people either here or on steam complaining.  Guess I'll just be waiting for a patch fix?

I'm going to toss my $.02 in.

It looks like even your log file is corrupted. I'm going to take a guess that you've developed a RAM problem.

EndlessLegend.exe caused an Access Violation (0xc0000005)

in module EndlessLegend.exe at 0033:10b7b69b.

Error occurred at 2016-10-08_134046.

C:\Program Files (x86)\Steam\SteamApps\common\Endless Legend\EndlessLegend.exe, run by Ethan.

56% memory in use.

8085 MB physical memory [3479 MB free].

9365 MB paging file [4337 MB free].

134217728 MB user address space [134217535 MB free].

Read from location 00000010 caused an access violation.

Access violation could definitely mean a bad RAM module.

I think @werewolf_nr is right.

Could you try running MemTest and see whether it detects some issues with your RAM?