Thanks for your replies everyone! ehh long day at work. So here's what I've gathered:
As far as I know, it shouldn't behave like that. Run windows "Resource Monitor", click CPU tab & see if any process/service using CPU resource.
Regarding VCORE offset, in layman explanation, you know when not overclock, stock frequency can run stable with stock voltage, so when overclock, to run stable you'll need to adjust the VCORE. The advantage using offset over manual is that when CPU is idle, the VCORE will reduced, which means less operating temperature. With manual, even when CPU is idle, the VCORE still the same & this increase operating temperature. VCORE offset example, let say VCORE=1.33V when under load on default (not overclock), when overclock you need at least 1.38V to run stable, so what you do is set offset to 0.05 & you'll get 1.33V + 0.05 = 1.38V.
Thanks for this explanation of the offset. I tried the offset at 100 bclk and it worked like a charm! Unfortunately the max ratio is 43 so clocks are limited. The board will not even boot at 125 bclk with an offset. From what I have heard, the signal from the processor that controls that does not work at anything other than 100 bclk
I checked my power options, and I was using high performance, but the CPU management was at 5% minimum. I changed the profile to balanced just in case. I also enabled the c3, c6, and c7 manually in the UEFI. So when I booted up I didnt notice which one worked, but it is down-clocking, and with auto vcore, it is down-volting!
Now I just have to fiddle with my RAM a bit. I can't get it stable @ 2000Mhz with looser timings and 1.5v. I'm currently running at 1666Mhz.
Thanks again!Edited by Rmerwede - 7/19/12 at 6:25pm