Search
Forum Home | Login
PsychoPif
PsychoPif
Join Date 04/2009
0

Crash

June 29, 2009 1:16:43 AM from Demigod ForumsDemigod Forums

I crash in the middle of a 5v5 game.

EXCEPTION_ACCESS_VIOLATION (0xc0000005) at address 0x775ae599
    attempted to write memory at 0x8bc44d93

Program : Z:\Stardock Games\Demigod\bin\Demigod.exe
Cmd line arguments :

Callstack:
    RtlLeaveCriticalSection + 9 bytes ((Unknown)(0) + 0 bytes)

Reactor version: 1.00.56
Demigod version MAIN.1.10.0146
Last 100 lines of log...

A full record of the log is stored in the Demigodlog.txt file

info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to guard ourselves, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
debug: Loading module '\000/lua/user/powerupaction.lua\000'
info: Setting audio parameter 'WARSCORE' to value '4.000000'
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: Can't use \000HQueenBrambleShield02
info: If we are trying to guard ourselves, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to guard ourselves, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: Setting audio parameter 'LEVEL' to value '6.000000'
info: If we are trying to guard ourselves, ignore the new request
info: If we are trying to guard ourselves, ignore the new request
info: If we are trying to guard someone guarding us, ignore the new request
info: If we are trying to guard ourselves, ignore the new request
info: Sim crashed hard in DoSimBeat(): ...\demigod\dgdata.zip\lua\ui\game\hud_msgs_failure.lua(20): attempt to call method `SetText' (a nil value)
      stack traceback:
          ...\demigod\dgdata.zip\lua\ui\game\hud_msgs_failure.lua(20): in function <...\demigod\dgdata.zip\lua\ui\game\hud_msgs_failure.lua:19>
          ...ames\demigod\dgdata.zip\lua\common\validateskill.lua(21): in function <...ames\demigod\dgdata.zip\lua\common\validateskill.lua:17>
          ...\stardock games\demigod\dgdata.zip\lua\sim\skill.lua(118): in function <...\stardock games\demigod\dgdata.zip\lua\sim\skill.lua:116>

Locked Post
Search this post
Advanced Search
Subscription Options
Reason for Karma (Optional)
Successfully updated karma reason!
PsychoPif
mesasone
Join Date 02/2008
0
Reply #1 June 29, 2009 1:26:09 AM
from Demigod ForumsDemigod Forums

We were having mega crashes tonight, we had about 5-6 people on vent playing DG and I would say we expeirenced 20 crashes over a few hours between the lot of us.  Several times 2-3 would crash at the same time in the same game.  It is very annoying and has friends looking for alternatives to Demigod, which is unfortunate because we really like this game when it works.

 

Also, there seemed to be some network issues - lag in games with high sim speeds and good pings.  Not sure what caused it.

Reason for Karma (Optional)
Successfully updated karma reason!
PsychoPif
kryo
Join Date 05/2003
+458 sdemployee
Reply #2 June 29, 2009 1:08:55 PM
from Demigod ForumsDemigod Forums

For any crash, please check if it created a .dmp file in My Documents\My Games\Gas Powered Games\Demigod. If it did, please send that file and your demigodlog.txt to support@stardock.com so they can pass it to the devs.

Reason for Karma (Optional)
Successfully updated karma reason!
PsychoPif
PsychoPif
Join Date 04/2009
0
Reply #3 June 29, 2009 6:37:08 PM
from Demigod ForumsDemigod Forums

Thanks, I think this adresse is gonna be my new favorite cause I've been crashing all weekend...

Reason for Karma (Optional)
Successfully updated karma reason!
View all recent posts
Mark all posts as read Delete cookies created by the forum Return to Top
Stardock Forums v        Server Load Time:   Page Render Time:

Stardock Magazine | Register | Online Privacy Policy | Terms of Use

Copyright © 2025 Stardock Entertainment and Gas Powered Games. Demigod is a trademark of Stardock. All rights reserved. All other trademarks and copyrights are the properties of their respective owners. Windows, the Windows Vista Start button and Xbox 360 are trademarks of the Microsoft group of companies, and 'Games for Windows' and the Windows Vista Start button logo are used under license from Microsoft. � 2012 Advanced Micro Devices, Inc. All rights reserved. AMD, the AMD Arrow logo and combinations thereof are trademarks of Advanced Micro Devices, Inc.