Windows 10: Fresh Win 10 Install, lots of event errors and warnings, audit failures, microstutter...

I get the majority of these events including security audit failures, DNS/DHCP errors, DistributedCOM warnings, CertificateServiceClient-CertEnroll errors, ModernDeployment-Diagnostics-Provider warnings, WLAN-AutoConfig warnings, and Kernel-PnP errors on both Windows 10 and 11. I'm currently on a barebones clean install of Windows 10 created installation media and cleaned my whole drive and I'm still getting these events, most of them after I installed drivers. The problem with my system is that games have this microstutter/frametime spikes. When I play online players sort of skip around the

:)

 

System Integrity Event 5061 Security Audit Failure

Anyone notice that with the rollup update from August 17, that the Security section of Windows Logs in Event Viewer have now all been renamed to simply "Information" instead of "Audit Failure" or "Audit Success". Ever since upgrading to Win 10, I've
been getting a lot of Audit Failures with Event ID 5061, which I presume is either related to one or more of the Nvidia drivers/programs, or is related to some other MS attempt to login to some server somewhere that fails (for reasons I've been unable to trace).
MS has been getting a lot of questions on these forums about event 5061, and apparently lots of people were alarmed about the reports of "Audit Failures" for "System Integrity", believing that it meant something was definitely wrong with their systems.

I just noticed the change in language tonight in event viewer. Now everything, and I mean all events listed under Security logs is listed as "Information". Failures still show a "lock" icon, and success shows a "gold key" icon, but the descriptions are
now simply "Information" only. You have to actually look hard to see whether it's a "failure" or "success".

Likely related, my Win10 system is unstable, and the Nvidia drivers keep crashing and recovering and then eventually crash the system. It does not seem to be at all predictable. I can be playing Solitaire, or looking at maps, or reviewing pictures in the
Bing Photo Archives, or just downloading e-mail. The computer will stay up for a day or two and then whammo. Instability, crashing and a need to continually reboot until things calm down. Oh, and throw in a couple of BSOD's too, with the message "Your
PC crashed ; (" and a report generating somewhere.

I figured Windows 10 might have some issues and I used a lot of preview builds with better luck than I'm having with a clean install of the final release version (downloaded and installed with an ISO). The machine is an older computer, running an Intel Core2
Quad processor, but it runs both Win 8.1 and Win 7 with no issues at all....I mean flawlessly. Whereas Windows 10, installed on its own partition on a clean install, is just completely unstable, and unfit at all for any production work.

 

Security Audit Failure Event 5061 In Windows 10

Hello,

A failure audit event is triggered when a defined action, such as a user logon, is not completed successfully.

The appearance of failure audit events in the event log does not necessarily mean that something is wrong with your system. For example, if you configure Audit Logon events, a failure event may simply mean that a user mistyped his or her password.

Advanced Security Auditing FAQ

 

Audit failures every reboot - Event 5061 - Cryptographic operation.

Before I upgrade my 10 to the Spring version, I did some more digging.

I looked at the sequence of Audit Successes before and after each Audit Failure - maybe they're related? Maybe the steps mean something? In the link below, I have pasted the "General" subwindows for the Event Viewer events closely preceding, including and following each of the two Audit Failures in my most recent bootup.

There seems to be some kind of pattern of the machine looking at the key, DELETING it, then looking for it again, then throwing the AUDIT FAILURE - maybe because it just deleted the key and the key isn't there any more - and then re-creating the key. Is the AUDIT FAILURE just the good result of a test that the key was successfully deleted?

But WHY is the machine doing this? Why delete and recreate? What's really going on?

Here's the link to the Word Online document in which I've pasted both Event Viewer sequences:
<THIS LINK>

Any thoughts? (And am I interpreting the events correctly anyway?)