Curse

Lady Aranza · Mar 10, 2011, 07:08 AM // 07:08

There seems to be a problem since this update. It doesn't happen all the time, but sometimes in the middle of a vanquish or a mission the game suddenly freezes with a ping of 700ms to 2 seconds or more and an FPS of 1 or 2. After waiting for several minutes, things go back to normal. It is not only the current Zaishen Mission or Vanquish, it happens also on other missions. There is no disconnect though. I am usually on International English districts when I start my missions/vanqs. I went to Europe English yesterday but that didn't help. Is this happening to anyone else? Is this maybe because so many more players are now playing the game?

I am playing on a borrowed older notebook (mine is in repair) with WinXP. Before the update, the playing went fairly smooth. I have installed and tried Game Booster already but it didn't help. The only other program that is open is the Firefox browser. Closing the browser doesn't help with the problem either. In the task list, I cannot see any other activities, so it's not a virus scan or something like that. Before the update, this just did not happen.

LocoStar · Mar 10, 2011, 08:45 AM // 08:45

It happens also in PvP areas. Sometimes I got 2 sec pings or even lagss with green dot too. Every few days also happens some conection errors like 007 or 040 when we switching district in Heroe's Ascent. It happens almost everyday since the update.

Tallonz · Mar 10, 2011, 10:59 AM // 10:59

I have returned after a year off and am suddenly getting freeze after about 5mins and then get the disconnected message with error=007.

I ran a trace route and a constant ping and all was OK so I thought why not reinstall and no luck still I am getting 007 .... Oh and yes I defragged as well

I will try again tomorrow .... it would be a shame if this keeps happening I was so looking forward to coming back

Iceblue · Mar 10, 2011, 03:06 PM // 15:06

Tallonz, you might have to do an update: http://wiki.guildwars.com/wiki/Command_line

-image

Forces the game to load all known updates.

* The program terminates after the update is completed; Guild Wars will not be able run with this parameter on.
o Recommended: Create an extra Guild Wars shortcut (e.g. "Guild Wars Updater") specifically to use this command line switch.
* -image updates gw.dat; after updating, that file can be be transferred over to other machines.
o There can be up to 4 gigabytes of data to download. Once -image completes, the exact file size of gw.dat will vary across installations.

Warbog The Slayer · Mar 10, 2011, 05:59 PM // 17:59

ye i have exactly the same problems gw is frezzing like 1 sec every 2 min then i am fine and sometimes when i zone after the login screen i get 1 or 2 fps and i need to w8 like 30-60 seconds until i can move

Kelfer · Mar 10, 2011, 06:00 PM // 18:00

/agree

I'm getting this too and as a regular player it's a pain frankly.

Btw No, -image doesn't improve anything

Chthon · Mar 10, 2011, 07:54 PM // 19:54

Pathping. Pathping. Pathping.
I should make sticky.

Could be a-net; could be your ISP; could be any one of a dozen+ intermediate nodes. "I get lag spikes" tells us nothing of any use in locating the cause of the problem.

Lord Dagon · Mar 10, 2011, 10:29 PM // 22:29

i was actually going to make a thread about this today, weird. But, yea ever since the embarkment beach update i've getting like 700s~33k(at its worst) ping since the update. Now, before the update i didnt have a ping to write home about(around 200~300ms)but the game ran smoothly and i had around 25~30fps. Now, without warning, i randomly just get huge spikes of lags. The longest was beening frozen on my screen for about 2mins during that mission in nightfall where you have to stop all command post before they see you.
So, in short, gameplay has become incredbily difficult because no one wants a person on their team with lag like this, and it really slows down my MQVQs that i like to do.

i have noticed tho that my lag seems to be worse when im in a party with one of my friends and their heros. It's also preety bad when alot is going on on my screen at any particular time.
I really hope they fix this. I havent made any changes to my computer or internet since embarkment beach so its 99% probable that its their fault.

Lady Aranza · Mar 12, 2011, 04:59 AM // 04:59

The problem persists...

Here is my pathping during a lag spike:

================================================== ============================
= Tracing network paths
================================================== ============================
*--> pathping -w 500 -q 3 -4 206.127.145.228 <--*

