I'm prime Orthos Stable for hours with 1.35v. The only other thing I changed in F6 bios is vdimm at + 0.1. Everything else is default after 'load optimized stttings'. Very easy MoBo + CPU combo to OC!Quote:
Originally Posted by wolfman140
Printable View
I'm prime Orthos Stable for hours with 1.35v. The only other thing I changed in F6 bios is vdimm at + 0.1. Everything else is default after 'load optimized stttings'. Very easy MoBo + CPU combo to OC!Quote:
Originally Posted by wolfman140
Either you must be super lucky or have a magic motherboard. So you said you are prime orthos stable...So you mean Dual Prime and Othros stable yes? I have since changed a lot of things on my mobo from the default because back in the day it was needed supposedly to OC. Maybe its not anymore and it messes things up. Maybe I'll give defaults a shot again later. But i doubt that'll solve my issue.
I haven't tried Orthos yet maybe I should. Some people have said that they are stable in Orthos but not dual prime. Others say they are stable in Dual Prime and not in Orthos. I'll have to get Orthos to check.
My E6400 is Orthos dual-thread stable at 3.2G with 1.35V but only on small FFTs and Gromacs. Large FFTs require 1.475V which is why I'm running at 3G with 1.35V instead.Quote:
Originally Posted by blurp
Quote:
Originally Posted by Dax5
Unfortunatly the default vdimm on the DS3 is 1.8v, and most DDR2 ram is now 2.0v stock. Therefor, not enough stock volts to boot. Look and see if you ram is default 2.0v, if so, you need to find a cheap stick so you can get into the BIOS and up the voltage.
thnx for the info looking into this mobo
Just to make sure I tried again Large in place FTTs. It's has been running fine for more than 6 hours so far. CoreTemp reaches 57-59 because I reduced my fans to have a quiet system.Quote:
Originally Posted by Fred_Pohl
Cool. I wish I had your CPU. Mine is great up to 3.1G but just doesn't want to do 3.2G without a lot of vcore.
Anyone here using the e6600 with the ds3?
YeahQuote:
Originally Posted by Dax5
Stuck at 333FSB @ 3Ghz. Tried lowering multiplier, tried changing to 2:1 memory ratio. Motherboard seems to FSB limited with my e6600. I bet if I popped a 6300 in, it would fire right up to 400FSB, like everyone elses.
It fails the Large TTF test like its a memory/NB problem once I get over 333. The higher above the faster it fails. I tried skipping and going straight for 400FSB with 1.5v at 9x, 8x, 7x & even 6x multipliers, wouldn't boot.
Some reason DS3 + 6600 = bad overclocks, unless you have a chip that does 3.6Ghz (9x400FSB). It seems you need a 975 motherboard to get a good OC :mad:
http://www.crowdcontrolusa.com/overclock/shizzy3.html
i disagree man! i came from a dfi 975x and it suckz big time! you should check out the 4ghz conroe club thread and see for yourself what people there are getting out of this board.Quote:
Some reason DS3 + 6600 = bad overclocks, unless you have a chip that does 3.6Ghz (9x400FSB). It seems you need a 975 motherboard to get a good OC
try this!
fsb 356
pcie 100
memory multiplier 2x
leave everything else to stock except for the ram timings
hit F10 and see what happens
Yeah, 3.2 GHz default Vcore Orthos stable. I can Post at 3.5-3.6 but my temps suck. Getting better cooling. BIOS F5.Quote:
Originally Posted by Dax5
E6600 running just fine at 390 x9. Fighting hard for 3.6 24/7 :)
All on TT BT. Seriously, i dont get it. I think my OC was easy as pie. More or less just popped everything in, dialed things in to my liking and started increasing FSB. Increased voltages when i met instability. Increased cooling on NB when th sink gave me burns.
What's the status on that little easy vdroop mod?
Is bios F5 still the best?
Seriousl, been away for a week and im completely lost in this :D
could you guys post your bios settings, so we can compare notes
thanks!
Conroe E6600, DS3, Team Xtreem pc5300 3-3-3 D9GMH.
Just from memory, still during testing, so not tightened in at all:
ram set at 4-4-4-8 (CPU-Z reads 4-4-4-9?)
PCI-e set at 100.
PCI-e voltage set at +.1v
VMCH set at +.1v (not sure this is necessary)
Vdimm set at +.4v.
vcore set at 1.575 iirc
Mem set at x2
As i said, it needs tinkering. Maybe i can up my memdivider. IDK, seems no one is hitting 1ghz+ on D9 with gigabyte though. My voltages may be too high on MCH and dimm.
I have surely forgotten some settings. I will return when i have done a reboot - or you could ask, i can prolly remeber what i set things at i i am asked :)
F6 is best. It helped me alot on oc'ing.Quote:
Originally Posted by SlackeR
Cool. I'll flash that one sometime. Any word on the extremely simple vdroop mod? the thread showed mixed results iirc..Quote:
Originally Posted by ClockCatcher
F6 is a piece of :banana::banana::banana::banana:. NO matter what I do now i can't even get in to windows with F6. WIth F5 I used to be able to set auto voltages and easily set 400fsb x 8 and things would work perfect. Now I can don't anything like that nor can I find a stable voltage anywhere. Better e6400 OC my ass.... What is gigabyte even doing?Quote:
Originally Posted by ClockCatcher
Well for me F6 is best Bios so far.Quote:
Originally Posted by HeadShotWI
User error maybe :rolleyes:
Quote:
Originally Posted by SlackeR
i have same problem with u, i set ram to 4-4-4-8, but cpuz read 4-4-4-9.
im currently using supertalent 2x1gb ddr800, which is using micron d9 to, n i hit a fsb wall at 450, i cant go higher than this no matter what i do, can someone tell me what i did wrong? or should i buy another memory that not using D9?
I'm running the same RAM (cutting and pasting your format and putting in my settings):Quote:
Originally Posted by SlackeR
ram set at 4-4-4-8 (CPU-Z reads 4-4-4-9?)
PCI-e set at 101.
PCI-e voltage set at AUTO
VMCH set at AUTO
Vdimm set at +.2v.
vcore set at 1.325 (stock)
Mem set at x2
I'm running a Scythe Infinity and get some brutal CPU temps mounted in a Gigabyte Aurora case. I'm swapping out the stock fans with some Yate Loons and throwing in a SI-128 w/ a Silverstone 120mm fan. The caps around the socket are EXTREMELY hot. I'm hoping the SI-128 will blow some fresh air onto them. Parts won't be here for a while, so I'm running default vcore. I have a Thermaltake Spirit II cooler on the NB.
The board has been great for me so far, but its just a standby until I see the RD600. Then I'm picking up the Abit or RD600. I think the DS3 seriously needs some cooling on the mosfets/caps around the socket.
Unfortunately I can't go with noisy fans (PC is in room beside master bedroom and the wife would complain) or water (cat and 4 month old son - and I'm lazy).
Quote:
Originally Posted by HeadShotWI
Why does everyone insist on calling a product complete crap because it doesn't work for THEM?
My DS3 (F6) and E63 does 3.01ghz with only +.2vdimm and +.1vmch, everything else is untouched.
6hr's dual Orthos stable.
Wow, I really need help here. Here's the problem:
This board seems to really hate my X-Fi, or maybe just the BIOS. Sometimes after screwing with settings in BIOS, or on a cold boot, it doesn't detect my X-Fi and I have to repair its drivers from the CD to get it to work again. One thing to note is I forgot to clear CMOS after flashing from F3 to F6, so could that be causing it? I really would be appreciative of a solution here.
Secondly, on a cold boot, the thing emits one long beep throughout most of POST, then a couple shorter beeps, but Windows loads fine and the system is dual Prime and dual Orthos stable (8 hours).
Is the thing with the X-Fi just a noted issue, or what?
Thanks a lot, guys.
Lil problem here.
I am able to o/c to this:
http://img158.imageshack.us/img158/8369/1srtfg0.jpg
But after that i cant raise FSB...
1st i thought it was my memory (DDR2-667) but then i raised the mem divider to 4:5 and i was able to do that (timings are AUTO):
http://img72.imageshack.us/img72/8905/mnimesxe4.jpg
I have to say i didnt try to do more. Maybe ram can do better...i ll try later. But that is not the case.
All voltages are in NORMAL mode. Tried to raise manually Vdimm by 0.4 but i got a FAILED msg in bios.
Why PC cant hold more FSB than 430 in 1:1???Am i missing something here?
Meh, EasyTune is a joke, pretty much. Do your overclocking the old fashioned way, through BIOS, and see if that doesn't change anything.
F6 bios should have some kind of X-FI fix.Quote:
Originally Posted by Omastar
I just realized i have not disabled the protect nx-bit or sth in avacned chipset. Is that beneficial?
I just had a hard reboot. Really dont get that one, i can orthos or prime for hours, seems to be a random error..