I've got a GA-P35-DS3R, 4 GB of OCZ platinum and an e4500.
I've been running it at 3157 ghz and 3003 mhz for about a year now fully stable, but I've always had cold boot issues when running the mobo above 266 mhz FSB. I give 1.39375 V to the CPU and an extra .2 V to the ram (OCZ needs lots of voltage and im well within safety limits) and +.1 V to the MCH due to the fact that I'm using 4 dimms.
Lately what has been happening (perhaps since I went to the latest BIOS) is that the overclock is in the BIOS but what I get in Windows (vista, if it matters) is the ram timings are tightened, the ram divider I selected in the BIOS is used, the voltages are increased but there is no change to the FSB. It still runs at 200 mhz (stock for the e4500).
Any ideas on how to fix this? Reseting the CMOS then re-applying the overclock usually works but its a bit of a pain to have to keep doing it.
Does it do the double-post before it goes into Windows? That resets the OC settings back to defaults. My GA-P35-DS3R does that on cold boots too, I have to re-do the CMOS settings slightly and then soft-reboot into Windows.
I live with it because I don't boot very often, I just leave my machine running.
__________________
Quote:
Originally Posted by Rubycon
I like to think of knowledge of being the best wealth one can build up. Unlike $ nobody can take it from you when you have acquired it.
I have the same motherboard, and I got the issue a few weeks ago. I believe the only way to fix it is to remove the CMOS battery, let it reset, then put it back in. I tried resetting the BIOS, upgrading the BIOS, and no dice for anything but removing the battery.
__________________ Opportunities for abuse are what keep us going!
AnandTech Immoderator
Love is a sensation, caused by a temptation, to feel penetration. A guy sticks his location in a girl's destination, to increase the population for the next generation. Did you get my explanation, or do you need a demonstration?
Originally posted by: VirtualLarry
Does it do the double-post before it goes into Windows? That resets the OC settings back to defaults. My GA-P35-DS3R does that on cold boots too, I have to re-do the CMOS settings slightly and then soft-reboot into Windows.
I live with it because I don't boot very often, I just leave my machine running.
When I cold boot it yes, it does the double restart.
But this new problem is weird, the OC does stick in the BIOS, the CPU "runs" at 3 ghz in the BIOS but in windows CPU-Z has the fsb only at 200 but all my other tweaks are OK.
I just checked my overclock and it appears that my BIOS has, once again, reset my CPU overclock. But none of the other settings are changed. If I get a new mobo battery will that change things? I mean... if the battery were flaking out (and it's only been one year) my other settings would be dying too, right?
__________________ Opportunities for abuse are what keep us going!
AnandTech Immoderator
Love is a sensation, caused by a temptation, to feel penetration. A guy sticks his location in a girl's destination, to increase the population for the next generation. Did you get my explanation, or do you need a demonstration?
Bumping this old thread to see if anyone has solutions. It's happened twice since my last post in this thread (so two times in a month). I'll try finding a new battery until then but could it really be the battery? The motherboard's not even 18 months old yet. Are these motherboards just defective or something?
__________________ Opportunities for abuse are what keep us going!
AnandTech Immoderator
Love is a sensation, caused by a temptation, to feel penetration. A guy sticks his location in a girl's destination, to increase the population for the next generation. Did you get my explanation, or do you need a demonstration?
I had this problem, seems common, I solved by loading defaults, saving and rebooting, and then re-applying the overclock.
The lost overclock when going to Windows seems to start happening after I've shut off the PSU, and maybe more likely if I've unplugged it from the wall (although this could simply be because I'm working on it for longer).
Weird thing is Linux kept the overclock, Vista/XP did not have it.
__________________
************************HOW TO NESTED QUOTE:************************
Install this into Firefox. Then click this, then click "quote" as usual, then click "Nested Quote" to the right of the title bar.
3.5Ghz&2.6Ghz-CPU-NB 720BE x3->x4 || GA790X-UD4P 8GB DDR800 || 9800GT 725/1750/2000 || Soyo 24" PMVA Heatware
Originally posted by: soccerballtux
I had this problem, seems common, I solved by loading defaults, saving and rebooting, and then re-applying the overclock.
The lost overclock when going to Windows seems to start happening after I've shut off the PSU, and maybe more likely if I've unplugged it from the wall (although this could simply be because I'm working on it for longer).
Weird thing is Linux kept the overclock, Vista/XP did not have it.
Ya, booting into Ubuntu sometimes fixed it for me too.
And I have profiles for stock / overclock...when an oc doesn't stick I load stock settings, go back and its usually fine too.
I've had this same problem with GA-P35 boards. If you unplug or turn off the psu the motherboard resets the overclocks but keeps the rest of the settings. What really sucks is that there isn't any overclock software available that will OC the fsb on startup/ Can you believe that? Somebody needs to get on the ball and fill this void. I experimented with clockgen in Vista X64 using an unsupported PLL for my MB but it wouldn't set the clock speeds upon startup. Oh and gigabytes overclock utility doesn't OC on boot either.
You know aside from this one issue the GA-P35 is a ROCKING board at a killer price. Have my E2200 easily OC'ed to 3ghz wihtout a hiccup. Not bad for a $60 board that supports Quad/extreme core.
P.S. It's not the battery.
__________________
Quote:
--
“For the scientist who has lived by his faith in the power of reason, the story ends like a bad dream. He has scaled the mountains of ignorance; he is about to conquer the highest peak; as he pulls himself over the final rock he is greeted by a band of theologians who have been there for centuries.”
-Robert Jastrow: Founding director of NASA's Goddard Institute for Space Studies commenting on the second law of thermodynamics and the creation of the universe.
Originally posted by: Perry404
I've had this same problem with GA-P35 boards. If you unplug or turn off the psu the motherboard resets the overclocks but keeps the rest of the settings. What really sucks is that there isn't any overclock software available that will OC the fsb on startup/ Can you believe that? Somebody needs to get on the ball and fill this void. I experimented with clockgen in Vista X64 using an unsupported PLL for my MB but it wouldn't set the clock speeds upon startup. Oh and gigabytes overclock utility doesn't OC on boot either.
You know aside from this one issue the GA-P35 is a ROCKING board at a killer price. Have my E2200 easily OC'ed to 3ghz wihtout a hiccup. Not bad for a $60 board that supports Quad/extreme core.
P.S. It's not the battery.
Yeah, I didn't think it was the battery, but considering removing it for an extended period of time was the ONLY way (at least, the only one I discovered) to get my overclock back, it seems a valid culprit...
But I mean, it doesn't appear to be the motherboard itself that's losing the overclock - my CPU still shows clocked at 400 FSB in the BIOS. It's only when I boot into Windows and check with a utility like Everest do I discover that my CPU FSB is really only 266.
Now, looking at this problem again, it seems that there could be a few problems happening:
1) Windows stops the CPU from overclocking -- very unlikely; and why now? Why just Gigabyte motherboards?
2) The real CPU speed isn't being reported to Windows correctly -- possible, because I don't really notice a difference in speed... but seems kind of strange. Also, Speedstep multiplier changes are affecting the total CPU speed as normal too (speedstep also worked correctly when I had my overclock). It *could* be an FSB reporting problem...
3) Gigabyte applies the overclock in BIOS, POST, everything - except when the computer boots into Windows, the overclock essentially disappears and reverts back to stock settings. I don't know why this would happen, but it could be a glitch with the chipset or something - while I have a GA-P35-DS3R, other people have been reporting the exact same problem with other Gigabyte boards (DS3Ls are the only ones I can recall ATM).
Considering this problem has been reported on other Gigabyte motherboards (though not commonly - it's very difficult to find a forum post regarding this issue), I'm led to believe that the problem is #3, but #2 deserves a good looking at... maybe when I have some free time I'll do some hard number testing and see if I get anywhere.
__________________ Opportunities for abuse are what keep us going!
AnandTech Immoderator
Love is a sensation, caused by a temptation, to feel penetration. A guy sticks his location in a girl's destination, to increase the population for the next generation. Did you get my explanation, or do you need a demonstration?
Originally posted by: Rhonda the Sly
Using the CLR_CMOS pins works just as well as removing the battery, just so you guys know. A lot easier than digging into the case, if you ask me.
Yep, I use a screwdriver in between the pins for 10-15 seconds to reset the CMOS.
Originally posted by: BlueAcolyte
Here's the solution. It seems to be a problem specifically with Gigabyte boards and unclean shutdowns (IE press the power button).
Wow, thanks a bunch to you for bringing this up and IDontCare for figuring it out!
I'll try this out and let everyone know how it works...I restart often switching from Vista to Ubuntu and back so the frequent loss of overclocks sure got annoying.
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.
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.
Wow, Nice work IDC!
Even that didn't work for me, it still would sometimes disappear in windows.
Until I recently switched to an NVDA vid card.....for some reason the overclock's have been staying on every restart now.
For the others with this problem, did you have an ATI or NVDA GPU?
Overclock in BIOS but not Windows