Routenverfolgung zu 206-127-145-228.plaync.com [206.127.145.228]
ber maximal 30 Abschnitte:
0 ahn0176delld600 [XXX.XXX.XXX.XXX]
1 fritz.fonwlan.box [XXX.XXX.XXX.XXX]
2 XXX.XXX.XXX.XXX
3 87.186.250.166
4 217.239.39.14
5 195.16.161.58
6 206-127-156-82.plaync.com [206.127.156.82]
7 206-127-145-228.plaync.com [206.127.145.228]

Berechnung der Statistiken dauert ca. 5 Sekunden...
Quelle zum Abs. Knoten/Verbindung
Abs. Zeit Verl./Ges.= % Verl./Ges.= % Adresse
0 ahn0176delld600 [XXX.XXX.XXX.XXX]
0/ 3 = 0% |
1 2ms 0/ 3 = 0% 0/ 3 = 0% fritz.fonwlan.box [XXX.XXX.XXX.XXX]
0/ 3 = 0% |
2 --- 3/ 3 =100% 3/ 3 =100% XXX.XXX.XXX.XXX
0/ 3 = 0% |
3 46ms 0/ 3 = 0% 0/ 3 = 0% 87.186.250.166
0/ 3 = 0% |
4 58ms 0/ 3 = 0% 0/ 3 = 0% 217.239.39.14
0/ 3 = 0% |
5 --- 3/ 3 =100% 3/ 3 =100% 195.16.161.58
0/ 3 = 0% |
6 --- 3/ 3 =100% 3/ 3 =100% 206-127-156-82.plaync.com [206.127.156.82]
0/ 3 = 0% |
7 55ms 0/ 3 = 0% 0/ 3 = 0% 206-127-145-228.plaync.com [206.127.145.228]

Ablaufverfolgung beendet.
*--> pathping -w 500 -q 3 -4 64.25.39.1 <--*

Routenverfolgung zu 64.25.39.1 ber maximal 30 Abschnitte

0 ahn0176delld600 [XXX.XXX.XXX.XXX]
1 fritz.fonwlan.box [XXX.XXX.XXX.XXX]
2 XXX.XXX.XXX.XXX
3 87.186.250.162
4 hh-eb5-i.HH.DE.NET.DTAG.DE [62.154.32.174]
5 62.157.249.78
6 ae-11-11.car1.Hamburg1.Level3.net [4.69.133.177]
7 ae-4-4.ebr1.Dusseldorf1.Level3.net [4.69.133.182]
8 ae-45-45.ebr2.Frankfurt1.Level3.net [4.69.143.166]
9 ae-44-44.ebr2.Washington1.Level3.net [4.69.137.62]
10 ae-82-82.csw3.Washington1.Level3.net [4.69.134.154]
11 ae-81-81.ebr1.Washington1.Level3.net [4.69.134.137]
12 ae-2-2.ebr3.Atlanta2.Level3.net [4.69.132.85]
13 ae-7-7.ebr3.Dallas1.Level3.net [4.69.134.21]
14 4.69.151.133
15 ae-12-60.car2.Dallas1.Level3.net [4.69.145.4]
16 4.59.197.26
17 64.25.32.10
18 64.25.32.26
19 64.25.39.1

