Thanks for your replies. I have just been learning more about the way the powersaving feature works for the Gigabyte mobos. So now I understand that with C1E enabled the processor will stay at a lower setting, only moving up as needed.
I have experimented both with enabling C1E and disabling it in BIOS and then doing tests with prime. And this has led me to wonder: what triggers these multiplier changes?
Right now I have things set at 440 x 8 (3.52 ghz), and I have C1E enabled. If I run prime95, and watch in coretemp, I never see it move from 6 up to 8, despite the fact a processor-intensive task is running. Why is this? Would coretemp not register this change, and is there another piece of software I would need to see this shifting? Also looking at the CPU panel in easytune, the multiplier always remains at 6, so I'm left wondering if the feature functioning properly?
I appreciate the feedback.
Message edited by intzor on 07-09-2009 at 11:55:56 PM
Just disable C1E ... i personnally never let it ON. Power saving ? .... my computer use 150W when idling ... so i just turn 2 room lights OFF and there is the saving ...
Disable C1E, your VTT and PLL seems fine. What about temps ?
very odd, all cores are at 100% but it is staying at x6.0.
I am looking at it in both CPU-Z and Core Temp.... both show 6...
does this mean there is no way I can overclock unless I turn C1E off? or could there be another BIOS setting causing a conflict, which is causing this?
Ok I was able to figure out the problem: it was having EIST enabled that was causing the multiplier to stay stuck at 6. I turned off EIST and now the C1E function is working properly.
I'm wondering if overclocking can cause problems with Vista sleep? Since doing my OC I'm having trouble getting the comp to wake up from sleep. When I go to wake it up the following happens:
fan comes on, there is sign of comp accessing my optical drives.. then everything goes dark.. same process repeats ad infinitum
if I turn the comp off at the PSU, then turn it back on after a few seconds, it will reboot, and allow me to restore my sleep state from disk... but that is pretty inconvenient...
never had any problems waking up from sleep before.. any ideas?
I'm wondering if overclocking can cause problems with Vista sleep? Since doing my OC I'm having trouble getting the comp to wake up from sleep. When I go to wake it up the following happens:
fan comes on, there is sign of comp accessing my optical drives.. then everything goes dark.. same process repeats ad infinitum
if I turn the comp off at the PSU, then turn it back on after a few seconds, it will reboot, and allow me to restore my sleep state from disk... but that is pretty inconvenient...
never had any problems waking up from sleep before.. any ideas?
vista's sleep mode is iffy at best - some systems with nvidia video chipsets still have issues, and overclocking also causes issues with it (well not vista but standby etc and coming out of it) - try disabling power mode "hybrid sleep" and google a guide to set the sleep mode to Hybernate (suspend to disk?) rather then STR/S3+.
Just disable C1E ... i personnally never let it ON. Power saving ? .... my computer use 150W when idling ... so i just turn 2 room lights OFF and there is the saving ...
Disable C1E, your VTT and PLL seems fine. What about temps ?
I left it on with my overclock and i manage to get my Q6600 to idle at *just* under the stock speed (2.334ghz) and max out at 3.5ghz (stock Q6600 - 2.4ghz).
to get your q6600 to 3.2 all you do is set your multi to 8 clock your ram at 400 and set xmp to profile 1, and mek sure your mem is on the 2.00d setting and put your cpu on 1.325 volts, and guees what you will have 3.2 ghz
and you don't have to disable c1e, I don't know why people keep saying that, it has nothing to do with stability or overclocking ability.
and to clock it to 3.6 just put your multi on 9 and fine tune your voltages, it's no harder than that
to get your q6600 to 3.2 all you do is set your multi to 8 clock your ram at 400 and set xmp to profile 1, and mek sure your mem is on the 2.00d setting and put your cpu on 1.325 volts, and guees what you will have 3.2 ghz
and you don't have to disable c1e, I don't know why people keep saying that, it has nothing to do with stability or overclocking ability.
and to clock it to 3.6 just put your multi on 9 and fine tune your voltages, it's no harder than that
do NOT just jump your overclock drasticly like suggested here
Thanks for your suggestion to disable sleep and enable hibernate. I did this and the hibernate function seems to be working as it should.
The downside with this is that it takes me longer to get back to my desktop than when using S3, since basically a reboot is needed, whereas when S3 was working for me (back before I OC'ed) I was able to get back to my desktop with the click of a mouse. But at least I don't need to reach back there and turn the PSU on and off as I have been having to do recently, so this is definitely the better way.
Message edited by intzor on 07-13-2009 at 12:40:48 AM
A quick note in Gigabyte OCing:
It is usually recommended that you should NOT install the DES (Dynamic Energy Saver) software. All the EP-xx boards have this software on the driver DVD. If you have already installed DES I highly recommend you uninstall it before doing a OC. The DES software can/may lead to system instability when OCed.
do NOT just jump your overclock drasticly like suggested here
How is that drastic when I have run that for a year with my voltage never getting over 1.24 volts at 3.2 ghz, If you think that is drastifc, you better lock yourself in your room, that is mild compared to 4 ghz people are getting from a q6600. Oh and by the way the EP45-DS3L can handle a 1600 fsb no problem.
How is that drastic when I have run that for a year with my voltage never getting over 1.24 volts at 3.2 ghz, If you think that is drastifc, you better lock yourself in your room, that is mild compared to 4 ghz people are getting from a q6600. Oh and by the way the EP45-DS3L can handle a 1600 fsb no problem.
Ummmm i managed to get my (early batch) E6600 clocked to 3200/1600 with stock cooling on an 965 based motherboard (ASUS P5B Deluxe/Wifi-app) back in the day - still running as an old rig even today with the same settings - i was one of the first to put the 4mb cache + 1600fsb "limit" myth (at the time) down - dont tell me 1600 is any sort of issue.
oh and im not talking about 4ghz and that sort of drastic, im talking step by step to get the most out of the cpu - the correct way, and a Q6600 @ 4ghz = super batch, super cooling, or super stupid (1.7+ on vcore)
well if you guys think having stock voltage set running the multi at 8 with the mem set at 400 which would give you a 1:1 on the memory with average voltage use not being above 1.25 volts on the cpu which is below 1.325 volts recommended on a motherboard that handles the fsb up 1600 which is the qdr for the mem being set at 400 is drastic? Then I must be a psycho for doing that the first time and leaving it like that for a year.