>It looks like that error is related to a performance counter for the BITS service, rather than the BITS service itself.
>Have you seen this link: https://social.technet.microsoft.com/Forums/office/en-US/ab7f88bd-027e-4515-898a-fcc2627aa368/cwindowssystem32bitsperfdll-failed?forum=winserverManagement

This is a generic issue many are facing. I have been working a little bit on this and pretty much all solutions do not work. I do not need that on production servers and it should be simple to disable that. I applied something this morning which I believe might resolve the issue. That suggestion was very difficult to find.

The following command returns what DLL is invoked:

lodctr /q

The following command will then disable BITS support, which is the one our Web servers complain about:

lodctr /d:BITS

Re-executing the first command again will now show BITS in disabled mode instead of enabled.