Berechnung der Statistiken dauert ca. 14 Sekunden...
Quelle zum Abs. Knoten/Verbindung
Abs. Zeit Verl./Ges.= % Verl./Ges.= % Adresse
0 ahn0176delld600 [XXX.XXX.XXX.XXX]
0/ 3 = 0% |
1 1ms 0/ 3 = 0% 0/ 3 = 0% fritz.fonwlan.box [XXX.XXX.XXX.XXX]
0/ 3 = 0% |
2 --- 3/ 3 =100% 3/ 3 =100% XXX.XXX.XXX.XXX
0/ 3 = 0% |
3 49ms 0/ 3 = 0% 0/ 3 = 0% 87.186.250.162
0/ 3 = 0% |
4 49ms 0/ 3 = 0% 0/ 3 = 0% hh-eb5-i.HH.DE.NET.DTAG.DE [62.154.32.174]
0/ 3 = 0% |
5 --- 3/ 3 =100% 3/ 3 =100% 62.157.249.78
0/ 3 = 0% |
6 68ms 0/ 3 = 0% 0/ 3 = 0% ae-11-11.car1.Hamburg1.Level3.net [4.69.133.177]
0/ 3 = 0% |
7 60ms 0/ 3 = 0% 0/ 3 = 0% ae-4-4.ebr1.Dusseldorf1.Level3.net [4.69.133.182]
0/ 3 = 0% |
8 65ms 0/ 3 = 0% 0/ 3 = 0% ae-45-45.ebr2.Frankfurt1.Level3.net [4.69.143.166]
0/ 3 = 0% |
9 147ms 0/ 3 = 0% 0/ 3 = 0% ae-44-44.ebr2.Washington1.Level3.net [4.69.137.62]
0/ 3 = 0% |
10 148ms 0/ 3 = 0% 0/ 3 = 0% ae-82-82.csw3.Washington1.Level3.net [4.69.134.154]
0/ 3 = 0% |
11 154ms 0/ 3 = 0% 0/ 3 = 0% ae-81-81.ebr1.Washington1.Level3.net [4.69.134.137]
0/ 3 = 0% |
12 166ms 0/ 3 = 0% 0/ 3 = 0% ae-2-2.ebr3.Atlanta2.Level3.net [4.69.132.85]
0/ 3 = 0% |
13 182ms 0/ 3 = 0% 0/ 3 = 0% ae-7-7.ebr3.Dallas1.Level3.net [4.69.134.21]
0/ 3 = 0% |
14 184ms 0/ 3 = 0% 0/ 3 = 0% 4.69.151.133
0/ 3 = 0% |
15 213ms 0/ 3 = 0% 0/ 3 = 0% ae-12-60.car2.Dallas1.Level3.net [4.69.145.4]
0/ 3 = 0% |
16 186ms 0/ 3 = 0% 0/ 3 = 0% 4.59.197.26
0/ 3 = 0% |
17 --- 3/ 3 =100% 3/ 3 =100% 64.25.32.10
0/ 3 = 0% |
18 --- 3/ 3 =100% 3/ 3 =100% 64.25.32.26
0/ 3 = 0% |
19 188ms 0/ 3 = 0% 0/ 3 = 0% 64.25.39.1

Ablaufverfolgung beendet.
Completed in 24.87 seconds

It seems there are two paths. I don't know how to interpret the log, however. I did clear my dns cache the other day btw.

Edit: Changed firsted three IPs to XXX.XXX.XXX.XXX (Thanks, Chthon)

Chthon · Mar 12, 2011, 09:15 PM // 21:15

Quote:

Originally Posted by Lady Aranza

snip

Your problem appears to be on this hop:
2 --- 3/ 3 =100% 3/ 3 =100% XXX.XXX.XXX.XXX
0/ 3 = 0% |
3 46ms 0/ 3 = 0% 0/ 3 = 0% 87.186.250.166
Looks like your ISP is to blame. Talk to them.

The second record also shows something wrong with Level3 in Dallas, which is not uncommon. Level3 kinda sucks.

Also, you should edit your post to remove the IPs from the first 2 or 3 entries. Replace them with XXX.XXX.XXX.XXX or something. You don't want people knowing you local IP router IP, or ISP gateway.

Lady Aranza · Mar 14, 2011, 06:23 AM // 06:23

Quote:

Originally Posted by Chthon

Your problem appears to be on this hop:
2 --- 3/ 3 =100% 3/ 3 =100% XXX.XXX.XXX.XXX
0/ 3 = 0% |
3 46ms 0/ 3 = 0% 0/ 3 = 0% 87.186.250.166
Looks like your ISP is to blame. Talk to them.

The second record also shows something wrong with Level3 in Dallas, which is not uncommon. Level3 kinda sucks.

Also, you should edit your post to remove the IPs from the first 2 or 3 entries. Replace them with XXX.XXX.XXX.XXX or something. You don't want people knowing you local IP router IP, or ISP gateway.

Thanks!

Uhm, I am not sure if it's really my ISP. I just tried to ping the two nodes with 100% loss, they didn't answer. I think they might just not respond to ping/ ICMP. I will make another pathping when GW is working fine, as soon as I get home from work. If it looks the same, my ISP is off the suspect list.

Chthon · Mar 14, 2011, 07:22 AM // 07:22

While the loss could be a false alarm, the huge jump in ping probably is not. (Huge jump in ping can be a false alarm if a node is strongly deprioritizing responding to ping requests, but then you see the value go back down on a later node. Here the value does not go back down.)

Lady Aranza · Mar 14, 2011, 05:21 PM // 17:21

Here is a pathping result during a period when GW was working ok:

*--> pathping -w 500 -q 3 -4 206.127.145.228 <--*

