Hello
I recently decided to overclock my CPU. I have a Q6600 G0 quad core CPU. On a Gigabyte EP35-DS3R rev 2.1. I have managed to overclock the CPU by raising the FSB to 315 (1260MHz). For cooling i have a Zalman CNPS9700 fan. Seems no matter what i do i can’t get the machine to boot if i raise the FSb over 315. I had hoped to get my cpu up to the 3.0 Ghz mark. While the 2.84 Ghz i am at now is not something to be ashamed of i would still like to try for that 3.0 Ghz mark. Any sugestions? Gigabyte’s BIOS for Overclocking is a mess, and doesn’t use conventional nomenclature so if you have any sugestions please don’t skip steps.
Nick
------------------------------Robert Wilensky:
We've all heard that a million monkeys banging on a million typewriters will eventually reproduce the entire works of Shakespeare. Now, thanks to the Internet, we know this is not true.
Reply to HoustonSerenity
don't give up. It took me a few hours fiddling with gigabyte bios to get there and I have the exact same mobo and processor as you.
I would keep all the ram stuff on auto and just mess with the cpu multiplier, FSB, and cpu core voltage.
I have mine at 9x334 running at 3.0ghz. I had to raise my voltage a bit to 1.38. I know some people can do it on stock voltage but I couldn't. Every cpu is different i guess. And you have to keep vdroop in mind too. 1.38 in bios is actually like 1.34 in windows and even dips down to 1.29 during load. I hope that makes sense. But try upping voltage a bit more.
This should work, no problem. See if you missed something.
1. In Advanced BIOS Features Temporarily set C1E and EIST to Disable. After you see the OC you can enable C1E again.
2. In MIT set the PCIe to 100.
3. ensure CIA is disabled and Performance Enhance is set to standard.
4. In MIT set CPU Host Frequency (Mhz) to 333.
5. in MIT set Memory Frequency (Mhz) to 2. You didn't post your RAM so this will give you a 1:1 667Mhz.
6. In MIT set DDR2 OverVoltage Control to the RAM spec. The base is 1.8V so +.1 = 1.9V and +.4 = 2.2V etc.
Leave all other settings on auto and boot.
Done.
You can look at Normal CPU Vcore in MIT or run Core Temp with EIST disabled, to see your VID. You can lower the Vcore, also in MIT, by small increments and use the lowest stable Vcore to reduce heat, although with C1E enabled you are probably better to keep it on auto.
------------------------------The Pastafarian belief of heaven stresses that it contains beer volcanoes and a stripper factory. Hell is oddly similar, except that the beer is stale, and the strippers have VD
Reply to rubix_1011
Drop your multiplier to 8x and bump up FSB with that.
8x 500 = 4.0ghz.
1.2250 VID 1.375 vCPU 2.0v RAM 5-5-5-15 2T DDR2-1066
I would get 8x 400 = 3.2 working, before trying for 8x 500 = 4.0ghz.
Depending on if you were lucky with a low VID (below 1.325), you may be hard pressed to get over 3.6 on Air. Especially if you are new to this.
Since it sounds like you are having issues with your RAM, perhaps try 6x 400 = 2.4 and make sure your RAM and FSB are good at 400 (1600QDR).
Then bump it to 7x 400 = 2.8 and test.
Then bump it to 8x 400 = 3.2 and test.
Then bump it to 9x 400 = 3.6 and test.
You will probably have to start increasing your CPU Voltage once you go past 2.8. You should be able to get to 3.2 relatively easily and that is a 33% OC. Not too shabby. Do not go over 1.5 CPU Voltage or 65+ C
Or if you have 333 FSB working bump it to 9x 333 = 3.0.
You should only need a nominal CPU Voltage increase for 9x333=3.0. Probably 1.35 - 1.375 depending on the VID of your CPU.
Message edited by gmanvbva on 07-09-2008 at 06:49:18 PM
I've increassed the CPU valtage to 1.38 and moved the Ram ratio to 2, i dont know if this is good for 4 gigs of 800 mhz ram, and I uped the FSB to 334 and i took the restriction off the CPU fan so now it runs like it was ment to. I have it running at 3.01 GHz, and as far as i can tell it is stable i have had no issues with it and it's been like this for about a week.
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.