test content
What is the Arc Client?
Install Arc

Game Client Crash

imcguigaimcguiga Member Posts: 44 Arc User
edited November 2014 in PC Gameplay Bug Reports
Over the past few days I've been seeing a lot of game crashing. This is the first week I've seen this type of problem. At first I thought it was heat related or a problem with memory. However I'e rebooted this morning and have only been playing for about an hour and I've had another crash. There are no messages from the game client. I get a Windows popup that the grame client has crashed and it is looking for a solution. Running Windows Vista Home Premium Service Pack 2 on an Asus Desktop Intel i7 920 2.67GH with 9GB Ram.

I have not been able to determine a pattern with the crashes but they do seem to happen more often in a Queued event. However I have had them while traveling in Sector Space.
Post edited by imcguiga on

Comments

  • czertik123czertik123 Member Posts: 1,122 Arc User
    edited November 2014
    problem is that cryptick - as allways - fuc**ed up game code so you have crashes, sometiems i have 3x cdt in 2 mins.
    after dr relase i have in averag 2x more cdt than before.
  • kthangkthang Member Posts: 172 Arc User
    edited November 2014
    You can check the Event Viewer, system tool, to see what Exception Code it crashed with. I would not be surprised if it said 0xc0000374 which is STATUS_HEAP_CORRUPTION. A quite common source of crash, and yes it's a coding error.

    If so, it seems to be related to how the game interacts with the GFX-drivers, and if you get the attention of support they'll take you through a song and dance about installing/re-installing/updating drivers and possibly re-installing Windows if you're really lucky. If it is indeed "confirmed" that it may be due to interaction with GFX-drivers, AMD/nVidia will be blamed when in fact these CTDs have been around for ages and through countless driver versions. That will be ignored though.

    I am appalled at all the bugs this game has accumulated through the years that were never ironed out. It seems, however, that it is slowly dawning on the people in charge but I wonder if it is too little too late. It starts innocently enough, with some small bugs that seems harmless. Displays things incorrectly, perhaps. No biggie, work on. Then things gets referenced, a coder gets a new job and the new guy gets thrown in to it, something new happens and the new guy has no clue how to find that small typo in tens of thousands of lines of code. In the end you'll have intertwining bugs. Bugs that interact, so to speak, and make things a lot worse.

    What they should do, no, need to do is to announce a total rewrite of the game-client. From the bottom up. But yeah, that's not going to happen any time soon although one can always hold out hope. If nothing is done, and you can bookmark this post for posterity, is that one day this game will simply stop working. Seems harsh? It ain't, one day all the bugs have accumulated to such a degree that some part of the game does not work and people will have a fit. Devs too.

    Personally I do not think it's the dev's fault or intention, not at all. There are people that want cash from this machine. Is the cost of repairing something higher than the income you get until something just stops then they won't let people do it.
  • imcguigaimcguiga Member Posts: 44 Arc User
    edited November 2014
    Problem happened again. Event Viewer shows the following for today from the most current.

    Faulting application GameClient.exe, version 0.0.0.0, time stamp 0x5473d524, faulting module ntdll.dll, version 6.0.6002.18541, time stamp 0x4ec3e39f, exception code 0xc0000374, fault offset 0x000abc4f, process id 0x18f0, application start time 0x01d00a6c72ab5080.

    Faulting application GameClient.exe, version 0.0.0.0, time stamp 0x5473d524, faulting module ntdll.dll, version 6.0.6002.18541, time stamp 0x4ec3e39f, exception code 0xc0000374, fault offset 0x000abc4f, process id 0x1678, application start time 0x01d00a5b7f608cc0.

    Faulting application GameClient.exe, version 0.0.0.0, time stamp 0x5473d524, faulting module ntdll.dll, version 6.0.6002.18541, time stamp 0x4ec3e39f, exception code 0xc0000374, fault offset 0x000abc4f, process id 0x1c3c, application start time 0x01d00a4de90a99d0.
  • imcguigaimcguiga Member Posts: 44 Arc User
    edited November 2014
    kthang wrote: »
    You can check the Event Viewer, system tool, to see what Exception Code it crashed with. I would not be surprised if it said 0xc0000374 which is STATUS_HEAP_CORRUPTION. A quite common source of crash, and yes it's a coding error.

    If so, it seems to be related to how the game interacts with the GFX-drivers, and if you get the attention of support they'll take you through a song and dance about installing/re-installing/updating drivers and possibly re-installing Windows if you're really lucky. If it is indeed "confirmed" that it may be due to interaction with GFX-drivers, AMD/nVidia will be blamed when in fact these CTDs have been around for ages and through countless driver versions. That will be ignored though.

    I'll look into updating drivers.
    kthang wrote: »
    I am appalled at all the bugs this game has accumulated through the years that were never ironed out. It seems, however, that it is slowly dawning on the people in charge but I wonder if it is too little too late. It starts innocently enough, with some small bugs that seems harmless. Displays things incorrectly, perhaps. No biggie, work on. Then things gets referenced, a coder gets a new job and the new guy gets thrown in to it, something new happens and the new guy has no clue how to find that small typo in tens of thousands of lines of code. In the end you'll have intertwining bugs. Bugs that interact, so to speak, and make things a lot worse.

    It's not that they are ignored, it's that they have a lower priority than other items on the development list. A fix and new content may have require the same amount of development time. But the new content gets higher priority unless the bug hits a majority of the players. It's the reality of development. We never have enough time or resources to do what we want.
    kthang wrote: »
    What they should do, no, need to do is to announce a total rewrite of the game-client. From the bottom up. But yeah, that's not going to happen any time soon although one can always hold out hope. If nothing is done, and you can bookmark this post for posterity, is that one day this game will simply stop working. Seems harsh? It ain't, one day all the bugs have accumulated to such a degree that some part of the game does not work and people will have a fit. Devs too.

    A rewrite is not realistic. A lot of shops are going Agile (new development method) and even if they weren't a rewrite is years of man hours and not something that would be in this products life cycle.
    kthang wrote: »
    Personally I do not think it's the dev's fault or intention, not at all. There are people that want cash from this machine. Is the cost of repairing something higher than the income you get until something just stops then they won't let people do it.

    Not looking to place blame. Placing blame has never fixed a problem, just redirected management to yell at someone else. I just want to get this fixed as it's frustrating to be in the middle of a cut scene or mission and suddenly have to restart the application.
Sign In or Register to comment.