Routenverfolgung zu 206-127-145-228.plaync.com [206.127.145.228]
ber maximal 30 Abschnitte:
0 ahn0176delld600 [XXX.XXX.XXX.XXX]
1 fritz.fonwlan.box [XXX.XXX.XXX.XXX]
2 XXX.XXX.XXX.XXX
3 87.186.250.170
4 217.239.39.10
5 195.16.161.58
6 206-127-156-82.plaync.com [206.127.156.82]
7 206-127-145-228.plaync.com [206.127.145.228]

Berechnung der Statistiken dauert ca. 5 Sekunden...
Quelle zum Abs. Knoten/Verbindung
Abs. Zeit Verl./Ges.= % Verl./Ges.= % Adresse
0 ahn0176delld600 [XXX.XXX.XXX.XXX]
0/ 3 = 0% |
1 0ms 0/ 3 = 0% 0/ 3 = 0% fritz.fonwlan.box [XXX.XXX.XXX.XXX]
0/ 3 = 0% |
2 --- 3/ 3 =100% 3/ 3 =100% XXX.XXX.XXX.XXX
0/ 3 = 0% |
3 45ms 0/ 3 = 0% 0/ 3 = 0% 87.186.250.170
0/ 3 = 0% |
4 66ms 0/ 3 = 0% 0/ 3 = 0% 217.239.39.10
0/ 3 = 0% |
5 --- 3/ 3 =100% 3/ 3 =100% 195.16.161.58
0/ 3 = 0% |
6 --- 3/ 3 =100% 3/ 3 =100% 206-127-156-82.plaync.com [206.127.156.82]
0/ 3 = 0% |
7 55ms 0/ 3 = 0% 0/ 3 = 0% 206-127-145-228.plaync.com [206.127.145.228]

Ablaufverfolgung beendet.
*--> pathping -w 500 -q 3 -4 64.25.39.1 <--*

Routenverfolgung zu 64.25.39.1 ber maximal 30 Abschnitte

0 ahn0176delld600 [XXX.XXX.XXX.XXX]
1 fritz.fonwlan.box [XXX.XXX.XXX.XXX]
2 XXX.XXX.XXX.XXX
3 87.186.250.162
4 hh-eb5-i.HH.DE.NET.DTAG.DE [62.154.32.174]
5 62.157.249.78
6 ae-11-11.car1.Hamburg1.Level3.net [4.69.133.177]
7 ae-4-4.ebr1.Dusseldorf1.Level3.net [4.69.133.182]
8 ae-47-47.ebr2.Frankfurt1.Level3.net [4.69.143.174]
9 ae-44-44.ebr2.Washington1.Level3.net [4.69.137.62]
10 ae-62-62.csw1.Washington1.Level3.net [4.69.134.146]
11 ae-61-61.ebr1.Washington1.Level3.net [4.69.134.129]
12 ae-2-2.ebr3.Atlanta2.Level3.net [4.69.132.85]
13 ae-7-7.ebr3.Dallas1.Level3.net [4.69.134.21]
14 4.69.151.157
15 * * *
Berechnung der Statistiken dauert ca. 11 Sekunden...
Quelle zum Abs. Knoten/Verbindung
Abs. Zeit Verl./Ges.= % Verl./Ges.= % Adresse
0 ahn0176delld600 [XXX.XXX.XXX.XXX]
0/ 3 = 0% |
1 0ms 0/ 3 = 0% 0/ 3 = 0% fritz.fonwlan.box [XXX.XXX.XXX.XXX]
0/ 3 = 0% |
2 --- 3/ 3 =100% 3/ 3 =100% XXX.XXX.XXX.XXX
0/ 3 = 0% |
3 51ms 0/ 3 = 0% 0/ 3 = 0% 87.186.250.162
0/ 3 = 0% |
4 49ms 0/ 3 = 0% 0/ 3 = 0% hh-eb5-i.HH.DE.NET.DTAG.DE [62.154.32.174]
0/ 3 = 0% |
5 --- 3/ 3 =100% 3/ 3 =100% 62.157.249.78
0/ 3 = 0% |
6 86ms 0/ 3 = 0% 0/ 3 = 0% ae-11-11.car1.Hamburg1.Level3.net [4.69.133.177]
0/ 3 = 0% |
7 55ms 0/ 3 = 0% 0/ 3 = 0% ae-4-4.ebr1.Dusseldorf1.Level3.net [4.69.133.182]
0/ 3 = 0% |
8 54ms 0/ 3 = 0% 0/ 3 = 0% ae-47-47.ebr2.Frankfurt1.Level3.net [4.69.143.174]
0/ 3 = 0% |
9 161ms 0/ 3 = 0% 0/ 3 = 0% ae-44-44.ebr2.Washington1.Level3.net [4.69.137.62]
0/ 3 = 0% |
10 146ms 0/ 3 = 0% 0/ 3 = 0% ae-62-62.csw1.Washington1.Level3.net [4.69.134.146]
0/ 3 = 0% |
11 149ms 0/ 3 = 0% 0/ 3 = 0% ae-61-61.ebr1.Washington1.Level3.net [4.69.134.129]
0/ 3 = 0% |
12 180ms 0/ 3 = 0% 0/ 3 = 0% ae-2-2.ebr3.Atlanta2.Level3.net [4.69.132.85]
0/ 3 = 0% |
13 185ms 0/ 3 = 0% 0/ 3 = 0% ae-7-7.ebr3.Dallas1.Level3.net [4.69.134.21]
1/ 3 = 33% |
14 182ms 1/ 3 = 33% 0/ 3 = 0% 4.69.151.157
2/ 3 = 66% |
15 --- 3/ 3 =100% 0/ 3 = 0% ahn0176delld600 [0.0.0.0]

