Guild Wars 2

Ever since Hot came out every time i get to place were there are more ppl doing something my game crashes … did not happen before hot and chanceing craphics to lowest does not chance enyfing otherwise game runs on 80 to 90 fps on max settings nicely . there was event were game crashd after 3 seconds i log in for 10 times.

I heard rumor its beacose of login server my region is in I’m from Estonia and i heard we are hosted by france??? dunoo

Likewise, my game keeps crashing constantly, esp. on full maps. These crashes would only be a minor annoyance if gw2 did actually function like most other mmorpgs and I would retain my spot (and position) on the map, unfortunately this isn’t the case here and I keep losing lots of time and progression because I’m denied boss kills etc. whenever the client dies.

Had no such problems prior to HoT.

Crashing here more and more on HOT. (Never crashed before hot).

Started off about once an hour (Acceptable after a launch) but now it’s every few minutes and getting unplayable.

Generally when I’m doing something with other people, like the planting eggs thing, so I either log back in dead or the events over and no rewards for me.

Very frustrating.

i found that everyting is fine until there is less than 15 ppl fighting around you if there is more than i crash so i ceep my distance from world events

I am encountering this every time I go to a world boss now. Tried twice now to get the new title/achieve for karka queen; crashed both times soon as fighting started, and by the time I get back in, it’s over, so zero credit (since I’m not even able to get in to get a few hits in). I’ve been running all bosses with no issues with the exception of a handful of Tequatl tries (but at least there in all but one of those cases, I crashed early enough in the fight and was partied with a friend that I was able to get back in, or I simply jumped into a Teq taxi group to get out of overflow server).

I’ve had two karka queen tries, two to three Teq kills, 1 Golem Mark II kill and 1-2 other bosses where I’ve crashed but got back in time to still get credit.

Having the same issue the most extreme being that I just crashed on the Mouth of Mordremoth at 25% on TTS’s first kill :S (200% Map Participation)

It seems to happen whenever a big event/large groups of people begin preforming skills/actions at once in PvE/WvW. Never had this issue to this degree before the expansion.

Yeah I’ve been crashing quite a bit in HoT as well. Which is funny since I used to hate LA because I would crash every so often, but now I’d crash within 30 mins of trying to do stuff in HoT. Usually right when I’m in the middle of trying to get exp during a world event. It’s pretty annoying.

I’m having exactly the same problem, anyone heard an update?

OOM error.. check your anet log.

This is common atm although they refuse to even admit there is a problem

is there a quick fix for OOM errors atm to work around this?

coque.3750:

is there a quick fix for OOM errors atm to work around this?

Yes .. has been posted 1000 times, but people are not willing to use it.

Set character model limit and quality to medium .. if thats not enough to minimum.

Also if you know you will be longer in a big zone for something like Tequatl it could
help to restart your client after entering the zone to avoid memory fragmentation.

http://stackoverflow.com/questions/3770457/what-is-memory-fragmentation

I’ve set everything on low and still receive these crashes. I’m not sure if it’s the same as others but i’ve had crashes where I am the only person around these crashes only occur in heart of thorns areas. I’ve got a 660ti sc/i7-2600k @4.5ghz/8gb ddr3 ram.

RoRo.8270:

I’ve set everything on low and still receive these crashes. I’m not sure if it’s the same as others but i’ve had crashes where I am the only person around these crashes only occur in heart of thorns areas. I’ve got a 660ti sc/i7-2600k @4.5ghz/8gb ddr3 ram.

1. You should ofc have 64-bit Windows, since under 32-bit the client already crashes
on half the amount of memory than on 64-bit Win

2. take a look into / post your crash-log to see if its an OOM (out of memory) crash
or something else.