Confused Noob at 11:00

Associate
Joined
6 Aug 2006
Posts
35
Hey all just started overclocking (first time) largely following jokesters guide (my rigs e6300, DS3 mobo and geil 800mhz ram). The first 25 FSB increase (going up in 5s) all went swimmingly, had to increase the cpu voltage one notch to keep stability but otherwise fine. This all stopped however when i went to 296 fsb (defaults 266) at that frequencie my computer keeps restarting and the bios resseting to default values (im running the f4e version as suggetsed). Now as you may have guessed im a noob at this so other than increasing the cpu voltage (which didnt work) im not sure how to tackle this issue. I havent done anything to the ram so dont know if i should be doing something with that (I've heard various things about ram frequencies and dividers but i really dont understand that side of things).

If anyone could point out my error (its probably pritty blatant to anyone whose done some serious overclocking) i would be highly appreceative.
 
Try increasing the FSB voltage (chipset voltage) a notch until its all stable. Should be ok. Otherwise you may need to update the BIOS to one of the new gigabyte beta versions, they're meant to be better for overclocking.
 
I would take a guess at a RAM divider, I find it very unusual that you would need to up yor vcore after just 25fsb extra.

What psu are you using?
 
Im presuming the fsb voltage is the same as the cpu voltage yes? if so ive already tried rising that a fair bit and i dont see why it would require a massive jump for only 5 fsb.

As for psu im running a 500w enermax liberty so a pritty good one.
 
Vispon said:
Im presuming the fsb voltage is the same as the cpu voltage yes? if so ive already tried rising that a fair bit and i dont see why it would require a massive jump for only 5 fsb.

As for psu im running a 500w enermax liberty so a pritty good one.

Could be.

• FSB/Memory Clock Ratio
• Memory timings too tight
• North Bridge Voltage too low
• FSB Voltage too low
• Or a few of the chipset settings enabled when they shouldn't be

I've managed 400Mhz FSB on my E6300 so you should get past a 25Mhz increase.
 
Tbh I'd start again from the beginning and try to establish the 'ceiling' overclock for each component in your system.

Lets break this down a bit. Your CPU can be overclocked by increasing the FSB, and if this causes instability then you may be able to rectify that by increasing the CPU voltage. Your FSB can also be increased, and if this causes instability then you may be able to rectify this by increasing the chipset voltage. Also, your RAM can be overclocked by increasing the FSB, and if this causes instability then you may be able to rectify this by increasing the RAM voltage.

Can you spot the link in the above?

They all involve increasing the FSB, so how are you supposed to know what caused the instability?

Well, the simple answer is you can't. Unless you take measures to eliminate the other components from causing the instability. This is where the multipliers come in :)

Dividers are just ways of increasing/decreasing the speed of components relative to others, and independently of the FSB. If you decrease the CPU/FSB multiplier, you can eliminate this from being the component that is causing the instability. If you decrease the RAM/FSB multiplier, you can eliminate the RAM from being the component that is causing the instability. If it's still unstable after decreasing these multipliers, then it's likely that the mobo is causing the instability, and voltage can be added to the chipset to try to increase the overclock.

Try this:

1) Set your RAM/FSB multi to around half of what it should be (i.e. 1:2 ratio instead of 1:1);
2) Set your CPU/FSB multi to around half of what it should be (i.e. 3x or 4x, instead of the usual 7x)
3) Try increasing your FSB in 5 or 10 Mhz increments and stability test between. If you experience instability, increase the chipset/NB voltage and try again. If it's stable, continue to increase the FSB. Keep doing this until you find a stable ceiling. Keep a log of all the FSB's and voltages and whether it was stable or not.
4) You now know what the max FSB is that your mobo can handle. Put the FSB back to stock, set the CPU multiplier back to 7x and start overclocking again. This time, keep your chipset/NB voltage inline with the notes you made for the frequency it's running at, and increase the CPU voltage if you get instability. Keep doing this, increasing in 5 or 10Mhz increments until you find the stable ceiling for the CPU. Keep a log!
5) Set the CPU multi back down to 3x or 4x. Set the RAM multi back to 1:1. Start increasing the FSB, chipset/NB voltages once again in line with the log you made, and increase in 5 or 10Mhz increments until you find the stable ceiling for the RAM.
6) You should now have the max stable overclocks for each individual component, so now you need to try to work all of them together by calculating the frequencies and dividers to try to get the best compromise for them all. Prioritise on the CPU speed first.

I hope that helps :) And btw, I'm an Athlon64 overclocker so if I've made some fundamental mistakes in the nature of overclocking Core2Duo's then please somebody feel free to correct me :)
 
Have you turned all the speedstep stuff off in the bios?

It goes under the name of 'EIST'. I had the same problems as you when it was turned on.
 
Back
Top Bottom