Ablaufverfolgung beendet.
Completed in 17.28 seconds

It seems that entry 2 and 5 of the second pathping just don't respond to ping, same as in my try from last night.

Chthon · Mar 14, 2011, 08:57 PM // 20:57

Are you geographically far from 87.186.250.170? That could explain the sudden jump up.

If your ISP is ruled out, the only remaining candidates are Level3 and the GW servers.

Lithril Ashwalker · Mar 14, 2011, 11:39 PM // 23:39

there are other threads similar to this as well, impossible for some of us to get things done.

Lady Aranza · Mar 15, 2011, 06:22 AM // 06:22

Quote:

Originally Posted by Chthon

Are you geographically far from 87.186.250.170? That could explain the sudden jump up.

If your ISP is ruled out, the only remaining candidates are Level3 and the GW servers.

According to whois, 87.186.250.170 is in Berlin. I am about 200 kilometers from there.

Quote:

there are other threads similar to this as well, impossible for some of us to get things done.

Exactly. Last night I did the Riven Earth vanquish - lag spikes every 5 to 10 minutes, one disconnect (thanks god the reconnect worked, I was nearly finished). It took me 1hr 45minutes to do this.

Well I hope I will have my notebook back from repair soon, maybe this will work better. If this persists on my notebook, I will contact support.

Chthon · Mar 15, 2011, 03:30 PM // 15:30

Quote:

Originally Posted by Lady Aranza

According to whois, 87.186.250.170 is in Berlin. I am about 200 kilometers from there.

Exactly. Last night I did the Riven Earth vanquish - lag spikes every 5 to 10 minutes, one disconnect (thanks god the reconnect worked, I was nearly finished). It took me 1hr 45minutes to do this.

Well I hope I will have my notebook back from repair soon, maybe this will work better. If this persists on my notebook, I will contact support.

OK, that jump is not unreasonable for 200km. So we're left with Level3's questionable routing and the GW servers for suspects.

One other possibility I can think of: Are you on a college campus? Many campuses employ "packet shapers" that are notoriously bad at "shaping" packets by dropping them. Often these things are configured to prioritize pings, so the problems may be invisible on a pathping. To diagnose that you need software that can send pings using different ports and protocols.

Lady Aranza · Mar 15, 2011, 07:27 PM // 19:27

Quote:

Originally Posted by Chthon

Are you on a college campus?

No, I am on a home network with a fairly common DSL internet connection. Also, my connection hasn't changed and I could play perfectly well before the EB update.

However, I've got good news: I just finished doing today's Zaishen Vanquish without any problems. Boy did that feel good!

I have no idea if the problem is gone, or if I just got lucky. ANet, have you done something? If yes, thank you very much! Lets see how it is tomorrow.

Lady Aranza · Mar 16, 2011, 02:24 PM // 14:24

Ugh, spoke too soon. I am back to having forced breaks.

Why? · Mar 16, 2011, 04:01 PM // 16:01

this is the GW servers. This is happening to lots of people all over the world. Something happened in one of the recent updates to destabilize the servers.

I am receiving a lot more errors and disconnects than I ever have. So are lots of other people all over the world.