My 2 cents on a similar problem which I hope will help you solve the trouble:
I got crazy for 3 days with a brand new W10 installation from scratch on some 3 yrs PCs - and that happened on one of the same PCs, all identical hw pieces, using W8.1, but I didn't care much 'cause I was going to upgade to W10 - on which I also installed Hyper-V to keep an old Windows XP installation, and Hyper-V uses a so called "virtual switch" to bind the physical netowrk card of the host to the virtual network card used by the VM (I configured it in "external" mode); I specify this becasue of a reason which will be clear later on in the explanation of the problem.
Well to make it as shortest as possible, after I've installed all of the drivers and basic sw tools and applications, liek Office 2013, I noticed that ALMOST each time I requested the "Manage" function from "This PC", Windows would return a generic "software exception" error just before opening the "Computer Management" MMC panel, which after that would perfectly work, though. Unforetunately, the Windows LOGs would show some "ntdll.exe" error related to the summoning of "compmgmnt.exe", and that was a pretty freaking enough warning realted to an unknown system trouble; after a few, but long, tries, I discovered that removing the Realtek ethernet driver pack (installed from the latest version available on Realtek's site) would fix the trouble, so I thought it was a buggy driver "only", even if I found no reference/evidence on the Internet about that, and in fact removing it from "installed programs" left me without network, after the first reboot, but everytthing else seemed fine... JUST that at the next reboot, W10 would find the driver again (usinf Windows Update) and install the network again, but even then things seemed fixed... UNTIL I reconfigured the HyperV's VM vritual switch and the darn error pop-up again in its horrific style; I swear I got crazy for so many other hours, until I found for a total lucky chance this thread on your support site and, guess what, I HAD INSTALLED the latest version od PDF Creator which brings with it PDF Architect... uninstalling the latter indeed made me go back in peace with my freshly installed, cleaned and so polished updated installations... I could imagine everything but a sw like yours causing such a peculiar intercation with other system components of that kind (guys, it bothers NTDLL.EXE...!!!), but hey... IT's made of this, right?