Question Frequent disconnections and DCOM error code 10016 ?

[zewoo]

Hi, I'm looking for someone with tech knowledge to help me sort something out. It really bothers me, so I will give as much detail as possible.

When I play Diablo 3 on battle net, I randomly get these network disconnections, lately many of them.
But in other games, launchers everything is good and nothing happens with network disconnections. It only happens in Diablo 3 game. Always it's overtaken by Windows distributed com error 10016, while in diablo 3 it's one zero less, error code 1016.

I know some may say it's not related, but I'm sure it is. Network disconnections last for 5minutes and then everything is back to normal. I need someone to help me fix this. I tried all Diablo 3 disconnection steps and DCOM error codes fixes, even the advanced ones. I asked a lot of people in Diablo 3, they all said it's just my problem.

I don't know what to do, App ID is unavailable and CLSID isn't written. Please someone help, I've been dealing with this for 2 years. I reinstalled Windows, even deleted Diablo 3 accounts so got new ones (but that's because of sms bypassers that got to my PC and make it die, literally).

 

[gggplaya]

Appears to be a permissions issue. Try running Diablo 3 and Battle.net both in Admin mode.

Reference: https://learn.microsoft.com/en-us/t...gement/event-10016-logged-when-accessing-dcom

Also, don't let windows auto find your drivers. Make sure you're using the ethernet and wifi drivers found on your motherboard's website, as well as the chipset driver.

 

[evermorex76]

Or go further and get the drivers directly from the manufacturer of the component (network chip, motherboard chipset/CPU, etc.), which are generally far more up to date.

Appears to be a permissions issue.

Its not an issue with permissions that needs to be fixed. They only say that you can change permissions to stop the events from being logged if they bother you, and otherwise that you can just ignore them. They explicitly say that the events aren't an indication that any functionality is effected. It just indicates that the first, preferred method of accessing the DCOM components failed, so the software fell back to using a different set of parameters to do it. There is only an issue if you see other events that indicate there was an actual failure. Having them logged is basically just so that if someone was debugging software and trying to optimize it, they'd know they should look at this and change their methods. Event Viewer has a LOT of entries that are irrelevant to anyone trying to do normal troubleshooting.

So Diablo 3 is trying to access DCOM components and it has to fall back to alternate parameters, but it otherwise succeeds. This may simply be that the game activates some feature to try to test and restore the connection, which happens to result in the DCOM events, but it doesn't mean the feature is failing to work. The DCOM events in themselves do not indicate a failure OR that what causes them is the cause of the disconnect. The fact that the numbers are similar is just coincidence. Event 10016 occurs constantly on my system and it's just a warning, not an error. (In fact it happens whenever there is a DNS lookup failure due to a timeout, in my BitTorrent client, so it's Windows's own services that are not using the "preferred" methods.)

Blizzard specifies that the code 1016 is usually caused by a connection issue. It's a generic disconnect error. The game lost connectivity to the servers. Aside from the DCOM errors, are there any other warnings or errors or even informational events that occur at the precise time that it happens? Especially anything network related but it could also be something that doesn't at first seem to mean anything.
What "3 disconnection steps" did you actually try? Are you using wired or Wi-Fi on your computer? What kind of Internet service do you have?

As shown here, you could use WinMTR running while you play to see whether there are any problems. (As one pointed out, if a single hop loses packets but the ones after it don't, then the packet loss at that hop isn't necessarily a problem, but other issues may be seen.)
https://us.forums.blizzard.com/en/d3/t/constant-there-was-an-error-code-1016/4555/4

It's entirely possible that this has nothing to do with YOUR machine or even your ISP, but is instead an issue somewhere in the middle, at one of the providers through which the traffic passes on the way to/from the remote server. You may get resolution simply by using a different server.

 

[zewoo]

There are only two DCOM errors but both are 10016 and it happens only when disconnect from this game. One is windows.security.center.wscbrokenmanager and second one is
windows.security.center. also but I don't remember the end of it.

I'm not at home right now, but will try to answer most of questions. I can check at home when it happened what errors were in event viewer. I'm using UGreen Cat 8 ethernet cable. I tried giving some permissions to these errors in event viewer, but it doesn't say App ID or CLSID. My ISP is Orange.

