Time Warner Instance Load Screen Hanging
01/06/2011 3:50 PMPosted by BrianII'd love to see what you have to send, sure. :)
The vast majority of people reporting this are going to the Chicago DC, but I have seen one or two verified reports of instance zoning to the LA DC. Any more data would be appreciated.
Will do! What type of time frame do you want for the trace? A couple minutes before and on to a couple minutes after?
It has happened twice tonight so far.
For some reason, I have no problems logging onto my account with my older computer. On my new computer I cannot get past the blue line of death. So what I do is when I reach that point I log into the same account on my older computer and it kicks me back out on the newer one. When I get my character logged on, on my older computer I relog again on the newer computer and wahlah I can get my character in game. It's like for some reason logging my char in on my old computer somehow helps me get past the blue line of death on the newer computer. Weird I know but somehow it works. Sometimes I have to do it twice but it always works. Anyhow hope this helps some of you get in game until they resolve this issue.
My realm is Runetotem. So for me, I am having problems with the instance server only. I currently have no major issues (outside of a small amount of latency since 4.0.1) on Runetotem.
My brother is a TWC tech, has checked my connections over the course of several days, says my link is fine.
I do anything else w/the net, its fine. Just WoW.
I then signed back in and I was in the dungeon group. Bizarre and very frustrating!!
My roommates are getting these issues too, but its only one of us at a time. NEVER all of us. Were using the same internet so this is really just a nightmare.
connection.log after it disconnected me:
1/6 21:56:48.075 Login program=WoW platform=Win locale=enUS
1/6 21:56:48.150 Component WoW.Win.13329
1/6 21:56:48.227 Component WoW.base.13329
1/6 21:56:48.252 Component WoW.enUS.13329
1/6 21:56:48.293 Component Tool.Win.2104
1/6 21:56:49.270 GRUNT: state: LOGIN_STATE_CONNECTING result: LOGIN_OK
1/6 21:56:49.346 Connecting to 184.108.40.206:1119
1/6 21:56:50.390 GRUNT: state: LOGIN_STATE_AUTHENTICATED result: LOGIN_OK
1/6 21:56:51.982 ClientConnection Initiating: COP_CONNECT code=CSTATUS_CONNECTING
1/6 21:56:52.023 GRUNT: state: RESPONSE_CONNECTED result: LOGIN_OK
1/6 21:56:52.458 ClientConnection Completed: COP_CONNECT code=RESPONSE_CONNECTED result=TRUE
1/6 21:56:52.500 ClientConnection Initiating: COP_AUTHENTICATE code=CSTATUS_AUTHENTICATING
1/6 21:56:52.765 ClientConnection Completed: COP_AUTHENTICATE code=AUTH_OK result=TRUE
1/6 21:56:53.386 ClientConnection Initiating: COP_GET_CHARACTERS code=43
1/6 21:56:54.002 ClientConnection Completed: COP_GET_CHARACTERS code=44 result=TRUE
1/6 21:57:24.928 ClientConnection Initiating: COP_LOGIN_CHARACTER code=76
1/6 21:57:33.273 ClientConnection Completed: COP_LOGIN_CHARACTER code=77 result=TRUE
1/6 22:03:28.024 ClientConnection Completed: COP_LOGIN_CHARACTER code=77 result=TRUE
1/6 22:03:29.228 ClientConnection Initiating: COP_GET_CHARACTERS code=43
1/6 22:03:29.472 ClientConnection Completed: COP_GET_CHARACTERS code=44 result=TRUE
1/6 22:03:46.830 ClientConnection Initiating: COP_GET_REALMS code=REALM_LIST_IN_PROGRESS
1/6 22:03:46.870 ClientConnection Completed: COP_GET_REALMS code=REALM_LIST_SUCCESS result=TRUE
1/6 22:03:49.333 ClientConnection Completed: COP_GET_REALMS code=RESPONSE_CANCELLED result=FALSE
1/6 22:03:49.361 ClientConnection Initiating: COP_CONNECT code=CSTATUS_CONNECTING
1/6 22:03:49.521 ClientConnection Completed: COP_CONNECT code=RESPONSE_CONNECTED result=TRUE
1/6 22:03:49.542 ClientConnection Initiating: COP_AUTHENTICATE code=CSTATUS_AUTHENTICATING
1/6 22:03:49.831 ClientConnection Completed: COP_AUTHENTICATE code=AUTH_OK result=TRUE
1/6 22:03:49.847 ClientConnection Initiating: COP_GET_CHARACTERS code=43
1/6 22:03:50.250 ClientConnection Completed: COP_GET_CHARACTERS code=44 result=TRUE
1/6 22:04:04.063 ClientConnection Initiating: COP_LOGIN_CHARACTER code=76
1/6 22:04:27.956 ClientConnection Completed: COP_LOGIN_CHARACTER code=77 result=TRUE
1/6 22:06:55.698 ClientConnection Completed: COP_LOGIN_CHARACTER code=77 result=TRUE
1/6 22:07:02.529 ClientConnection Completed: COP_LOGIN_CHARACTER code=77 result=TRUE
1/6 22:11:16.064 ClientConnection Completed: COP_LOGIN_CHARACTER code=77 result=TRUE
1/6 22:11:18.387 ClientConnection Completed: COP_LOGIN_CHARACTER code=77 result=TRUE
1/6 22:30:12.390 Client initiated Disconnect from 82ce810c
1/6 22:30:12.423 GRUNT: state: LOGIN_STATE_DISCONNECTED result: LOGIN_OK
1/6 22:30:12.437 Login program=WoW platform=Win locale=enUS
1/6 22:30:12.510 Component WoW.Win.13329
1/6 22:30:12.530 Component WoW.base.13329
1/6 22:30:12.750 Component WoW.enUS.13329
1/6 22:30:12.826 Component Tool.Win.2104
If you need any information, I will gladly help out.
This is especially frustrating when you are doing a PuG heroic and you wipe. When you finally get back in the game from Alt+F4ing, you are usually booted from the group from being offline.
Approximately 50% of the time my girlfriend and I load into an instance, arena, or battleground, the load screen freezes, and eventually disconnects.
This's also often followed by severe lag spikes (1000ms+) upon logging back into the game after force closing the game.
If it's of any relevance, my location is Brisbane, Australia, my ISP is TPG and my router is a NETGEAR DG834G. Also, I doubt that (at least for me) ISP is the cause as my friend who lives several blocks away (within the same exchange) has the exact same plan with the ISP and has never experienced this problem.
I've tried the temporary solutions suggested in the other thread with 158 pages which involves changing the Speed/Duplex of my network card, disabling all checksum offloads as well as switching to a USB wireless adapter, all to no avail.
I've also tried re-installing the game and disabling all addons and still getting the same problem.
Please fix this soon, my guild and arena team mates are getting more and more frustrated with my inability to run back after a wipe and losing an arena match because they were short a member.
Its sad, but my way around it is to have someone rez me because if i release, i'll probably not make it back (and it's 5 min quicker atm).
For the record, I've never had problems until the release of the expansion so if you guys changed any major networking codes or access ports or something (i'm not a comp tech by any means) between cata and wrath, it may be well that.
Bump into the heads of TWC because it's only a matter of time before someone on the thread goes "i've changed ISP and i'm all cured" and there's mass exodus from that company.
If TWC is the problem and they want our money, they'd figure out what they are doing wrong before they lose a few X-thousand customers.
01/06/2011 8:42 AMPosted by BrianII am going to be looking at gathering some packet captures from people experiencing this issue. The setup that I am looking for is the simplest possible and will require downloading and running Wireshark. No wireless, no router, software firewalls temporarily removed, all drivers up to date, etc. This is just to provide a clean environment for testing purposes. If anyone is interested in assisting me with this, please email me at email@example.com. I am currently sorting through posts looking for other good candidates.
You will also, obviously, have to be using Time Warner or a subsidiary and connecting to the Chicago DC.
I'm glad this is being looked into. It's very frustrating. I can't PuG since the restarting would likely get me kicked from a group and I'm tired of punishing my guildmates with the restarts and the latency/dcs that occur when I successfully load into an instance. Not cool when you're offtanking or healing and lag out on the pull because you actually got past the load screen without having to restart WoW.
What's strange to me is that my husband and I are going through the same connection, but he's experiencing far fewer problems than I am, even when we are in the same heroic together. However, I have been running more instances (particularly heroics and raids, which seem to have more occurrences than normal dungeons). I'd be willing to help with testing, but he'd need to handle any firewall, router, wireless or other tech details. (Time Warner, KC, Moon Guard server)
Please report any Code of Conduct violations, including:
Threats of violence. We take these seriously and will alert the proper authorities.
Posts containing personal information about other players. This includes physical addresses, e-mail addresses, phone numbers, and inappropriate photos and/or videos.
Harassing or discriminatory language. This will not be tolerated.