The WMI error is a known issue:
From Microsoft's KB2545227:
Cause:
This originated in the Windows 7 SP1 DVD/ISO creation process. There
was an issue in the creation process that caused a WMI registration to
remain in the DVD/ISO. Since the registration is designed to work only
during the DVD/ISO creation process, it fails to run on a live system
and causes these events. These events are not indicative of any issue
in the system and can be safely ignored. If however you want to
prevent these events from getting generated and want to remove this
specific WMI registration manually, please follow the steps mentioned
in this article for running the workaround script.
They offer a FixIt to fix the problem, plus manual instructions:
In Notepad create a new document named Workaround.txt
Copy the following script into notepad:
strComputer = "."
Set objWMIService = GetObject("winmgmts:" _
& "{impersonationLevel=impersonate}!\\" _
& strComputer & "\root\subscription")
Set obj1 = objWMIService.ExecQuery("select * from __eventfilter where name='BVTFilter' and query='SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA ""Win32_Processor"" AND TargetInstance.LoadPercentage > 99'")
For Each obj1elem in obj1
set obj2set = obj1elem.Associators_("__FilterToConsumerBinding")
set obj3set = obj1elem.References_("__FilterToConsumerBinding")
For each obj2 in obj2set
WScript.echo "Deleting the object"
WScript.echo obj2.GetObjectText_
obj2.Delete_
next
For each obj3 in obj3set
WScript.echo "Deleting the object"
WScript.echo obj3.GetObjectText_
obj3.Delete_
next
WScript.echo "Deleting the object"
WScript.echo obj1elem.GetObjectText_
obj1elem.Delete_
Next
Save the text as Workaround.vbs
Close Notepad
Open an elevated command prompt:
a. Click on start
b. Click on Programs
c. Right-Click on Command Prompt
d. Choose run as administrator
Change Directory to the one containing workaround.vbs
(Example CD c:\users\%username%
)
Run cscript workaround.vbs
After running the script the Event ID 10 errors related to this event should stop occurring. This does not remove any of the existing entries in the Event log, they would need to be manually cleared out of the application event log.
For the "The NEWDRIVER service failed" issue:
You have a service named "NEWDRIVER" registered with the system, but the file(s) it needs to run are missing. Since the files are missing, and your computer is behaving OK, you can just remove the reference to the service.
You should be able to do this from an elevated command prompt, with the sc
(Service Control) command. Eg.:
sc delete NEWDRIVER