Virgor the errors on active X can be the result of permissions...
The program is not allowed to execute active X aps, and is failing.
Either way.. i will not tell you to disable your permissions because that is saving u from picking up a malware virus on one end.
however you are doing some testing on very dangerous areas.
(dangerous as in DATA being wrong... not dangerous as in you can get hurt)
When doing OS tweaking / Testing, we always do it in a controlled windows enviorment.
Meaning fresh install, brand new OS.
this rules the possibility of ADDON's interfering, and causing problems with tweak testing.
Some programs may not like the fact your cpu goes in C1E, or may produce funny results when overclocked / downclocked / C1E'd.
When testing features on cpu like you are, we do that on a controlled machine.
A Machine which is displaying cpu temps / core temp / voltages on your rail (hwmonitor / multi meter) and a killa-watt at the wall to see if load reductions are present.
the method your going by is the visual method (feels faster / responsive) with an unrecorded number test.. (FPS)
At best you can see load temps... but not full load values, so you have no real clue if u got a net improvement, cuz the temp reduction could of been changes in your room temp, or a nice breeze going though your room.
I am not telling you to stop because your doing it all wrong..
I am actually applauding you for getting technical in trying to figure things out.
But i am also warning you, that u will run into a lot of errors, because the path your on, was a path most reviewers like me have treaded and we saw a very deep end.
But this is a path everyone must take and learn... you learn more from errors, then successes... a good tester/reviewer is one who knows many failures so he knows what never to repeat again when he is facing the public.