Well what I have done is simply flush dns, repair files, reset whole network in house reset network settings to default, looked for some keys I did reset that they recommended, but for dcom events.

Disconnects happen randomly, can be like 3 times within 20 minutes and 3 times within 4 hours of playing, but 2 days ago there were even more disonnects in less time. I also always disable some stuff in Windows Services.

If it might help. I changed cables, changed network card to system main, because I bought a new one a month ago. I can give more info when I will be back at home.

 

[evermorex76]

There are only two DCOM errors but both are 10016 and it happens only when disconnect from this game. One is windows.security.center.wscbrokenmanager and second one is
windows.security.center. also but I don't remember the end of it.

If you can provide the full details (screenshot or copy and paste) it may help determine what is happening. But as I said, the events may not be indicating the CAUSE of the disconnects, but merely be something REACTING to the disconnect. Battle.net software may initiate "recovery" steps when there is a disconnect, and it may be the steps it performs to try to recover which cause those events. Remember, Microsoft has said that the events themselves DO NOT indicate that something failed to work, only that the software had to switch to a different method to do whatever it was trying to do. You need to stop trying to "fix" the DCOM events. If the software doesn't generate any other events then either the software worked, or it doesn't directly generate events that go into Event Viewer. (And in that case if the software doesn't save anything in its own log files then you'll have no idea what happened.)

My ISP is Orange.

So, you're using a wireless ISP. The most unreliable type of Internet service available. (Is it Orange Wireless in the US? It can be confusing because Orange was a wireless provider in the UK but doesn't exist now, but Orange Group still exists as a multinational telecom provider.) Even dial-up has a better guarantee of connection. It's almost certain that your service simply drops data once in a while (it's still impossible to even get a PHONE CALL to be 100% clear) or has extremely high latency or somewhere on the ISP's network there is congestion and they start dropping/throttling traffic, or this issue might not be caused by that (even though those things happen) and could be caused further up the traffic path.

Running WinMTR while playing as well as looking for other events may shed further light on it (you'll be able to tell if it's the connection inside your house dropping or not), or switching to a different server may help, but it may come down to simply needing to use a more reliable ISP, which may not be possible or affordable in your area. Even if you find that it's your service dropping packets or being throttled or something, the ISP isn't going to care. It's the nature of wireless and they don't guarantee anything.

 

[zewoo]

I stopped fixing dcom errors, I am using Orange without wifi in Poland. 600/100 mbs. My latency on speedtest is 2 or 3ms so I don't have wifi in my offer. I don't think it is Orange fault, on steam games and other everything works. On my phone I use tmobile not orange. It can't be ISP problem, my roommate one year ago didn't have these. I reinstalled windows several times and still disconnects. I downloaded WinMTR but for now didn't have time to check it.

 

[evermorex76]

I don't think it is Orange fault, on steam games and other everything works.

Those games aren't using Battle.net, and may work entirely differently in the underlying code in how they handle network issues like packet loss or latency, which can occur at any point in the path between you and the server. If you and your roommate were both playing the same game at the same time on the same server with identical PCs and they didn't experience any issues at the same moment that you were being disconnected, it COULD indicate something other than a network issue, but at this point you have basically nothing to provide an answer.

If the game doesn't have any way to view logs of what it's doing in the background when the disconnects happen, and there's nothing in the Windows event log, and WinMTR doesn't provide any insights, it's going to be REALLY hard to resolve without just throwing more random things at it.

Regarding the DCOM events, DCOM is related to network communications and very likely is heavily involved with the battle.net game and server communications. I looked up the windows.security.center.wscbrokermanager string as it related to DCOM, because it made me think maybe something the game is doing is violating security. It is after all a very old game, released long before Windows 10 or 11 (you didn't mention which you're using) which introduced a lot of new security features. Even if content was being released until recently, the underlying client/server code may not have been updated much. It's possible that the game tries to do something which one of the security features blocks, like some weird memory accesses. One would think the developers would have encountered and fixed the issue but since the code presumably still falls back to other methods and does what it needs to do, it would be as Microsoft says something that can be ignored and not worth spending resources to fix. I found posts about deleting some keys in the Registry, but that would only eliminate the events, not the disconnects.

