Windows 10: why are there very many rapidly occurring events in event log?

i couldn't find a good "topic" for this post.my event viewer shows events appearing continuously and very rapidly in 3 windows logs, going back seemingly forever: application . . level: almost all information . . source: security-spp security . . keywords: all are audit success system . . level: most information, some warning for each log an estimate for events per day is in the 100s and maybe over 1,000. for each log i can copy 100 or more events into a text file. can i send this to someone who can see in more detail what's going on? this can't be good... can it? why is this happening

:)

 

Event viewer error with event id 10016

Hello,

Thank you for posting your query on Microsoft Community forum.

I understand that you are getting an error “DistributedCOM 10016” in the event viewer logs.

• Do you face any issues on the computer?
  
• Have you made any recent changes to the computer?

This problem may occur if either of the following conditions is true:

• A program with the class ID (CLSID) that appears in the message tries to start the COM component by using the DCOM infrastructure. However, the user does not have the required permissions to start the COM component.

• The Network Service account does not have the correct permissions.

Event logs are special files that record significant events on your computer, such as when a user logs on to the computer or when a program encounters an error. Whenever these types of events occur, Windows records the event in
an event log that you can read by using Event Viewer. Advanced users might find the details in event logs helpful when troubleshooting problems with Windows and other programs.

If you do not have any issues with app or any other program I would suggest you to ignore it.

Keep us posted if you face any issues related to Windows in future. We will be glad to help you.

 

NTFS Compression on Event Logs

Anyone ever try doing NTFS compression on their Error Logs?
It's all text, so it should compress pretty well.






Anyone else try this? I suppose it's only useful in server-land when you have huge event logs..

To compress:
Run services.msc
Find Event Log and set to "Disabled"
Reboot
Go to c:\windows\system32\config
NTFS Compress anything that ends in .evt
Run services.msc
Find Event Log and set to "Automatic"
Reboot

 

Display driver nvlddmkm stopped responding and has successfully recovered. Event ID 4101.

I followed the steps as suggested, but unfortunately, the issue continues to occur, with the same errors in the event log as I first described. I would appreciate any additional suggestions.