Though it would need to be analyzed more exactly it is likly related to having more interrupts if your only change was switching the graphics card. The interrupts let the drivers run (scheduled by OS) and those consume some resources not to speak about the general loss in performance by context switches. You do not see this consumption of CPU resources in task manager.
But again, would need to be analyzed with according tools to be sure about this.
Also Nvidia Display Control Center could cause this. You should get rid of this and install only a driver.
How to identify with a simple method? First check your idle load with task manager, do nothing but watching task manager, how much is it? If it is very low than it is caused by interrupts (kernel software = driver). If it is not very low than it is caused by some user software (= any application) and you can identify it with task manager.
For now i uninstalled the nvidia 3d vision and updater stuff, which installed as a part of the drivers, kept the driver itself, some HD audio and PhysX stuff.
Anyway it did not help

I downloaded the PassMark CPU benchmark to try something else to compare and there is no problem there, i ran it multiple times and everytime i got about the same score around 11500 points, what is in line with the CPU benchmark table they have on the Passmark home site (995x 3,6GHz gets 10800 points).
Ok, i can confirm the score decrease is down to latest Nvidia Drivers, 270.61. I uninstalled them and driver-sweeped them, rebooted and then ran Cinebench about 10x with no drivers installed (and pretty big desktop icons

) and i kept getting consistenly the proper score in 9,55-9,65 range. Even rebooted again to see, if its no coincidence, but no, its the drivers... i reinstalled them back and voila: 8,8 scores again.
I downloaded and ran several times the older CB (R10) and got consistent scores in the 29500-30000 range, + the aforementioned Passmark was pretty consistent as well. So its probably just a R11.5 issue, though the question is now, if this affects for example Vray or 3dsmax´s Mental Ray, or any other app i might use as well. I already wrote a topic about this on Nvidia forums, do you think there is a possibility they might look into it and fix it in the next drivers?