Gigabyte GA-P35-DS3L Thread

[t3plexxx]

totally new to overclocking. got this board and a g6600 g0 stepping. and the tuniq tower cpu fan. ive tried overclocking it and everytime i boot it just boots (not yet in the logo) then turns off
then boots
then turns off
thenboots to logo no but unsuccessful overclocking cause its still 2.40 ghz and the settings in bios is back to disabled instead of manual. can anyone help me out?

[Rpg2]

Originally Posted by Thanatos8

Not sure quite what I was doing wrong before, but did a lot of reading so I really understood what was doing what. Currently have it o/ced to 2.8 Ghz, running at 30C idle, 50 degrees average running Prime 95 tests. Tommorow I'm going to shoot for 3.2, and won't likely push it over that, since I run my machine for days in a row, and 3.4-3.6 may produce too much heat. Anyone had experience running at higher then 3.2 for multiple days? Maybe use speed stepping so it declocks itself while it idles at night?

My friend told me that the E2180 goes up to about 3 to 3.2Ghz which is quite fast for that chip. I'm not sure if you could push it further, but if the temps and voltage permits then by all means go ahead.

Running a heavily OCed chip for 24/7 cuts it's lifespan from what I've read.

[claytona]

Originally Posted by t3plexxx

totally new to overclocking. got this board and a g6600 g0 stepping. and the tuniq tower cpu fan. ive tried overclocking it and everytime i boot it just boots (not yet in the logo) then turns off
then boots
then turns off
thenboots to logo no but unsuccessful overclocking cause its still 2.40 ghz and the settings in bios is back to disabled instead of manual. can anyone help me out?

sounds like you may be a little over the top with your speed or not running enough voltage. make sure to lock in pcie freq, set performance mode to std and make sure memory divider is at 1:1 (2.0 setting). default settings can take you way over the top if you don't set it all to manual.

[claytona]

Originally Posted by Thanatos8

Not sure quite what I was doing wrong before, but did a lot of reading so I really understood what was doing what. Currently have it o/ced to 2.8 Ghz, running at 30C idle, 50 degrees average running Prime 95 tests. Tommorow I'm going to shoot for 3.2, and won't likely push it over that, since I run my machine for days in a row, and 3.4-3.6 may produce too much heat. Anyone had experience running at higher then 3.2 for multiple days? Maybe use speed stepping so it declocks itself while it idles at night?

That seems like a lot for that cpu, but then again... see what others have done to get an idea but since cpus are individual you may not get that much, you may get more. If you push it hard you'll need a lot of Vcore. I haven't had any trouble with the speed step so I guess it could save you some life during idle. I'd look up "trace ablation" at tom's hardware and anandtech sites to see how hard you may really want to push it. You can always use prime95 with hwmonitor to check temps at full load to see where your heat stands. Nothing I'm doing really requires super big #s so I've been very happy in the 3.2G range, beats the @#$% out of 1.8G. But I bet 3.4-3.6 would be very cool. If yours runs cool at that speed without crazy Vcore it could be sweet for a long time. If you have to beat it to death with voltage to get it stable maybe life won't be so long.

[Thanatos8]

Well I'm reached 3.0 ghz on all stock voltages and testing fine, but now I'm hitting a wall. 3.2 ghz I just had to up the vcore a little to get it to POST, temps were fine but encountered IMMEDIATE error on Prime95, upped the FSBV and NBV +.1, immediate error, both to +.2, still immediate error. Any suggestions?

[smokinbonz]

Originally Posted by Thanatos8

Well I'm reached 3.0 ghz on all stock voltages and testing fine, but now I'm hitting a wall. 3.2 ghz I just had to up the vcore a little to get it to POST, temps were fine but encountered IMMEDIATE error on Prime95, upped the FSBV and NBV +.1, immediate error, both to +.2, still immediate error. Any suggestions?

Yeah push your vcore to like 1.4 and give it a try, i did the same thing ran stock voltage to 3 ghz then was amazed by how much juice i needed to get to 3.2 and stable, then my ram died and corrupted everything so that was a fiasco. But im pretty sure this will work for you

[Kip69]

odd question time: Will this card run an ATI x2 card? Such as the very tempting 4850X2 something something

I know no 2 cards in Xfire, but will 1 dual GPU card work?

[Victorious25]

So as it turns out I have the EP35-DS3L, not the P35-DS3L, and that's where all my problems were coming from. If anyone else made this mistake and is having issues with OCing, it's because the Vcore won't stick from the BIOS, and you need to download the beta BIOS for the board. If you search for it, there's a thread with links and more information.
On a side note: Since there's no thread for the EP35, is it cool if I just post what I get my OC to in this thread?

[claytona]

Originally Posted by Victorious25

So as it turns out I have the EP35-DS3L, not the P35-DS3L, and that's where all my problems were coming from. If anyone else made this mistake and is having issues with OCing, it's because the Vcore won't stick from the BIOS, and you need to download the beta BIOS for the board. If you search for it, there's a thread with links and more information.
On a side note: Since there's no thread for the EP35, is it cool if I just post what I get my OC to in this thread?

I can't speak for everyone but there's posts about ds3r's and about everything else here. I don't know what any problem would be.

I guess we just trudge along, it is getting hard to find anything tho...

[claytona]

Originally Posted by Thanatos8

Well I'm reached 3.0 ghz on all stock voltages and testing fine, but now I'm hitting a wall. 3.2 ghz I just had to up the vcore a little to get it to POST, temps were fine but encountered IMMEDIATE error on Prime95, upped the FSBV and NBV +.1, immediate error, both to +.2, still immediate error. Any suggestions?

my thought go with smokinbonz on this. I don't think you'll really have trouble 'till you get over 1.45. Keep an eye on temps and don't forget about the nasty Vdroop this board has. You can crank Vcore WAY up only to find you're still undervolt in cpuz. I didn't see how you are monitoring Vcore, the bios is very misleading, cpuz will tell the story.