Q6600 not reflecting BIOS overclock.

[Krynj]

So, since pretty much my 2nd or 3rd boot, I've had my Q6600 at 3GHz. But just the other day, I noticed in Core Temp that my CPU has been put back to stock. I promptly restarted, went into BIOS, and to my surprise, 333x9, manual clock specification enabled.

So, what gives? Why don't I see 3GHz anymore?

Mobo is GIGABYTE GA-EP35-DS3L

 

[clarkey01]

I wouldn't worry too much, windows reports me as at stock, but CPU z sees my OC and I know from frame rates that the OC is working.

 

[Krynj]

I should add, CPUZ also sees my multiplier at 266 as well. Everything used to read the 3GHz OC, but now, it just doesn't.

 

[Drsignguy]

I have 2 gigabyte boards ( ep35c-ds3l and p35-ds3l ) If it gone back to default levels, that means it didn't like the overclock instability. You had to have rebooted during that time for it to have gone back to defaults. You can save the settings by using that feature in bios by hitting F11, and loading by hitting F12.

 

[Krynj]

It was Prime95 stable at 3GHz. But, I do think what happened is that my computer was turned off by means of holding the power button while I was away for a couple days, which may have set it back to defaults. I will give that a try though.

 

[Krynj]

No luck there either. I'm really quite stumped here. I changed nothing, and now it just won't go to 3GHz. Quite frustrating.

 

[Drsignguy]

Ya, I was going to say too that sometimes if the memory isnt stable it will go back to default. doesnt do it all the time, just when its way off kilter.

Here is a site that was linked from here from another thread and I tried this stress test. I used it and it really lets you know if you are stable or not in about 8 mins with 1 pass.

 

[Krynj]

Thanks for the link, but there's really no way I can stress test at anything other than stock right now.

 

[Shlong]

Since you have an EP35-DS3L you might have the Dynamic Energy Saving mode on which would lower cpu speed when doing normal functions and increase your cpu speed when needed.

 

[Drsignguy]

Originally posted by: Shlong
Since you have an EP35-DS3L you might have the Dynamic Energy Saving mode on which would lower cpu speed when doing normal functions and increase your cpu speed when needed.

I think this a software package that comes with the board on the DVD. You have to install it in order to use the Energy savings. So, if Shlong is correct and you did install it, this would be an issue. But if you haven't installed it, then don't worry about it.

 

[Krynj]

I never activated it, so, I'm not sure how it would have turned itself on.

 

[VirtualLarry]

Gigabyte boards are legendary for up and failing to hold there overclock. Your board has gone bad, buy another one. Dont bother trying to RMA, gigabyte doesnt support overclocking, even though those features are advertised.

 

[Shlong]

I bought the same board EP35-DS3L (your sig says DSL3 though) not too long ago. The only times I had problems where the overclock didn't hold was a) when I had the memory divider not at 1:1 b) EIST & C1E enabled in Bios c) DES software installed (which would show my speed in cpu-z as 2.4 ghz or so at idle and 3.3 ghz once I did something cpu intensive).

 

[Krynj]

I'm almost positive what caused this was an improper shut down (not done by me of course). I tell my room mates that if I'm gone for a couple days, and my computer's on, feel free to shut it off by simply pressing the power button, which then shuts it down via Windows shut down process. I'm pretty sure one of them just held the button for 5 seconds and shut it off, as it was reading 3GHz during the previous windows session.

I never changed any memory or FSB timings. Just multiplier and voltage. I was stable for weeks through a series of tests, benchmarks, etc. Never had even the slightest problem.

 

[Krynj]

So has my board really gone bad?

 

[Drsignguy]

Don't know, Have you tried your Over clock settings again? If you tried, and it keeps going back to default levels, try clearing cmos by pulling the battery and wait a few then reinstall the battery. Then try a small overclock to see if it takes....

 

[Krynj]

I've tried OCing again, with no luck. I suppose I could try a battery pull as a last resort.

 

[Idontcare]

Originally posted by: FetusCakeMix
I've tried OCing again, with no luck. I suppose I could try a battery pull as a last resort.

I have DS3L and this issue is common.

What happens is that the BIOS is set to error on the side of caution and pretty much assume that any computer reboot or system shutdown which isn't "clean" must be a bad overclock.

To "clear" the lingering memory of this false-positive you have to unplug the PSU from the outlet and set the mobo clear cmos jumper and leave it like that for about a minute.

Then set your clear cmos jumper back to default, then plug the PSU back into the wall. I have confirmed repeatedly that you must unplug the PSU from the wall to make the process work.

The next thing you must do when your system reboots is go into the BIOS and first select the load defaults option, save (F10) and reboot.

