It happens, no problem.
I took a quick look at the event logs. I'm going to say that combing through event logs looking for performance tuning is more work than I am willing to commit to doing. I asked for the data because it was the easiest way to answer your question about the Error events you're seeing.
Here's what I cherry picked from the information you posted:
Make sure you have sufficient disk space to operate your machine.
Log Name: System
Source: volsnap
Date: 2015-01-08T11:53:10.809
Event ID: 24
Description: There was insufficient disk space on volume C: to grow the shadow copy storage for shadow copies of C:. As a result of this failure all shadow copies of volume C: are at risk of being deleted.
Without further research, I'm not certain about this, but the description lends itself to performance. It's probably normal throttling but it's an area you can look at to see what's causing it to throttle back. It is not a serious condition.
Log Name: System
Source: Microsoft-Windows-Kernel-Processor-Power
Date: 2015-01-08T11:36:45.238
Event ID: 37
Description: The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 28 seconds since the last report.
These both relate to Western Digital and should be researched. If you don't use the WD backup service - disable it in Services or the Services tab in MSconfig. If you do use the WD backup services, fix the configuration. The rules are wrong or you didn't tell it where to backup the data.
Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 2015-01-09T12:26:45.000
Event ID: 10005
Description: DCOM got error "1068" attempting to start the service WDBackup with arguments "" in order to run the server: {81213AB4-5937-4340-88CD-66B4BC80DF73}
Log Name: System
Source: Service Control Manager
Date: 2015-01-09T12:22:56.910
Event ID: 7001
Description: The WD Backup service depends on the WD Rules service which failed to start because of the following error:
The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
Again, this points to disk space, specifically your paging file (virtual memory)
Log Name: System
Source: Microsoft-Windows-SharedAccess_NAT
Date: 2015-01-09T12:23:27.000
Event ID: 34005
Description: The ICS_IPV6 was unable to allocate bytes of memory.
This may indicate that the system is low on virtual memory, or that the memory manager has encountered an internal error.
I recall reading something like this "Mbam missing file" but you'll have to dig deeper. See if Malwarebytes forum has anything on this
Log Name: System
Source: Service Control Manager
Date: 2015-01-09T12:22:35.694
Event ID: 7001
Description: The MBAMService service depends on the MBAMProtector service which failed to start because of the following error:
The system cannot find the file specified.
That's about it.
Conclusion: I believe the many errors you see in the Event log revolve around disk space and also this event
Description: The WD Backup service depends on the WD Rules service which failed to start because of the following error:
The service cannot be started, either because it is disabled or because it has no enabled devices associated with it
There are tens if not hundreds of the WD Rules events. If you have disabled that service, re-enable it. The old events remain in the log, but new ones won't be generated.
It is tedious work, but if you're looking to get those few milliseconds, you have to do the heavy lifting.
Sorry this wasn't a "here ya go, these things will help you" post.
It's more an answer to your query re: Error level event logs and a "point you in the right direction" post.
Bill
.
