Game disconnects randomly for no reason, I am suddenly getting this issue without any system changes, tried troubleshooting, reset modem, flushed dns, reset wifi adapter, checked to make sure d3 was in the clear in firewall, literally nothing has changed on my end except a battle.net update and now I cant stay connected for even 10 minutes without getting 1016 error and d3 taking me back to the login page. Anyone else having this or just me? I’m in Ontario and never had this issue before.
6 Likes
yep, started today…
There is a file called Blizzard Entertainment (cache file) located in ProgramData delete this folder. If this doesn’t work, go and find the D3Prefs.txt file from C:\Users\Documents\Diablo III delete it. It will download a new folder and file when you reenter the game. The first file can get corrupted, the second is a config that can get a bad setting and cause load issues.{ Example: setting for Chromoeffects or Razer can cause issues in the config file}.
After getting the 1016 error It it takes me to the password login screen. I normally never have to enter my password.
After re-entering my password. It takes me to the whats new page and I have to click through what’s new.
After logging in from the error I noticed It also resets my chat settings (puts me back in general chat and resets the chat font settings)
I just started getting this error a couple of days ago.
If i exit the game normally my chat settings stay the same. Only when i get disconnected from the game by error 1016 my chat setting are getting reset.
This leads me to believe there is more to this error then just an internet connection.
I also tried everything Robray suggested and I am still getting the error.
I deleted the cache folder located inside the blizzard entertainment folder, and the D3frefs.txt file.
I didn’t delete the entire blizzard entertainment folder, although constant disconnects make me want to delete the entire game, very frustrating.
2 Likes
This error is old, and i mean years and years… it still plagues us. And all Blizz can and will do is point you to a troubleshooter. And those steps dont work. And you log calls, and update them, open new calls and nothing ever gets fixed. why? because its easier to blame the user, that way bliz, does not have to spend money… after all they already took your cash, what do they care if you cannot play?
6 Likes
Hey all,
The error 1016 is just a highly generic “you were disconnected from the game and because of how the disconnection happened, we are not sure why” error message. It’s extremely common and there’s a high likelihood that none of you have the same issue since none of you are in the same place in the US. I checked the Diablo 3 server stats and apart from a couple hiccups in EU a few hours ago (long after all your posts) it’s been really stable.
I can’t troubleshoot all of you in one thread, but I can work with the Original Poster here. If the rest of you are still having problems, feel free to create your own threads or contact support through tickets for help.
As for oobymach,
You’ve already done a lot of things for this - at least all of the things I’d have you try before trying to get a connection test. If you’re still having this problem, please create a WinMTR test which catches a disconnection. You want to restart the test every 10-15 minutes until you catch one of these problems. Once you’ve caught one red handed, run the test for about 5 more minutes. This will let us look for problems between your house and our servers which may cause this.
If you have problems with posting it due to a link error, go ahead and copy paste this into your next post, and replace “WinMTR goes here” with your test.
~~~~
WinMTR goes here
~~~~Actually it ran stable again after saturday, idk if it was my isp but I noticed the battle.net app would show the disconnected icon (the unplugged cable) for a few seconds every so often and web pages would stop loading during this time too so it wasn’t just diablo that was affected.
Glad to hear that it seems to have run stably after Saturday, oobymach. It does sound like a routing problem probably caused the issue and it may have been addressed by the ISP.
If the problem comes back, could you provide a WinMTR test to the host address: us.actual.battle.net ? Run the test until the problem occurs for 5 to 10 minutes. If you have issues pasting here, use Pastebin and post the end of the link. (ie. 123456 for pastebin.com/123456)
Well it keeps happening and idk why, here’s the result of mtr test during which it happened 3 times…and it’s happened about 20 times now this morning…
~~~~
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 1 | 2208 | 2199 | 3 | 4 | 71 | 4 |
| 10.4.172.66 - 1 | 2239 | 2238 | 37 | 73 | 467 | 60 |
| 10.5.203.18 - 1 | 2239 | 2238 | 40 | 77 | 527 | 96 |
| 10.55.113.244 - 1 | 2239 | 2238 | 41 | 78 | 516 | 64 |
| 10.55.113.122 - 1 | 2239 | 2238 | 39 | 75 | 491 | 70 |
| 10.55.113.177 - 1 | 2239 | 2238 | 38 | 73 | 533 | 54 |
| 10.4.244.62 - 1 | 2239 | 2238 | 38 | 75 | 578 | 81 |
| 10.4.244.73 - 1 | 2239 | 2238 | 38 | 74 | 539 | 94 |
| 10.55.113.182 - 1 | 2239 | 2238 | 52 | 83 | 500 | 107 |
| 10.55.113.23 - 1 | 2239 | 2238 | 52 | 87 | 451 | 72 |
|tcore3-toronto12_bundle-ether25.net.bell.ca - 1 | 2239 | 2238 | 50 | 79 | 501 | 102 |
|tcore3-chicagocp_hundredgige0-4-0-0.net.bell.ca - 1 | 2239 | 2238 | 51 | 87 | 556 | 68 |
| bx6-chicagodt_0-6-0-0.net.bell.ca - 1 | 2239 | 2238 | 49 | 86 | 499 | 73 |
| blizzard_bx6-chicagodt.net.bell.ca - 1 | 2239 | 2238 | 49 | 92 | 502 | 86 |
| No response from host - 100 | 449 | 0 | 0 | 0 | 0 | 0 |
| et-0-0-3-br02-eqla1.as57976.net - 1 | 2183 | 2170 | 98 | 158 | 3965 | 2335 |
| 137.221.68.93 - 1 | 2239 | 2238 | 105 | 146 | 657 | 193 |
| 24.105.30.129 - 1 | 2239 | 2238 | 107 | 141 | 372 | 131 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
~~~~
1 Like
Same problem here. I did all the troubleshooting and still disconnecting at random times.
5 Likes
Never had this problem before. happening constantly in s22
5 Likes
here IS how I’d like Blizzard to help U.S. w/ such issues, IF ‘all else fails’, while gaming. Why doesn’t someone do something like THIS? (found in this link)
by " increase-online-gaming-performance-by-tinkering-with-ethernet-card-driver.88083 "
"if you want the optimal online gaming experience, go to Advanced tab of your Ethernet adapter settings, and disable the following:
- Interrupt Moderation - clumps packets together and sends them as a batch - the main offender
- Flow Control - sounds counterintuitive to disable it, but it messes with existing flow control in Windows networking stack
- Receive Side Scaling - also messes with Windows networking stack
- [anything goes here] Checksum Offload - supposed to speed up performance by offloading TCP/UDP checksumming to hardware; in reality does nothing for an average desktop PC except interfere with Windows networking stack
- Green Ethernet - performance-eating eco garbage
Try it and see! Less rubberbanding zombies in Left4Dead, more headshots in your favorite FPS, etc etc.
Also, if you play a MMORPG and want faster responsiveness, you need to disable TCP/IP Nagle algorithm in Windows. There are multiple guides about it though.
Same here… i keep getting the 1016 error no matter what suggestions Blizz posts =(
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| router.asus.com - 0 | 456 | 456 | 0 | 0 | 1 | 0 |
| 10.10.10.1 - 0 | 456 | 456 | 0 | 0 | 1 | 0 |
| 97-107-32-58.dcwis.com - 2 | 436 | 431 | 4 | 14 | 42 | 14 |
| 10.255.255.133 - 1 | 452 | 451 | 5 | 15 | 51 | 20 |
| 84.206-40-96.netnet.net - 1 | 452 | 451 | 7 | 15 | 37 | 13 |
| 71.66.44.178 - 2 | 436 | 431 | 7 | 19 | 63 | 16 |
| 71.66.44.177 - 5 | 392 | 376 | 8 | 18 | 50 | 19 |
| masnoh06-swt501.bcs.swo.rr.com - 3 | 404 | 392 | 7 | 18 | 38 | 19 |
| ae15.applwibp02h.midwest.rr.com - 1 | 444 | 441 | 9 | 19 | 54 | 35 |
| be72.gnfdwibb01r.midwest.rr.com - 1 | 440 | 436 | 18 | 30 | 60 | 24 |
|bu-ether16.chcgildt87w-bcr00.tbone.rr.com - 2 | 432 | 426 | 18 | 29 | 68 | 30 |
| 66.109.5.225 - 1 | 452 | 451 | 18 | 29 | 89 | 33 |
| 24.30.201.81 - 2 | 436 | 431 | 18 | 34 | 129 | 41 |
| No response from host - 100 | 91 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 91 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 91 | 0 | 0 | 0 | 0 | 0 |
| 137.221.68.81 - 1 | 444 | 441 | 59 | 71 | 145 | 69 |
| lax-eqla1-ia-bons-03.as57976.net - 1 | 448 | 446 | 60 | 69 | 90 | 72 |
| 24.105.30.129 - 1 | 448 | 446 | 58 | 69 | 96 | 64 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| Destination network unreachable. - 1 | 955 | 953 | 0 | 0 | 2 | 0 |
| Destination network unreachable. - 1 | 955 | 950 | 0 | 0 | 1 | 0 |
| 97-107-32-58.dcwis.com - 1 | 931 | 924 | 6 | 14 | 54 | 12 |
| Destination network unreachable. - 1 | 931 | 923 | 5 | 15 | 42 | 14 |
| Destination network unreachable. - 1 | 935 | 928 | 7 | 16 | 52 | 10 |
| Destination network unreachable. - 1 | 927 | 918 | 7 | 18 | 103 | 11 |
| Destination network unreachable. - 2 | 916 | 904 | 7 | 18 | 47 | 10 |
| masnoh06-swt501.bcs.swo.rr.com - 2 | 915 | 904 | 7 | 17 | 53 | 14 |
| ae15.applwibp02h.midwest.rr.com - 1 | 935 | 929 | 8 | 21 | 66 | 22 |
| Destination network unreachable. - 1 | 935 | 928 | 18 | 29 | 60 | 24 |
|bu-ether16.chcgildt87w-bcr00.tbone.rr.com - 1 | 939 | 934 | 18 | 30 | 96 | 24 |
| 66.109.5.225 - 1 | 939 | 934 | 17 | 28 | 69 | 23 |
| Destination network unreachable. - 1 | 943 | 938 | 25 | 38 | 106 | 32 |
| No response from host - 100 | 191 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 191 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 191 | 0 | 0 | 0 | 0 | 0 |
| 137.221.68.83 - 2 | 891 | 874 | 67 | 79 | 157 | 69 |
| 24.105.30.129 - 1 | 931 | 924 | 68 | 78 | 104 | 82 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
i submitted a ticket and I am getting no response on the problem?
Hey there,
Packet count is dropping from 955 to 931 around here, and is consistently lower the entire rest of the test. These missing packets are likely the cause of the disconnects in this quoted case.
The best solution would be to contact the internet service provider and let them know of the issue. They should be able to reach out to whomever manages these nodes to investigate the problem. Though keep in mind this can be a lengthy process so there may be no “fast” solution here.
A VPN service may be a temporary workaround but those are normally paid services so I don’t typically recommend them. Even if this is a wanted option I do still highly recommend reporting this to the service provider as that is a much more long term solution.
Hope the info helps. Cheers!
Called Speculum and had THEM check my internet. Changed plugs. Changed routers. Ethernet cords. Used Wifi and Ethernet. NOW, my wife also dc’s… NOT at the same time or rift even. On 2 diferant channels. Same channels. Reset Windows 10. Issue went away, about an hour. Back 3x’s in for me… and my wife… but… again… NEVER the same time! Never the same internet. Reset cable modem. Unplugged routers. waited 3 minutes. Shut down the pc’s. Flushed my dns and my toilets 4 or 5 times now, since I’ve been working on this for last couple days now. Since 130 this am 4 me. 12 hours now. Do something. then, test. Get kicked. Repeat. do something else… do it again. Ever since, the PTR. NEVER HAD THIS ISSUE w/ our connections. Had our laptops, since last xmas. NO issues. Then… the PTR for 22 came. What happened? 3 or 4 times, i lost my hero’s, and gear in ptr… just figured, ah, wth… NOW… this. Could have, could still be, my best season EVER! But, here I am, telling Lack-0-Vision. SOMETHING they did, seemingly, has caused this. OR. Maybe not. But, I’ve been using my monitor and ONLY svchost.exe uses MORE internet, than Battle.net HELP!!!
Been having this Error 1016 issue since I installed the update for S22. Throughout my years of playing D3, I’ve gotten that error a handful of times out of the blue, but just today alone, I’ve had 39 crashes…This is getting annoying.
2 Likes