Then go back into the BIOS and setup your OC options. Save and reboot.

Now at this point in the timeline there is some kind of reboot/cold-boot counter in the BIOS and if it doesn't register a controlled shutdown followed by a clean cold-boot then it will assume that any subsequent reboots (initiated by you, windows, or a failed OC) are all counted as failed OC's.

So once you set your OC settings and the BIOS does it's mandatory reboot to get out of the BIOS screen the very next thing you need to do whenever the reboot is complete and you are in windows or linux is you must do a hard-shutdown (not a restart). Let the computer sit at least a minute after shutdown before booting again.

This sets whatever register Gigabyte uses for tracking "known good BIOS settings" as your OC settings and now you can initate reboots/restarts and not have the OC get mis-percieved as a bad OC.

 

[Krynj]

Awesome. Thank you very much.

So to make sure I follow you here:
1) Unplug PSU
2) Set the CMOS jumper to clear (and boot?)
3) Put CMOS jumper back to default.
4) Plug PSU back in.
5) Load BIOS defaults.
6) Set the OC, reboot.
7) And once in windows, shut all the way down, leaving PC to sit for a minute or two?

 

[Idontcare]

Originally posted by: FetusCakeMix
Awesome. Thank you very much.

So to make sure I follow you here:
1) Unplug PSU
2) Set the CMOS jumper to clear (leave like this for 30-60s, no booting yet)
3) Put CMOS jumper back to default.
4) Plug PSU back in.
5) Load BIOS defaults, F10 save, reboot.
6) Set the OC, (F10 save, reboot).
7) And once in windows, shut all the way down, leaving PC to sit for a minute or two?

Looks good, added a few comments in bold above.

Also at step 6 I always save my OC settings as a profile in the BIOS (the red screen, where you have 10 slots to save profiles).

I don't know if this makes the success rate of the BIOS retaining my overclock settings any higher than otherwise but my experience thus far with 5 DS3L mobos is I haven't had a lost OC issue since I started following this procedure.

 

[Krynj]

I'll give that a shot when I'm a little more sober than I am right now.

 

[Krynj]

Worked perfectly! Thank you.

 

[VirtualLarry]

Wow, so this is a confirmed fix for the problem of gigabyte mobos not holding their OC? Someone alert the mobo forum!

 

[Idontcare]

Originally posted by: FetusCakeMix
Worked perfectly! Thank you.

Happy to hear it!

Originally posted by: VirtualLarry
Wow, so this is a confirmed fix for the problem of gigabyte mobos not holding their OC? Someone alert the mobo forum!

I remember posting this in one of those laboriously lengthy DS3L threads back in Jan.

No doubt it was rapidly buried and long forgotten by Feb.

Definitely feel free to recycle the info to help anyone you come across or repost it in the mobo forums, I rarely visit there these days.

 

[BonzaiDuck]

Originally posted by: Idontcare

Originally posted by: FetusCakeMix
Awesome. Thank you very much.

So to make sure I follow you here:
1) Unplug PSU
2) Set the CMOS jumper to clear (leave like this for 30-60s, no booting yet)
3) Put CMOS jumper back to default.
4) Plug PSU back in.
5) Load BIOS defaults, F10 save, reboot.
6) Set the OC, (F10 save, reboot).
7) And once in windows, shut all the way down, leaving PC to sit for a minute or two?

Looks good, added a few comments in bold above.

Also at step 6 I always save my OC settings as a profile in the BIOS (the red screen, where you have 10 slots to save profiles).

I don't know if this makes the success rate of the BIOS retaining my overclock settings any higher than otherwise but my experience thus far with 5 DS3L mobos is I haven't had a lost OC issue since I started following this procedure.

Weren't the DS3* mobos including the P35 chipset?

My problem with a -UD3* board was likely due to the conditions you mention in an earlier post that causes BIOS to reset, but it may also have included causes such as: "BIOS version discontinuously lowers over-clocking potential of earlier processors," or "damaged E6600 CPU," but I seriously doubt that any damage had come to the E6600.

In my case, system would not POST, and would not therefore offer convenience to enter BIOS Setup. Sometimes, this occurred AFTER a patient and careful CLR_CMOS. But just removing parts from their sockets and replacing them had a good chance of clearing the problem and allowing BIOS Setup entry.

The fact was this: I had the system running fine with the E6600 2.4 @ (333*9; 5:6 with DDR @ 800 Mhz. There was something else going on -- involving power-management features and different processor model-lines (D, Conroe, Penryn, etc.) in conjunct with BIOS version.

But I have noticed the "unable to hold over-clock settings" problem with other Gigabyte boards. I'm sure of it.