Aside from looking for other events and using WinMTR, get your drivers and motherboard BIOS updated if not already done (as said, don't just let Windows install drivers). I don't know what else can be done aside from that. If there are absolutely no indications that you're having local connectivity issues (no packet loss or latency jumps between your PC and your router and no link disconnects) and no indications of issues on your ISP's network or between you and the game server, then it MUST be an issue with the game and/or server and there simply won't be anything you can do about it.

 

[zewoo]

Yeah well, I'm using windows 10 newest version, but blocked updates. My roommate was using windows 7 and is to this day. I updated bios like a month ago, drivers are always the newest for ethernet, from realtek main site, checked from bios site and reset it's driver to default, same thing happened. I can tell you the thing about hackers targeting my accounts, maybe it will help. So first account main, everything good for 3 months then verification codes are sent from Verify, like 10 one day next 3. I changed password then, even several times. And with same time disconnections started happening. Some time later, no account alerts from other locations, just sms. Yes, was using authenticator and have added phone number to battlenet account. Seems like they somehow bypassed 2fa and got to my account, some session hijack? maybe rather token.

And weeks later motherboard in pc is dead literally, no screen signal, no keyboard and mouse turning on, pc just boot and no responding. Bought another motherboard, everything works. I quit battlenet for a while, as I said all these things last since 2 years as I have mentioned. I will try to shorten all of this because it will really be too much. So basically, when came back to battlenet account same things happened smses, disconnections, same scheme then pc dead after time.

Okay, left main account. Created new account, same scheme happens pc is again burned. No, it isn't any coincidence, my temperatures were about 50 celsius. I was so desperated I deleted this second account. And again third account, now back after 1 year again, I didn't add phone number to account because it's evidence of starting point is obvious. So month playing on this account, nothing happens and last days disconnects, really strong password, no mails alerts login so it might not be related to hacker but maybe it will help. Always it happens after about 3 months I could say or 2. Disconnects also yesterday there were no longer disconnects, but just for few seconds ( I think it might be the cable, because It's really loose).

Other cables the shorter ones, the one I use is cat8 ugreen 30feet. So shorten one doesn't move while plugged in and the main one feels like it will drop in a moment. I know it might be two other problems, but sometimes not obvious things help. There were no signs anything is wrong before the motherboard stopped working.

Nothing suspicious working in the background, it could have been something linked to other processes. I don't know how they got to my pc but evidence is really obvious and these are not unlinked things. Somewhere I read that when I was launching diablo 3 they were also running malware on my pc but I can't verify if it hasn't just been running all the time. I didn't have performance issues, I didn't notice anything since all these hack events occured. I really need help with both these things that might be related. I don't want to waste money again on motherboard for x time.

 

[Ralston18]

Reference:

"Other cables the shorter ones, the one I use is cat8 ugreen 30feet. So shorten one doesn't move while plugged in and the main one feels like it will drop in a moment. I know it might be two other problems, but sometimes not obvious things help. There were no signs anything is wrong before the motherboard stopped working."

Use Cat5e pure copper, round UTP, 22-24 AWG cable.

No flat cable, no aluminum cable (or copper clad aluminum).

That Cat8 cable is not at all applicable and likely fake or substandard at best.

Terminations may be another issue.

 

[bill001g]

It is a bit unclear what you have done since there is a lot of different types of information in the posts. Software issue like DCOM events are very different than network issues.
I kinda suspect it is the game/blizzard if that is the only one that disconnects. Then again if you do not play a different game commonly you might not see it. Other than maybe live stream you will not see short outages.

It is unclear if you tested with winmtr. This will show you really have a network issue. Maybe try the very simple test of open a CMD windows and run a constant ping command to some common IP like 8.8.8.8. When you see issues in the game quickly switch over to this window. Mostly you are looking for packet loss but very large latency spikes over 100 or 200ms can cause issues also. If there are no issues in this ping command then it is not likely a network issue....could technically be a network issue in blizards newtwork since 8.8.8.8 is google.

If you do see issues with the ping then it might be work the effort to run winmtr or pingplotter. You can also do this manually with trace and ping commands which is what I tend to recommend because then you understand what you are actually testing.

 

[zewoo]

