Guild Wars 2

Most likely caused by a null pointer somewhere in the game code by the looks of it:
http://www.windowsbbs.com/legacy-windows-os/40538-what-causes-exception-code-c0000005-access_violation.html

Kalec.6589:

Exception: c0000005 is not only with GW2. It is a conflict in your system. This code happens in others games and software.

not nessecarily. It is true that this error happens in other games and software, but thats because its a general error code that any program could throw (given the right set of bugs and glitches). If its only occuring in this game then its highly unlikely that its a problem with the system.

VirtualBS: You need to understand that this crash often locks up the computer before it is able to throw a blue screen, as illustrated by my issues and skeletank or create a minidump.

Quite often there is no stop code for us to diagnose with or dump to run bluescreen view with.

Im still hoping a dev will weigh in on this topic.

Also on a lighter, humerous sidenote. A Tech support rep recently misunderstood the specy report I sent them by mixing up the frequency on my stock clocked ram with my processor; claiming that my i7-2600k was overclocked from 833mhz to 1066 and that this was causing my crashing.

That doesnt seem right does it?

Hey guys

Considering the fact that Anet have been fairly tight lipped on this subject and some users have been copy pasting the same tips to no avail I thought I might open up a discussion regarding this glitch.

The problem I refer to is the frequent crashing of the games client on some users machine resulting in

• Black screens
• Frozen screens with lines
• BSOD errors
• Looping sound
• and ultimatly forced hard reseting of the users computer.

The general consensus from forum users not experiencing the problem is to blame it on the users computer configuration, whether it be out of date drivers, bad copies of windows e.g.32 bit or faulty parts.

Personally I dispute this diagnosis as

• The problem seems equally spread out between 64 and 32 bit users
• Most, if not all, of the users experiencing the problems are running the latest bios and drivers (12.8 catalyst with latest profiles or the Nvidia beta)
• Most users are playing on fairly new, high end computers. This is important because the likely hood of so many people , relitivly new, video cards failing is low
• Most users do not or currently are not overclocking (A good recomendation alas)
• Some users that have actually bought new hardware (Ive read about a couple of peope buying completly new ram kits and cards) are still experiencing problems.
• Very few of the victims are anywhere near approaching temperatures where safety shutoffs and faults are expected
• This is their only failing game (More intensive games such as BF3 and D3 seem to continue running)

While many reccomnendations provided are commensense and realistic, given the number of users experiencing the problem it is much more likely this is an engine problem, and given that is seems somewhat dependant on graphics quality, possibly a memory leak of some variety.

This would be acceptable if such an issue was aknowledged by the devs but instead many of us are left with no eta on a fix and a broken, semi-unplayable at times, piece of two week old software.

I do not dispute that this post is a less than balanced look at the issue, being a victim myself, but I would like to start a conversation with you guys so we can form a better understanding of the issue and the circumstances. I am more than curious to hear rebutals from those who believe and can prove a relation to individuals hardware and the problem.

I would love a response from the devs, but their replies seem sparse in this forum at the present time (a search of the last 4 pages of dev replies yielded aprox 3. in this forum) so we’ll see.

/Tsu

that felt good to get out

Perhaps this is a lower priority problem than hacking because crashing clients can still make microtransactions, hacked accounts cant.

Christ can people stop blaming this on out of date drivers and overclocking?
After reading god knows how many of these threads (and being a current victim myself) a couple of things are obvious:
1. Its not a 32bit windows problem as there are many 64bit users having the same problem
2. Its not an OC or temp problem. Those who have overclocked are as affected equally as much as those at regular clock speeds. And almost no one Ive seen has claimed any temp values outside the norm.
3. Its not out of date drivers or BIOS. 99% of people have been running the latest drivers and still encounter this error. It is possible a new driver will fix it but there isnt one.
4. Its not dodgy or outdated graphics cards. These people can still max other intensive games such as BF3 and benchmarks like Unigine

Their advice for turning of AA in CCC would be great if that option still existed in the latest builds. Also the troubleshooting exe they are sending round would also be a wonderful idea if it actually was built for GW2 or could locate it. I take that last comment back, their latest game advisor build seems to ahve fixed this problem.

The one thing common between all those experiencing this problem is simpy the fact that they run the game. And Arenanets unwillingness to aknowledge the problem is really starting to get on my nerves. I didnt pay $80 bucks for a broken piece of software. Nor will I stand for this weak attempt of tech support that they are offering currently.

I understand that they are busy with bots, gold sellers and hackers and thats fine. I would just like an aknowledgement of the problem by them.