Are unhandled exception errors software problems or hardware problems or could it be either?

I've gotten the following error three times:

EXCEPTION_ACCESS_VIOLATION (0xc0000005) at address 0x18016432
    attempted to read memory at 0x0010d94c.

To my recollection, the "attempted to read memory" address was exactly the same each of the three times.

Does this mean I have bad RAM?

Here's the rest of the 100 line log from the most recent incident:

EXCEPTION_ACCESS_VIOLATION (0xc0000005) at address 0x18016432
    attempted to read memory at 0x0010d94c

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

Callstack:
 RADTimerRead + 15330 bytes ((Unknown)(0) + 0 bytes)

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: Can't use \000HEPA01VenomSpit04
info: Can't use \000HEPA01VenomSpit04
info: Can't use \000HEPA01VenomSpit04
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 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: Removing upgrade [CBuildingHealth03]
info: ARMY1_1 Adding upgrade [CBuildingHealth04]
warning: hgsa01 can't use ability HGSA01ShrapnelMine01 because of \000{ Disabled=true }
warning: Error running /lua/sim/tasks/AbilityTask.lua script in CScriptObject at 346eb870: ...dock games\demigod\dgdata.zip\lua\sim\scripttask.lua(74): ScriptTask.TaskTick called. Did you forget to add TaskName to your command lua param table?
         stack traceback:
          [C]: in function `error'
          ...dock games\demigod\dgdata.zip\lua\sim\scripttask.lua(74): in function <...dock games\demigod\dgdata.zip\lua\sim\scripttask.lua:72>
info: ARMY2_1 Adding upgrade [CTroopNumber06]
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
debug: Loading module '\000/units/reinforcements/rgiant/rgiant01_script.lua\000'
info: Removing upgrade [CBuildingHealth03]
info: ARMY2_2 Adding upgrade [CBuildingHealth04]
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: Can't use \000HEPA01VenomSpit04
info: If we are trying to attack our current target, ignore the new request
info: Can't use \000HEPA01VenomSpit04
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 '14.000000'
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: Can't use \000HEPA01VenomSpit04
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: ARMY1_2 Adding upgrade [CTroopNumber05]
info: ARMY1_2 Adding upgrade [CTroopNumber04]
info: Can't use \000HEPA01VenomSpit04
info: If we are trying to attack our current target, ignore the new request
info: Removing upgrade [CTroopStrength02]
info: ARMY2_2 Adding upgrade [CTroopStrength03]
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 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
warning: Attempt to buy invalid item
warning: Unit = \0002097152
warning: Attempt to buy invalid item
warning: Unit = \0002097152
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 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 our current target, ignore the new request
info: Can't use \000HEPA01VenomSpit04
info: If we are trying to attack our current target, ignore the new request

-Kris

 

592 views 2 replies
Reply #1 Top

I was wrong about one thing--it turns out it wasn't the same memory address each time.

Reply #2 Top

It's unlikely that you have bad memory.  Demigod should generate a mindump.dmp file in your My Documents\My Games\Gas Powered Games\Demigod folder.  If you zip that and send it with the DemigodLog.txt, (and ImpulseReactor.log if it happens while in the lobby) to [email protected] we can forward it on to GPG to take a look at.