Every few minutes the game just plain disconnects with the error WOW51900319. Anyone else having this…
Yep, started today for me. Like 5-10 minutes between each disconnect. It also removes all changes to settings and untracks every single quest every time I disconnect. Really annoying. Exact same error message.
I’m trying to level a new class and this is almost unplayable.
Ok Im really wondering wtf is going on… Cleared my wtf/interface/cache no joy… char loads and within 60-120seconds disconnects back to the same error
WinMTR shows this for 185.60.112.158 (and similar for .157)
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
---|---|---|---|---|---|---|
EtisalatHub.lan - 0 | 3 | 3 | 1 | 3 | 7 | 1 |
31.215.198.2 - 0 | 4 | 4 | 4 | 11 | 24 | 24 |
10.246.250.142 - 0 | 4 | 4 | 4 | 12 | 27 | 27 |
195.229.4.68 - 0 | 4 | 4 | 11 | 17 | 27 | 27 |
195.229.2.93 - 0 | 3 | 3 | 114 | 118 | 125 | 114 |
pr01.eqfr5.blizzardonline. net - 0 | 3 | 3 | 115 | 128 | 138 | 115 |
ae1-br01-eqfr5.as57976 .net - 0 | 3 | 3 | 134 | 150 | 174 | 174 |
et-0-0-2-br01-eqam1.as57976 .net - 0 | 3 | 3 | 121 | 327 | 724 | 121 |
No response from host - 0 | 0 | 0 | 0 | 0 | 0 | 0 |
137.221.78.49 - 0 | 3 | 3 | 121 | 134 | 155 | 121 |
185.60.112.158 - 0 | 3 | 3 | 118 | 121 | 125 | 118 |
________________________________________________ | ______ | ______ | ______ | ______ | ______ | ______ |
However, WinMTR shows this for 185.60.112.159
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
---|---|---|---|---|---|---|
EtisalatHub.lan - 0 | 8 | 8 | 1 | 2 | 6 | 6 |
31.215.198.2 - 0 | 5 | 5 | 2 | 4 | 9 | 4 |
10.246.250.141 - 0 | 8 | 8 | 3 | 26 | 108 | 108 |
195.229.4.66 - 0 | 8 | 8 | 7 | 26 | 108 | 108 |
195.229.1.183 - 0 | 8 | 8 | 122 | 145 | 213 | 213 |
pr01.eqfr5.blizzardonline. net - 0 | 8 | 8 | 117 | 141 | 210 | 210 |
ae1-br01-eqfr5.as57976. net - 50 | 2 | 1 | 1552 | 1552 | 1552 | 1552 |
et-0-0-2-br01-eqam1.as57976 .net - 0 | 2 | 2 | 1818 | 2479 | 3141 | 3141 |
137.221.65.75 - 0 | 4 | 4 | 138 | 234 | 312 | 302 |
137.221.78.47 - 0 | 8 | 8 | 118 | 142 | 212 | 212 |
No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
________________________________________________ | ______ | ______ | ______ | ______ | ______ | ______ |
its really cute you did all this work, but it will be a bug on bliz side that they can’t test for and fix.
Im thinking of making a kickstarter on their behalf to hire a tester.
having the same issue, started after 1pm
For a while today morning it was ok. then it started again
Same here along with latency issues.
Same issue here. I get random crashes along with the WoW error message. Upon logging back in, all my objectives are untracked.
I was worried that it’s an issue with my hardware, but it seems it’s not an isolated case.
Been having this over the last few days. Was thinking it was my PC but my second monitor is been fine watching YouTube/BBC iPlayer/reading websites, so it’s not my internet.
Same error code of WOW51900319 every time I’m dc’ed and log back in I have to re-track all my quests.
Edit : dc’ed so far at 11:08, 11:38 and just now at 14:18.
Strange all end in 8 …
It’s been over a week and this bug is still lingering. I’ve been spamming old dungeons and raids for both gold and transmogs and most of the time when I try to exit the instance I keep either getting a message about some error that the instance failed to load, meaning I can’t exit the instance or the game downright crashes on me.
I have experienced DCs for more than a week now; at random times and across all characters. Adding to that, the loading bar on the loading screen freezes at 1/3 in, and I then (also) DC.
Hey all, not sure if that’s the solution, but I’ve been getting no crashes for more than 24 hours by now. Here’s what I did (on Windows 10):
- Right-clicked on the bnet app and enabled Run as Administrator under the Compatibility tab
- User account control settings - set to Never notify (bottom setting)
I thought it was just me also but the untracking thing has been happening to me since 3 days ago before these dcs starting getting worse, so im wondering if its a different thing?
Been having this over the last few days. 4 times yesterday and just got it again today at 12:40
Have the same issue with the same error, code 7th time now i disconnected in an hour in mythic + dungeons
Oh the untracking of quests has been happening to me too across all toons. Very annoying.
Edit: the disconnects have stopped tho. Last few days the connections been stable.
Same problem we had a few months ago. But then after 1-2 weeks the DC disappeared, I just figured Blizz had fixed it, but now the DC are back. Mine started today. It’s been fine for the last few months.
My friend and I both keep getting DCed; we live in separate cities and neither of us has a bad internet connection; it is only WoW that is acting up.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.