I have been having an issue lately that completely prevents me from logging in 100% of the time. I boot the game up, it gets to the splash screen where usually the logging in box would pop up, except it never does. It just hangs there until it crashes with error code 3016. What’s interesting is that If I boot it up, then immediately switch to a different active window leaving D4 on in the background, it successfully logs in and I get to the character select screen. If I switch back to D4, it crashes as soon as I hit a button. This was not happening a week or two ago. It happens literally every time. Haven’t gotten in game in the last two days. Internet is completely fine with every other game, so I’m not sure what’s happening with D4.
Thank you for starting your own thread. This is always preferred unless you are having an exact same issue in an existing thread, but its better to have your own to track your own issues.
I have answered you here:
-Error 1016 not resolving - #7 by DTMAce-1687
But you can reply here in your thread.
Thanks - yes. I’ve tried all of your suggestions. I’m about ready to give up because I have no early clue what it could be.
weird update:
I was playing around with the localprefs file and i changed the startup resolution to something other than full screen. I have a 2560x1440p monitor and so I changed it to 1280x720…wouldn’t you know it boots up perfectly in a small window and plays great. If i manipulate the window by dragging to enlarge it close to full screen, i start getting insane amounts of lag
what is going on??? it seems to me like the cause of the connection errors is related to my resolution. in full screen it simply doesn’t even connect?
Yeah, I now have some correlation with a couple of other threads reporting similar problems.
So obviously there is a different cause than simple networking connections.
There must have been some update (windows or driver) that has changed something. Possibly to battlenet, but hard to say.
I tested mine again tonight, but it appears to be fine. But I’m also running a driver from June 1st for my Nvidia card.
Hey there,
If the provided steps do not solve the issue, then I recommend submitting a ticket with an msinfo and pingplotter test attached for further investigation. (instructions for collecting that msinfo report will be on the form.)
Pingplotter steps: Blizzard Support - Running PingPlotter
Click your name at the top right of this page, click support, click contact support.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.