There is a procedure for dealing with the 10016 DCOM errors. Check the wording of the description in the Event Log entry, but it should suggest that there wasn't sufficient security privilege to a Class-ID and App-ID to access or activate.
Here's one of the links I used to take notes and plan my operations -- from Windows 10 Forums:
Event ID 10016 -- DistributedCom
You first must identify the component involved which is indicated through the ClassID and AppID. It makes the search through the Component Services list easier. Push comes to shove, by brute force you could search visually for the App-ID key through the Component services window and identify it that way.
You then have to take administrative ownership of the component, at which time you can alter the access and activation privileges on it.
Before you go forward with that, download BlueScreenView and use it to analyze the last BSOD mini-dump file, noting which drivers were involved in the crash. You can reinstall those drivers, and extend the effort to other drivers as well.
Then, if Event ID 10016 continues, see if it always points to the same ClassID and AppID. If you reboot -- does it reoccur? Sometimes there are more than one set of ClassID and AppID involved, and you'll have to work on them separately. Likely not, but I'd think it's possible.
PS This is a tedious pain in the ass.