Game Crashed

[magic1313]

Game Crashed after Victory against excavation bot

Error Log

Unity Player [version: Unity 5.2.3p3_383123ade41b]

mono.dll caused an Access Violation (0xc0000005)
in module mono.dll at 0023:101195ba.

Error occurred at 2016-01-27_233454.
C:\Program Files (x86)\Hex\Hex.exe
93% memory in use.
0 MB physical memory [398 MB free].
0 MB paging file [0 MB free].
0 MB user address space [124 MB free].
Write to location 00200000 caused an access violation.

There is more to error log but too large to post.

[Valnir]

Hi!
Few of us have similar problems
I personally have exactly the same except it happens after nearly every game.

http://forums.cryptozoic.com/showthread.php?t=47344

[Phenteo]

Are you both on Windows 10?

[dbug]

I have this error to and i am on Windows 10 Pro 64bit

[Valnir]

Win XP SP3

[Phenteo]

A player reported that they were able to fix the issue in windows 10. They had to enter their computer bios and change their ram settings from default to the speed of the ram. Example: If your ram is 1600 MHz, but your system is set you default at 1333MHz you can change it to 1600 to resolve the issue.

Hope this helps!

[Valnir]

Seems It solved the problem, now Im trying to get the resolution back to max and testing it.
Thank you Phenteo!

Time for some some real PVE experience!

[magic1313]

I am windows 7 SP1

[Valnir]

Seems It solved the problem, now Im trying to get the resolution back to max and testing it.
Thank you Phenteo!

Time for some some real PVE experience!

Unfortunately I was wrong.. the problem still exists..

In dungeon everything works fine and fast (max resolution, ram speed set) , but it still crashes after victory screen when a single encounter is done at the AZ

[Angsar]

Valnir, could you go into event viewer in windows and see what is causing this issue?

Type in event viewer in the start menu if you are on Windows 10.

Windows Logs -> Application Check for the error message that crashed hex.

You will get a lot of rows with text that contains hex.exe version etc.

What I am interested in here is what's under the "faulting module path".
Is it ntdll.dll ?

If that is the case there's a couple of things that could be causing it.
For me it was my memory that needed to be clocked to the correct speed.

ntdll.dll often tells you that there's something wrong with privileges.
What i've found so far that might cause the crashes are these:

1. Incorrect memory clock settings in bios.
2. Hard drive issues.
3. UAC Settings in Windows 10.
4. DEP (Data enforced Protection)

Solution:
1. Turn up your memory to the correct clock, worked wonders for me.
2. Try installing HEX on a different hard drive, may even work on an external one. Before you do this, make sure you have deleted hex from your registry as well.
3. If I am not mistaken I was recommended to put UAC second from the bottom by a NOBLE. I usually run my windows without UAC (bottom).
4. I have not found a solution to this. It's more related to UNITY engine in Windows 10 than to HEX itself. This is a long shot.

If you find yourself fixing your crashes I would be more than happy to hear about it.
I have found a couple of users on Windows 10 that has occuring crashes as issues and it would be lovely to gather as much data as possible to forward to support / phenteo to get to the developers.

Kind regards,
Ansgar