Constant DC's when logging/loading zones

Support Technical Support
1

This all started when I server xfered my character from Malganis to Dalaran (US). Been getting constant DCs when trying to start the game or load up. Lag in raid/world has been very noticeable as well. Have to consistently alt-f4 my game when I try to load in a zone because I just dc during the load.

US Central:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |

Host - % Sent Recv Best Avrg Wrst Last
10.0.0.1 - 0 437 437 0 1 15 1
96.120.102.129 - 0 437 437 8 13 30 16
po-306-1294-rur202.burien.wa.seattle.comcast.net - 0 437 437 8 13 32 9
be-221-ar01.seattle.wa.seattle.comcast.net - 0 437 437 8 14 30 16
24.124.128.162 - 0 437 437 8 16 48 15
be-33650-cr01.seattle.wa.ibone.comcast.net - 0 437 437 7 15 32 15
be-1401-cs04.seattle.wa.ibone.comcast.net - 0 437 437 9 15 30 12
be-2411-pe11.seattle.wa.ibone.comcast.net - 0 437 437 10 16 30 17
50.242.149.178 - 0 437 437 10 19 89 15
ae1-br02-eqse2.as57976.net - 0 437 437 65 76 185 67
No response from host - 100 88 0 0 0 0 0
et-0-0-1-pe01-eqch2.as57976.net - 0 437 437 65 73 171 66
24.105.62.129 - 0 437 437 67 73 93 77
________________________________________________ ______ ______ ______ ______ ______ ______

West Coast:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |

Host - % Sent Recv Best Avrg Wrst Last
10.0.0.1 - 0 744 744 0 1 18 2
96.120.102.129 - 0 744 744 8 14 37 17
po-306-1294-rur202.burien.wa.seattle.comcast.net - 0 744 744 7 14 50 13
be-221-ar01.seattle.wa.seattle.comcast.net - 0 744 744 8 14 30 11
24.124.128.162 - 0 744 744 8 17 52 13
be-33650-cr01.seattle.wa.ibone.comcast.net - 0 744 744 9 17 39 16
be-1301-cs03.seattle.wa.ibone.comcast.net - 0 744 744 9 16 46 13
be-2311-pe11.seattle.wa.ibone.comcast.net - 0 744 744 9 16 38 18
50.242.149.178 - 0 744 744 10 21 107 13
ae1-br01-eqse2.as57976.net - 0 744 744 39 50 157 42
xe-0-0-0-1-br01-eqsv5.as57976.net - 0 744 744 39 47 158 42
et-0-0-29-br02-eqsv5.as57976.net - 0 744 744 38 46 162 42
xe-0-0-1-1-br02-eqla1.as57976.net - 0 744 744 38 53 232 41
et-0-0-29-br01-eqla1.as57976.net - 0 743 743 43 191 1510 554
No response from host - 100 150 0 0 0 0 0
et-0-0-0-pe02-swlv10.as57976.net - 0 744 744 38 47 164 42
las-swlv10-ia-bons-02.as57976.net - 0 744 744 38 44 62 44
137.221.105.2 - 0 744 744 39 45 62 49
________________________________________________ ______ ______ ______ ______ ______ ______
2

Hey there Granterino!

Looking at the WinMTR data you provided I am not seeing anything severe enough to account for what you are experiencing in game.

Going from the west coast to a central server hitting 73ms is not surprising and the game should still be very playable at 70ms.

Was this test run while actively experiencing the issue in game?

If so, latency is within normal ranges there doesn’t appear to be any data loss. So either the test did not pick up the issue or the issues are not connection caused. That would put us to something on the system or with the client itself. You mentioned this happened after a transfer.

This could be bad cached data for the character so here is what I would recommend.

If you have any addon managers installed. They are fine programs but they have the tendency to prevent our troubleshooting steps from working. Please uninstall them and leave them off your system until we have solved the problem.

Once that is confirmed, we need to delete the temporary game files to attempt to eliminate any corrupt data that might be affecting the client or characters. Your game will rebuild them when you next login but this will remove all installed addons. Please do not reinstall any addons until we know the issue is resolved:

Clearing Temporary Data:

  1. Click the gear symbol in the Blizzard Desktop Application and select show in explorer.
  2. Inside the retail folder delete or rename the Cache, Interface and WTF folders.

Resetting In-game Client Options:

  1. Click the blue bnet icon on the bnet app.
  2. Choose settings, then game settings.
  3. Click the reset in game user options button under the correct game listing.
  4. Confirm the changes and close the window.

Running a Scan and Repair of the Client:

  1. Click the gear symbol next to the play button. Select Scan and repair.
  2. If any errors are found and repair, rerun scan and repair.

Once this is done go ahead and retest. If the issue persists I recommend submitting a ticket directly to support (Be sure to include the requested data of an MSinfo and Dxdiag. (Steps should be included with the ticket form. If you could also run a 10 minute winmtr to the central server while experiencing the issue in game, that will be helpful as well.

https://us.battle.net/support/en/help/product/wow