"Memory could not be read" crash at deconstructing

Discussion in 'Support' started by Mr Burns, Apr 24, 2010.

Thread Status:
Not open for further replies.
  1. Mr Burns

    Mr Burns Member

    Messages:
    9
    Likes Received:
    0
    Trophy Points:
    0
    Each time I try to decon some enemy stuff with my engie tool I get this crash
    "blabla memory error at blabla, memory could not be read, click OK to terminate the program"
    actually, I was getting it a lot, searched for a solution, typed "+mat_forcehardwaresync 0 +snd_async_prefetch_priority" in launch options and that problem is solved except for when deconstructing.

    any help with that?

    edit: also noticed that I can watch other people deconstruct without crashing

    crash logs:
     

    Attached Files:

    Last edited: Apr 24, 2010
  2. Brutos

    Brutos Administrator Staff Member Moderator

    Messages:
    3,385
    Likes Received:
    0
    Trophy Points:
    0
    Are using the default particles?
     
  3. Mr Burns

    Mr Burns Member

    Messages:
    9
    Likes Received:
    0
    Trophy Points:
    0
    if default means that I didnt change anything then yes
    but
    I have no idea why, particles dont show up most of the time, sometimes they do, not very often though
    usually I see only APC grenades

    console screen:
     

    Attached Files:

  4. Empty

    Empty Member

    Messages:
    14,912
    Likes Received:
    11
    Trophy Points:
    0
    lmao.
    you're only missing every fucking effect in the game.
     
  5. Mr Burns

    Mr Burns Member

    Messages:
    9
    Likes Received:
    0
    Trophy Points:
    0
    ye lol, but this way I can at least play it
     
  6. Empty

    Empty Member

    Messages:
    14,912
    Likes Received:
    11
    Trophy Points:
    0
    Well this is pretty damn obvious what the problem is.

    Locking thread.
     
  7. MOOtant

    MOOtant Member

    Messages:
    4,047
    Likes Received:
    0
    Trophy Points:
    0
    Crash fixed in 2.25b.
     
Thread Status:
Not open for further replies.

Share This Page