Gigabyte DS3 problem

Associate
Joined
29 Sep 2006
Posts
1,237
Location
Liverpool
Well ive had my DS3 mobo for a few weeks now, and apart from one or two things its brilliant.

Well the main problem is..when i overclock (FSB @ 430) when i restart the system, it disables the overclock on its own! So each tiome i turn my pc on i have to boot into the bios every time, and just enable the overclock. the fsb stays the same, but the option for the OC is set to disabled on its own.

Can anyone shed any light as to why its doing this? It nearly always POSTs, but sometimes i dont get a beep, and the screen says no signal..but i have read that eople have set their pcie freq. to 101 or 105 and it has sorted that issue.

This isnt a majour problem, just very annoying when i forget to do it and wonder why my games lag very bad!

Is this a common fault? I think the board is Rev3.3 (if anyone could tell me how to find out id be glad to if it helps) and its on F10 bios.

Thanks in advance
 
It just sounds like it's not a stable overclock. The DS3 resets a bad overclock itself to save you having to clear the CMOS.

A tad more vcore would probably solve it.

And are you giving the Ballistix 2.2v?
 
Nah. You're better managing them yourself.


On the Ds3 the Memory voltage needs to be set to +4 to get 2.2v. I would also give the FSB and MCH voltages a nudge to +1.

As for the vcore, anything upto 1.45v should be fine for the e6300, tho you'll need to watch your temps.

Are the RAM timings still on auto too (you'll have to hit Ctrl and F1 together on the main BIOS screen to unlock them).
 
ram timings are at 5-5-5-20... if i have them lower i dont get a post (on off on off problem.. same happens if i have the ram freq over 1ghz.. so i have the multi at 2.

Right, ill go fiddle with the volts and see if i get any improvements
 
The Ballistix should do 4-4-4-12 @2.2v upto ~1000mhz.

After that you can either give it a tad more juice or loosen the timings to 5-5-5-15 or so.
 
Well i messed with the volts and had a few problems..

Firstly i tried what you said, knocked up the volts on ddr2 to 2.2, FSB and MCH +.1 and i had vcore at 1.35 - Failed to overclock, did the same, just disabled it

So i tried vcore at 1.37, same problem

Now, im at 1.1 (says cpu-z) and ddr2 @ 2.2. couldnt have the ballistix over 1000mhz, it just doesnt like it for some reason :(

but its on, and overclocked.. so i think ill just leave things how they are and see how it goes.. Thanks for all the help Cob
 
Back
Top Bottom