ds3 ocing guide

Associate
Joined
1 Jul 2006
Posts
109
I know this sounds stupid, but seeing the prevelance of ocing help request for the ds3 with conroe I was wondering if those who manage to oc *** ds3 to *** max is willing to write a guide on how to oc the conroe. I mean The Asgard has a thread up regarding ocing but its a bit disjointed. Could he be persuaded to write up a formal guide on waht to do, what to disable and how to test the setup..


many thanks
 
Dont like to pester board members but a fresh, more specific guide (ie core2duo absed) would be sooo usefull. I had a look at Pcformat magazine this month as they had a section on overclocking and it was really quite useless and generalised.
 
I have seen that one and sorry to say.. its a bit disjointed. Its good for asnwering specific questions and queries but what I am requesting for is something more general..

I mean for ex: how do one start the ocing process? start doing a 50mhz jump or go straight to 400... or perhaps inch along at around 10-15 a time..

or would it be better to use easy tune to do a oc, then use that result to change the setting in bios..

just an example..

ps: how come t h e is blotted out ?
 
well, as someone who did a lot of it themselves.

first things first, ensure that A. you have good ram, and B. update the bios. The F1 is pants, the F4e is a helluva lot better.

a good early thing to try for is 300 fsb, then work up from there. Mine is now sitting quite happily at 429FSB, and 3GHz is plenty for now, 43C idle and 53C load.

hmm, voltage wise, see what they have done for the board itself, and getting the ram up to 2.1V is a good idea as well. My ram is at 4-4-4-12, I could try tightening the timings, but I might leave it at this for now, it seems stable enough, and its definitely a lot quicker than the socket A system I came from.

Do all overclocking in bios, the only motherboard utility I installed apart from the drivers was the @BIOS. I managed to flash my bios fine through that. Easytune is not worth it.

Thats the basics. Using orthos/SP2004 to check stability, easier than having to run multiple instances of prime, as these programs natively support dual core/multiple instances.

Can't think of much else apart from that.

Good luck to you.
 
What I've been wondering is when people say 'inch up' from whatver fsb what does that require. I mean do u inch it up by 10mhz a time and see if windows loads? Or do you inch it up 10mhz a time and then run prime for 2 hours? Just asking since if its the second it would seem a very long process.
 
Where do u get the F4e bios from?

I have managed to get to 400fbs and is fully stable, tried getting to 3.0ghz but couldnt get it stable :(
 
fan_83 said:
I have seen that one and sorry to say.. its a bit disjointed. Its good for asnwering specific questions and queries but what I am requesting for is something more general..

I mean for ex: how do one start the ocing process? start doing a 50mhz jump or go straight to 400... or perhaps inch along at around 10-15 a time..

or would it be better to use easy tune to do a oc, then use that result to change the setting in bios..

just an example..

ps: how come t h e is blotted out ?

Ask in there then. Problem is that we will have millions of threads about the same thing. Just makes it harder for everyone then.
 
socaaddict: assuming that someone has a 6300 and plans to overclock to 3.5ghz like asgard did.. it would take 47 steps at 5mhz increments and it would take 8 hours to get there... and thats not including the time it takes to adjust the setttings.

isn;t that a little too long
 
I think asgard did his overclock over a week long period, so no, its not too long. considering I got mine up to 3.1GHz over two days, a week to go up to 3.5GHz is plenty enough. I mean, early on, like me, you can do bigger steps (think I went straight to 300FSB, tested that for a bit, 325, 250, 375, 400). Only once I was up to 400 FSB did I start doing the much smaller increments.
 
Back
Top Bottom