Jump to content

flanagak

Members
  • Posts

    14
  • Joined

  • Last visited

Posts posted by flanagak

  1. Hello all,

    Im new to the server and saw the Login server crashed again today.
    So I was reading the forums and found this.

    Thought I might be able to help resolve this.

    <quote>Unhandled exception at 0x0044cee2 in login_server.exe: 0xC0000005: Access violation writing location 0x04e04000.</quote>

    1st thing to note: 0xC0000005 = Memory Heap Corruption.

    This also means that most likley your stack is also going to be corrupted and may not point to the correct methods in your stack trace.

    The key to debugging heap corruptions is that we need to get a memory dump just before it gets corrupted.

    That way you can look at the stack at that point in time and see what is being called.

    Here is a link that explains how to setup Application Verify as well as Debug Diag in order to generate a memory dump just prior to the exception.

    http://blogs.msdn.com/b/lagdas/archive/2008/06/24/debugging-heap-corruption-with-application-verifier-and-debugdiag.aspx

    Once you have the memory dump and App Verify data we can trace down the cause of the issue.

    FYI: Running Debug Diag and App Verify on the process will cause it to consume a lot more memory during execution.

    Hopefully you have plenty in the sever. :D

    --flanagak--

    In Game: Rune

    • Like 1
×
×
  • Create New...