nice clock you got there.. :) what NB vltage you use??Quote:
Originally Posted by flytek
Printable View
nice clock you got there.. :) what NB vltage you use??Quote:
Originally Posted by flytek
hey, what BIOS settings are you using, I'm having difficulty getting over 400FSB with my E6400/DFI-ICFX3200, and i have room to play with regarding temps.Quote:
Originally Posted by bypolar
425FSB would be nice..... 3400Mhz on air is my aim, and i can sync my RAM nicely up to there (bandwidth seems to drop a bit with ASYNC).
1.66 for NB and 2.03 for one of the pll's...just for max overclock and short benches.Quote:
Originally Posted by erwinz
NB strapp 333.
also i found fo max ram clocks i needed to boot the ram as high as possible before clocking up
normally i just run 400 1:1 sync mode.
Man changing to sync mode killed my bios/board..it may have had to do with ancillary voltagesQuote:
Originally Posted by flytek
I guess in retrospect..I would recommend increasing some voltages prior to sync mode abit...ie NB 1.8 PLL, convert and pci-e voltage
Btw guys, I know what my multiplier issue was... Oddly enough it was running windows Vista. But back on XP x64, multiplier acts like it should.
Good deal, I was wondering what that was.Quote:
Originally Posted by Suicide King
I´m just playing with some 3060´s here and while testing i did see my "old" nF4 DFIs on the shelf. Dunno why - but after one 3060 would not play over 3825MHz - i remembered the VCore Add % Option on the nF4s. This Option helped a lot during the "good old" nF4 times, "so what the heck" i thought and adapted the settings on one of my ICFX3200`s and ->
Findings:
"old":
3.80 100% stable with 1.5125V (Bios) - SG 1,42V - no %
3.85 No-Go with up to 1.6V (Bios) (reboot after ~ 2 mins)
3.90 No-Go (reboot after ~ 2 mins)
"new":
3.90 priming since ~ 30min with 1,5000 (Bios) + 5% :woot:
SG shows 1,47V under full load :clap: :clap: :clap: - Coretemp reports 74c :eek: - but no worry - it`s a very tiny h2o setup with a dual-radi.
If that works, i try to get the vcore down a bit and test again - looks like S775´s react kinda the same way the S939`s did in the past.
Dunno why :D - but so far i`m more than happy :banana: with that finding :toast:
Sometimes it´s good to look back and bring back some memories :rolleyes:
great results there man, can you please post your detailed settings on that 3.9GHz new setting? thnx ;)Quote:
Originally Posted by Pete@X
well I thought about this as well because of the DFI SLI DR mobo I have but trying to figure out what combos might seemed impossibleQuote:
Originally Posted by Pete@X
many seem to say the DFI SLI DR/Ultra D like 104%/110%/113%....but I did seem to get anything that helped me
How did you choose 5%..trial and error....I guess you are finding this is providing a more stable vcore under idle and load conditions?
@nealh: yapp - VCore is more stable ... and how i found the 5% :rolleyes: , was just a 1st Test if it helps is some way ... neeed to dig a bit deeper into the % settings ....;)
Here we go:Quote:
Originally Posted by marauder16
(Bios 12/02/07)
Performance Options
Memory Clock Frequency:AUTO
Control CPU Frequency: Manual
CPU Frequency(MHz): 435
NB FSB Strapping: 333
PCIE Overclock: 101
Software Reset Clockgen: Disabled
Memory Overclocking: Enabled
Overclocking Frequenca: 433
-------------------
NorthBridge Selections
Memory Channels: Auto
Memory Power Management: Disabled
IGD Clock Gate: Disable
NB Channel Mapping: Auto
Simple Addr Translation: Disable
Chip-Select Swap: Disable
Burst Length: 8
Bank0 Map GFX: 4
Bank1 Map GFX: 5
Bank2 Map GFX: 6
Channel Mapping NB: 5
Channel Mapping GFX: 1
Bank0 Map NB: 5
Bank1 Map NB: 11
Bank2 Map NB: 7
--------
Memory Timing Menu
CS Output Timing: Delay 1/4
Dual Channel Split Mode: Auto
Addr/CMD Driving Pre-AMP: Disabled
Addr/CMD Driving Strenght: 5
Clock Driving Pre-AMP: Always
Clock Driving Strenght: 13
Address/Command Timing: Auto
Memory Timing Select: Manual
...
...
Read Data Transfer: Enabled
Read Strobe Delay: Disable
Read Strobe Arrival: Enabled
--------
FSB IO Strenght
FSB IO Driving Control: Default
1X NMOS Strenght: 10h
1X PMOS Strenght: 10h
2X NMOS Strenght: 10h
2X PMOS Strenght: 10h
4X NMOS Strenght: 10h
4X PMOS Strenght: 10h
-------------------------
CPU VID Control: 1.50000V
CPU VID Special Add: 105%
DDR2 RAM 1.8V Voltage: 2.10V
CPU VTT 1.2V Voltage: 1.44V
NB Core 1.2V Voltage: 1.48V
NB PLL 1.8V Voltage: 2.13V
NB PLL 1.2V Voltage: 1.38V
NB PCI-E 1.2V Voltage: 1.34V
NB Core 1.2V Convert From: 2.14V
SB Core 1.2V Voltage: 1.34V
Clockgen Voltage: 3.40V
GTL REF Voltage Control: Enabled
CPU Core 1/2 GTL REF Voltage: 48
CPU Core 3/4 GTL REF Voltage: 48
North Bridge GTL REF Voltage: 128
CPU PLL Setting Override: Enabled
Conroe P-State Multiplier: Auto
C1E Function: Disabled
thnx man ;) will try to test this.
EDIT: lol, those settings didn't even get me to windows, it's so weird how same settings work on different systems, now testing at same but 3.8GHz
EDIT2: ok, I give up until I get a HR-05, crashed at 3.8GHz after a few minutes, lol...
I tested the board today with an Intel Pentium 630 SL729 and had exactly the same problems. I've tried different combinations with the power conector (floppy on/off, switched, etc). I also noticed that:
- the RAM L.E.D. doesn't power up, but the modules are good (tested on ECS mobo :D).
- if the beeper is ON, it makes a very low noise when starting/shuting down the board, something like a little "poc".
So, I bealive it's dead before I even started it. Good. NOT. :mad:
So being as you GTREF settings are still 48, you ain't played around with these? They seem to be key settings from what I have read.
hey all anybody have use.. Team Xtreme 667 cas 3 on the DFI RD600 board.. :) can anybody post there highest orthos stable results.. :)
thanks.. :)
Since forking out for a RocketRaid 2310 PCI-e Controller, this board absolutely Flys compared to using the boards ATI or Promise. I was getting fed up with courrupt files off the ATI headers & almost Clockwork-like speeds from Promise. It`s a shame they left 8 month old technologies on the board on it's release date & we might have AMD to thank for that. (not that I blame them)
Anyway, I still havn't blown board number 3 yet, not that I did with board number 1 or 2, but the day this board dies is the Day it gets posted to DFI with a simple letter telling them where to put it. £206 for a board with sh1t slow Promise or Corrupted files off ATI takes the pi$$ at any level in this Industry. Whilst we have talented people like Oskar doing the Bios scene, I would suggest we need better board testers in the Industry that can actually conduct tests properly. Having read some earlier posts about RD600 Raid being fine & without issues, I'd suggest these people look for another Job! :slapass:
Equally, whilst having had 8 DFI boards across 2 platforms, to get ONLY 2 boards to work...Help-a-fella....I`d say DFI need to do summat big-time about their cr4p components supplier or manufacturing process or even both. 75% failure is just sh1t.
mm.. hope there is a new bios.. :) DFI this is a Landparty BTW.. cough DFI new bios please.. and options for promise raid..
I need some help guys I got my new RD600 from RMA
my idle cpu temp at same vcore of 1.52 is 40c(about 3-4 lower(ambients are couple of degrees cooler this am)
BUT my NB temp suck..at stock 1.3v..with a microcoo whisper XE it was 59C....
just could not seem to get good heat transfer(contact did not look really bad when I looked at TIM on the HS..
I switched back to stock HS and added a 50mm fan on top...idled at 55C at 1.3v
at 1.42v(that I needed befroe to run at 390 fsb) I idle at 59/60C...quick 3 min Prime blend and I hit 64C!!!!!!
I am going to go back and remove the 50mm and use a 120mm fan blowing on chipset....but that means I have to remove my new corasir memory cooler
what are the safe temps on this chipset
BTW my cpu did seem to load Prime 95 higher also on the new board(generally on old board I hit 56C max on coretemp....quick run and coretemp hit 53C...also it seems SG and coretemps seem a little closer off this board..generally at least 5C difference...but now 2-3C..load temps...idle temp all 3 are just about equal)
I have no idea if this board has a better temp reporting....or another other dead board???
Seems about right all round. I'm on water NB & CPU & can confirm 55 Deg idle on NB with Stock Cooler @ 1.3V. I had to wait for my NB Block to arrive.Quote:
Originally Posted by nealh
Where are you taking your Temp readings from & using "what"? .....if software!
Well, I thoght I'd killed summat today! Board started randomly crashing. IE errors, corrupt ini files......All for trying a 200 STRAP on a lower FSB & playing with AMD System Manager & Yes, Allow Software Clockgen Option was ENABLED in Bios!
RESET CMOS, load saved Bios settings...NO POST?????
RESET CMOS, change ONE fkin Item like no BOOT PIC....NO POST?????
Had to pull all USB out of the Back, plug in PS2 keyboard, EZ RESET CMOS & Re-flash Bios from DOS Session using the EZreset defaults. Thank JFK I had original BIOS on floppy otherwise I'da been totally JFK'd.
Being quite honest about this RD600, it's a piece of sh1t when it goes wrong!
Maybe I'm lucky to have gotten out of this mess cos I'm now back at 370fsb 1:1 but ffs & wtf?
Support from ATI & DFI is poor.....ICFX3200 T2R/G...Released as an alive Donkey but only with 3 legs. :rolleyes:
JD & Coke anyone? :D
Reading back over the thread m8, I'm at stock Voltages 1:1 370fsb. ;)Quote:
Originally Posted by nealh
Are you getting 55C on NB at idle with waterQuote:
Originally Posted by Kin Hell
I only have SG as a guage for chipset temps....idle with 1.42v at 59/60..seems much hotter than the first mobo...quick load temp was 63/64 C
Sounds realy high, i used an MCX 159-cu on n-b 1.42v @ load ~46c idle ~43c
what are your ambient temps.....Quote:
Originally Posted by Ten
are you using the shims from swiftech?
about ~22 ambient and yes i used the shims from swiftech. Fits like a glove:) but i used a e67 and not so high fsb just 370 if that matters?
very nice temps..my ambients if Florida tend to run 25/26CQuote:
Originally Posted by Ten
I would guess a higher fsb will add more heat...not sure though