Well, that's not too bad for 7900GT. Should work just fine. :D
Printable View
Well, that's not too bad for 7900GT. Should work just fine. :D
The board's in the mail along with a Swiftech MCX159-CU for the northbridge, I was just wondering if the mosfet heatsink should also be replaced, and if so, what were everyone's suggestions?
fan in back of case should provide adequate airflow for mosfet heatsink, even while watercooled. If running excessive voltage, a fan may be required, but highly unlikely.
I am currently Orthos stable with 400X9 at 1.37v Vcore and 1.48v on NB. I can't seem to get it Orthos stable past this, 416 x 9 is my max boot into windows with these settings and anything over that will not load windows.
Do you guys think I need to bump the Vcore to 1.45-1.5v and bump the NB to 1.56v? I am looking for around 3.8 24/7 use.
Memory is running great at 505mhz 4-4-4-16 1T, Async off course.
Maybe a bit higher vcore, and wait with n-b because 1.50v @ n-b~ 450fsbQuote:
Originally Posted by metalman2785
u know if its get's unstable:)
we have been told by Tony per DFI over 1.5v on NB will shorten its life and is not recommended for 24/7 useQuote:
Originally Posted by metalman2785
Thanks..I have D9GMH...its crucial 10th anniv ramQuote:
Originally Posted by pcmoddingmy
Guys I am real curious what you have found with voltage on the mobo
I set 1.42v for NB...bios reads 1.44
I am afraid to go 1.48 as this may lead to over 1.5v
I have used various changes to " various NB sub-settings"..but I still what increases will produce shorten life
I have to say 1.5v NB max for 24.7 seems poor if max fsb is 450 or so with this...how can they call it an overclockers board
anyone have 12/7 beta bios..I hear this was better for overclocking...had raid and usb issues though
I get 450 @ 1.4v. FSB limit sounds cpu-related...and not that cpu is limited, but GTL needs to be tweaked, IMHO.
With 1.53 i go up to 464MHz so no problem with limit. My bios read 1.5 for 1.53.
I think I will try leaving the NB at 1.48v and pump some more volts into cpu. CPU is watercooled, and NB has 2 fans actively cooling it. During Orthos CPU loads at 45C and NB is loading at 60C (54C idle). Does that NB temp sound too high for 24/7 use?Quote:
Originally Posted by Ten
hmm..what are your tweak settings...Quote:
Originally Posted by cadaveca
I am still at 48/48/128
e6600@ 3420 (9x 380)
BTW I can lower multiplier to 8 and still I am fsb limited...my cpu seems to max at 3500 at 1.518-1.525v
8x 425 crashes with NB at 1.42v....may need to tweak everything a bit more...so many options hard to know which one to tweak first
damn nice crucial sticks....505 with 4-4-4-16....I cant get 500 5-5-5-18 stableQuote:
Originally Posted by metalman2785
BTW fsb issue I bet is 2T...the shipping bios does not like 1T even async..I bet if you go to 2T you will get a higher fsb
what vdimm are you using to get 505 1T...wow
can you post all your mobo voltages and settings...I would love to see what you got
You have a very nice cpu and I bet 1.5v will likely get 3800(is the 1.37 a bios setting or reading from win software??)
TY, I am very pleased with my cpu/mobo and ram at this time. I am at work right now, but I will post all of my settings when I get home, about 5:30pm eastern.Quote:
Originally Posted by nealh
Vdimm had to be bumped to 2.3v to get orthos stable at 505, 4-4-4-16 1t, but I still feel 2.3v is safe for 24/7 use.
I haven't tried any oc'ing with 2T command rate, so that could possible help with my FSB wall. 1.37v is Bios setting, CPU-Z reads it as 1.35v.
I am pretty sure you will do better at 2T..supposedly this bios was set for 2T more than 1T and takes higher voltagesQuote:
Originally Posted by metalman2785
I am only running 2.2v ....afraid to kill my ram
Quote:
Originally Posted by metalman2785
very nice memory you got there.. :) a 505, 4 4 4 4 16 @ 1T :)
@ another observation on this board.. I cant trust the cmos reload option.. i usaully use the cmos reload when I failed an oc.. but recently.. I have tested the same setting and I have been stable with that settings(orthos stable).. but when I use the cmos reload and try to run orthos.. my tested settings fail..
If there are DFI people here please test the cmos reload options again.. :) tnxs
Settings for E6600, ORTHOS stable @ 3.6
CPU Freq - 401
CPU VID - 1.36875
CPU Special - 100.01%
CPU VTT - 1.36
NB Core - 1.36
NB PLL (1.8) - 1.93
NB PLL (1.2) - 1.38
NB PCI-E - 1.34
NB 1.2V convert from - 2.06
SB - 1.34
Crucial Anniversary @ 505 mhz
DDR2v - 2.3
Command - 1T
Timings - 4-4-4-4-18-24-42-3-6-3-2-3-2-2-5
I am gonna use 2T command rate and try some more oc'in :clap:
Quik test with water, 550FSB
http://img377.imageshack.us/img377/2527/550td3.jpg
Even more maybe can get, but not tested..yet.. :rolleyes:
Settings are same as my above post except 1.45 vcore in Bios.
410x9 passed an hour Orthos, but 411x9 fails Orthos in first 15 mins :(
http://img175.imageshack.us/img175/148/dualpi2rr1.jpg
its the 1TQuote:
Originally Posted by metalman2785
very nice OC.. and your mems i really like.. :)Quote:
Originally Posted by metalman2785
mm.. i think you can't rule out the 1T yet..Quote:
Originally Posted by nealh
do a memtest86 first in your settings and in 1t.. if it passed then its not the 1T..
here is my result using 1T
http://img183.imageshack.us/img183/9...stable6oa2.jpg
my cpuz -> http://valid.x86-secret.com/show_oc?id=172524
the 1T stress the overclock and chispet..I bet if he lowers to 2T he will get further
I am not blaming the ram...but the chipset/mobo on well it handles the 1T timing
Thanks, I like them too :DQuote:
Originally Posted by erwinz
2T command rate didn't get me any further. I think the NB needs 1.56v :(
I used the AMD overclock tool and got to 433 mhz fsb before super pi became unstable and crashed. Now every time I try and modify the fsb with AMD overclock tool my comp crashes :confused:
yup i think he coud try using 2T ^_^Quote:
Originally Posted by nealh
hey man hows your 10th aniversary crucial?? whats the highest async have you push it so far??
try reseting the cmos.. :) don't use cmos reload.. :) i got this problem.. and fix it by reseting the cmos and starting configuring my bios again..Quote:
Originally Posted by metalman2785