It is clear that it only happens in battle net. I tested if since these 2 years. Without battlenet everything fine with network, came back it started and only in diablo3. Now launched the game for 20 minutes, and it happened. Ping is okay like 30 in games, no spikes. Only thing in event viewer that happened right now was dns client errors 10014 network service (I'm using google dns right now). I tested some dnses with ipconfig, but it was without packet losses or anything. On google I have lowest, then cloudflare.

 

[zewoo]

then if it might be some blizzard issue what should I do? No one that I played with in d3 had these, literally no one I've asked.

 

[zewoo]

Also after the disconnect something weird happened in event viewer, it says always when opening administrative events: one or more logs contain errors and there is 4 microsoft (dxgkrnladmin, two hyper v vid admin and storage disk admin) all of them are marked access denied. I'm sending link for all these and previous distribuded com issues:

https://imgur.com/a/vVSm9Ib

View: https://imgur.com/a/vVSm9Ib
.

 

[Ralston18]

Are you able to provide full translations of those Event Viewer errors in English?

Or perhaps show them in English.

= = = =

Make and model router (or modem/router if combined)?

The router's logs (if available and enabled) may provide additional clues.

Who has full admin rightsd to the router? You will need help from that person.

 

[evermorex76]

dxgkrnladmin would clearly be an issue with DirectX. Hyper-V-VID-Admin and Storage-Disk relates to configuration events in Hyper-V for virtual machines. Are you using Hyper-V, running virtual machines? If not, uninstall the feature. Hyper-V does insert its own networking drivers to create virtual interfaces.

"one or more logs contain errors" usually means your event logs are corrupt but in this case seems to just be that you don't have permission to view those events. Are you using an administrator-level user account, or opening Event Viewer "as administrator"? If not, that may be why you get access denied on certain events. I normally never look at anything other than the standard System and Application event logs, as anything else is basically application-specific, but if you have something like Hyper-V that might be causing issues, then looking at those logs may also be useful (under Applications and Services/Microsoft/Windows

I've never in my life used the "administrative events" view. Just look in System and Application so that you're seeing all the events that happen at the time of the disconnects, even if they wouldn't show up in administrative events.

DNS client events can normally be ignored as they're usually spurious and are regarding non-user-facing things. "cxcs.microsoft.net" is related to Microsoft Customer Experience Center. If those events happen during these issues, it could be that since Microsoft bought out Activision Blizzard they've added some code to contact their servers to report issues.

You may try changing your DNS to simply use the default, pointing to your router which points to your ISP's servers, just to ensure there's no issue with using Google's for some reason. And now you've said that you know there's a cable problem, so...

You should enable updates in Windows 10. There's very little reason not to allow them, and especially if you haven't allowed updates for years. Just make sure System Restore is enabled and working so you can easily roll back any that might break something (which is not so often anymore with Win10), and as always you should have full backups being performed. And of course you're leaving yourself open to "hackers" abusing known vulnerabilities. (I'm not even going to get into trying to figure out how people are killing your motherboards or why they'd be doing it to you repeatedly.) Are you using anti-malware software other than Windows Defender which wouldn't be getting updates?

Your roommate continuing to use Windows 7 makes them "part of the problem" of the Internet being full of compromised machines being used for malicious purposes, and people being hit with malware and ransomware.

Diablo 3 came with DRM software, as well as the always-online requirement, which a lot of alarmist people will call "malware".

run a constant ping command to some common IP like 8.8.8.8

Pinging the actual game server would be more informative most likely, and if using WinMTR it ought to be the same thing.

If the issue does seem to be with battle.net or Diablo 3 specifically, the only thing you can do is ask their support for help, like somehow enabling detailed logging so you can see what the software is doing before and after a disconnect. But if the problem is simply inherent to the game, just some bug, you're unlikely to ever get a fix or even acknowledgement that there is a problem.

 

[bill001g]

Pinging the actual game server would be more informative most likely, and if using WinMTR it ought to be the same thing.

Winmtr is better but the ping command is built into windows so easier for new user.

Problem with pinging a game server are all the immature people who play video games. Many game companies have rigged their servers to not respond to ping commands because someone gets mad and then does denial of service attacks against the server using ping. In addition many times these are not the actual server it is some kind of load balancer with many actual machines representing a single server. If one of these machines has issues the ping traffic may not be forwarded to the same physical machines as the game client is running on.

It mostly doesn't matter, if ping to 8.8.8.8 is good then there is no issue with his network. Even if ping to the game server would show a issue it is something blizzard or their ISP would need to fix.