Cool'n'Quiet stopped working on my 1090T after massive OC

[arterius2]

Need some advice from someone with experience on this, as I have never encountered this issue before

I'm running Windows 7, power management is on "balanced"
Cool'n'Quiet was working until today, after I ran few hours of Memtest86+ on my machine, I boot back into Windows, and notice that all my cores are stuck at their highest clock setting - 4.25ghz, I know that this doesnt sound like such a bad idea, but my machine is on 24/7, and I'd like Cool'n'Quiet to kick in when its on idle. Just few hours before this CnQ was working perfectly, where it would throttle down to 800mhz when its idle. I did not change any of the BIOS setting that would have an effect on this, (CnQ and C1E is enabled in BIOS), then I started playing around with my OC, I notice that if I bring my OC down to around 3.8ghz, CnQ kicks in again

so my real question is, could this possibly be related to my OC? does CnQ turn itself off automatically once you OC past 4.0Ghz mark for stability reasons? or did i damage the motherboard or CPU by over-volting (which I managed to reach @ 1.64v), or is this just a windows 7 issue, in which the windows changed its settings without my knowing and allowed it self to prevent CnQ after a certain OC? (due to the fact that i crashed often while in windows from attempting OC to a higher clock rate)

if anyone can shed some light on this, would be much appreciate!

 

[warmon6]

Need some advice from someone with experience on this, as I have never encountered this issue before

I'm running Windows 7, power management is on "balanced"
Cool'n'Quiet was working until today, after I ran few hours of Memtest86+ on my machine, I boot back into Windows, and notice that all my cores are stuck at their highest clock setting - 4.25ghz, I know that this doesnt sound like such a bad idea, but my machine is on 24/7, and I'd like Cool'n'Quiet to kick in when its on idle. Just few hours before this CnQ was working perfectly, where it would throttle down to 800mhz when its idle. I did not change any of the BIOS setting that would have an effect on this, (CnQ and C1E is enabled in BIOS), then I started playing around with my OC, I notice that if I bring my OC down to around 3.8ghz, CnQ kicks in again

so my real question is, could this possibly be related to my OC? does CnQ turn itself off automatically once you OC past 4.0Ghz mark for stability reasons? or did i damage the motherboard or CPU by over-volting (which I managed to reach @ 1.64v), or is this just a windows 7 issue, in which the windows changed its settings without my knowing and allowed it self to prevent CnQ after a certain OC? (due to the fact that i crashed often while in windows from attempting OC to a higher clock rate)

if anyone can shed some light on this, would be much appreciate!

Whats your windows power management set to? If it's set to like "high performance" or something like that, it could be your problem.

 

[arterius2]

i've stated in my first post that power management is set on "balanced" @ start of 2nd paragraph

 

[loneninja]

Most motherboards usually disable Cool n Quiet once you start overclocking, I've never seen it work to a certain clock and shut off afterwards. Have you checked in your power options that the cpu power states are configured properly? You'll find this somewhere in the advanced settings of your power profiles(balanced is one of them)

1.64V is dangerous for the processor, even 1.5V is pushing it for 24/7 use in my opinion. I highly doubt you damaged it though, would of had to run at that voltage for a while.

I've also got to wonder why you set up such a power hungry beast when your concerned about power consumption in a 24/7 computer.

 

[warmon6]

i've stated in my first post that power management is set on "balanced" @ start of 2nd paragraph

Opps, sorry about that.

overlooked that part.

 

[loneninja]

Forgot to mention this before, but if you can't get cool n quiet working properly on your motherboard with that overclock, you could always use K10stat to downclock within windows. It works great, I've been using it for over a year now because my motherboard disabled cool n quiet if I adjust any cpu settings in the BIOS.

 

[arterius2]

my motherboard is an Asus Crosshair IV Formula, it comes with bunch of bells and whistle so you can never be too sure.
I've checked the power options, I did not change anything, the cpu power state was left as-is, which is 5% @ idle and 100% at load.
I do not run the CPU @ 1.64V, I just meant that I've attempted at that voltage. for 24/7 use i've stabilized it @ 4.27ghz @ 1.56V.

as for my concern for power consumption, ill answer this in a way that makes sense to me, and hopefully to you....
My work warrants me to use a machine of this caliber 24/7, 3D modelling during the day, let it render during the night, however, I have my personal concern for the enviroment and I do believe in green computing so when im surfing a webpage or taking a nap or lunch, id rather have my computer saving those watts.

 

[arterius2]

Forgot to mention this before, but if you can't get cool n quiet working properly on your motherboard with that overclock, you could always use K10stat to downclock within windows. It works great, I've been using it for over a year now because my motherboard disabled cool n quiet if I adjust any cpu settings in the BIOS.

this wouldnt be such a big mystery if yesterday I didnt see with my own eyes that at 4.27ghz OC, both cpu-z and core temps shows CnQ working as it throttles down to around 800mhz idle, and back up again when i run an application.

 

[shortstuff_mt]

Are you sure you just don't have something like a virus scan using cycles and not allowing CnQ to go down to 800MHz? I know it sounds like a dumb question, but sometimes the solution is the most obvious thing that's easy to overlook. Check task manager and see if there's something running in the background that you didn't know about.

 

[FALC0N]

if anyone can shed some light on this, would be much appreciate!

My understanding is that CnQ doesn't function correctly when you increase the multiplier.

It does work properly with bus overclocking though.

 

[arterius2]

Best answer selected by arterius2.

 

[arterius2]

thanks, I think you are right, @ 250x17 CnQ is working
but @ 200x 21 CnQ is not working. looks like it is the multipliers

 

[warmon6]

thanks, I think you are right, @ 250x17 CnQ is working
but @ 200x 21 CnQ is not working. looks like it is the multipliers

Well, i will certainly keep a mental note of this for future reference. Never knew there was a problem with CnQ when overclocking.

It certainly amazing that there almost always something you dont know and it's practically in your face everyday. Guess it just how life like to play with us. :lol:

 

[arterius2]

Well, i will certainly keep a mental note of this for future reference. Never knew there was a problem with CnQ when overclocking.

It certainly amazing that there almost always something you dont know and it's practically in your face everyday. Guess it just how life like to play with us. :lol:

absolutely, exactly my thought =)