DFI Ultra D - System not stable over 300FSB

[Rapier]

I've been reading in several forums for the past few days and I can't say I've found my answer yet. My Ultra-D seems to hit a wall at 300 FSB. The opteron I've clocked down to 9x from 10x on the multiplier (2.7 ghz) where the opteron isn't even breathing hard. She just isn't stable at that 300+. I know the board can do it, I could use some advice on getting it there. System is listed below with some bios info. I'm no nooby to overclocking, just to DFI boards. Thanks in advance for the help.

System Info.

DFI Lanparty Ultra-D
Opteron 146
Geil PC4400 2x 512mb
BFG 6800GT
WD Raptor 74gb
Seagate 200gb IDE
Hitachi 160gb SATA
OCZ 520 SLI PSU
Liteon 193 DVD/RW

Here is some Bios info:

Bios dated 6/23/2005 NF CK804 (I hope this is the right info)

Genie BIOS Settings:

FSB Bus Frequency - 300
LDT/FSB Frequency Ratio - Auto
CPU/FSB Frequency Ratio - Auto
PCI eXpress Frequency - 100Mhz
CPU VID StartUp Value - Startup
CPU VID Control - 1.550v
CPU VID Special Control - Above VID * 104%
LDT Voltage Control - 1.30v
Chip Set Voltage Control - 1.60v
DRAM Voltage Control - 2.70v



DRAM Configuration Settings:


DRAM Frequency Set - 166
Command Per Clock (CPC) - disable
CAS Latency Control (Tcl) - 2.5
RAS# to CAS# delay (Trcd) - Auto
Min RAS# active time (Tras) - Auto
Row precharge time (Trp) - Auto
Row Cycle time (Trc) - 07 Bus Clocks
Row refresh cyc time (Trfc) - Auto
Row to Row delay (Trrd) - 02 Bus Clocks
Write recovery time (Twr) - 02 Bus Clocks
Write to Read delay (Twtr) - 03 Bus Clocks
Read to Write delay (Trwt) - 05 Bus Clocks
Refresh Period (Tref) - 3120 Cycles
Write CAS Latency (Twcl) - Auto
DRAM Bank Interleave - Enabled


DQS Skew Control - Auto
DQS Skew Value - 0
DRAM Drive Strength - Auto
DRAM Data Drive Strength - Auto
Max Async Latency - Auto
DRAM Response Time - Normal
Read Preamble Time - Auto
IdleCycle Limit - 256 Cycles
Dynamic Counter - Disable
R/W Queue Bypass - 16 x
Bypass Max - 07 x
32 Byte Granularity - Disable(4 Bursts)
__________________

 

[coomar]

Chip Set Voltage Control - 1.60v

bump it to 1.7V

 

[coomar]

LDT/FSB Frequency Ratio - Auto

you should set that to 3x

 

[coomar]

Command Per Clock (CPC) - disable

you should turn CPC on, it should be able to work with your ram (though this has nothing to do with the max HTT of 300 problem)

 

[Thor86]

It would help if you told us what you used for stability testing, and what kinds of in-stability you experienced.

 

[coomar]

RAS# to CAS# delay (Trcd) - Auto
Min RAS# active time (Tras) - Auto
Row precharge time (Trp) - Auto

your better off generally setting these to whatever the ram is supposed to run at (it looks like your underclocking the ram), you don't want the SPD to set the timings for you

 

[Rapier]

LDT/FSB Frequency Ratio - Auto

you should set that to 3x

The box doesn't want to get into windows at 3x LDT. 2x will work at 300FSB.

Command Per Clock (CPC) - disable

you should turn CPC on, it should be able to work with your ram (though this has nothing to do with the max HTT of 300 problem)

I remember when I ran this memory on this chip and my old winchester (at 1:1) on my MSI board that the ram couldn't handle 1T at anything much over 255 FSB. Thats why I changed it to 2T

It would help if you told us what you used for stability testing, and what kinds of in-stability you experienced

The opti can handle 300FSB in my MSI board at 1.52 volts on the core. Right now I've got the mem set to DDR 266 at 2.7 volts, 2T and CAS 2.5 (all to take the mem out of the equation) . The core is set to 1.55v + 1.04%. LDT at stock volts and auto. Everything else is default. She'll prime, Super Pi, and fold all day long. I can play CS:S for 20 mins and video shuts down and locks-up. No BSOD.

RAS# to CAS# delay (Trcd) - Auto
Min RAS# active time (Tras) - Auto
Row precharge time (Trp) - Auto

your better off generally setting these to whatever the ram is supposed to run at (it looks like your underclocking the ram), you don't want the SPD to set the timings for you

You make a good point it being set at SPD. The board might ramp-up these settings if I'm under-clocking the ram

 

[rise]

try your trrd @ 3. i had a similar problem with morrowind crashing me out even though pi, prime, folding, occt etc were stable and that fixed me.

i also use tref "auto" unless i have to change it.

i'm sure you've probably seen it but just in case.

 

[Mucker]

Take your ram voltage to 2.8 too....

 

[Shimmishim]

try more voltage for the cpu.

just cuz it'll do it on one board at one voltage doesn't mean it will on a different board.

also, can you run superpi32M on the dfi board?

 

[Rapier]

Originally posted by: rise4310
try your trrd @ 3. i had a similar problem with morrowind crashing me out even though pi, prime, folding, occt etc were stable and that fixed me.

i also use tref "auto" unless i have to change it.

i'm sure you've probably seen it but just in case.

I've read the FAQ. I've also got this posted over at DFI Street and Xtremesystem forum. One guy suggest I try the following setting. Do you have a opinion?

Genie BIOS Settings:

FSB Bus Frequency - 300
LDT/FSB Frequency Ratio - Auto
CPU/FSB Frequency Ratio - 9
PCI eXpress Frequency - 100Mhz
CPU VID StartUp Value - Startup
CPU VID Control - 1.550v
CPU VID Special Control - Above VID * 104%
LDT Voltage Control - 1.30v
Chip Set Voltage Control - 1.60v
DRAM Voltage Control - 2.70v



DRAM Configuration Settings:


DRAM Frequency Set - 166
Command Per Clock (CPC) - enable
CAS Latency Control (Tcl) - 2.5
RAS# to CAS# delay (Trcd) - 4
Min RAS# active time (Tras) - 10
Row precharge time (Trp) - 4
Row Cycle time (Trc) - 14 Bus Clocks
Row refresh cyc time (Trfc) - 24
Row to Row delay (Trrd) - 03 Bus Clocks
Write recovery time (Twr) - 02 Bus Clocks
Write to Read delay (Twtr) - 02 Bus Clocks
Read to Write delay (Trwt) - 03 Bus Clocks
Refresh Period (Tref) - 3120 Cycles
Write CAS Latency (Twcl) - 3
DRAM Bank Interleave - Enabled


DQS Skew Control - Enable
DQS Skew Value - 212
DRAM Drive Strength - 5
DRAM Data Drive Strength - 2
Max Async Latency - Auto
DRAM Response Time - Normal
Read Preamble Time - Auto
IdleCycle Limit - 256 Cycles
Dynamic Counter - Disable
R/W Queue Bypass - 16 x
Bypass Max - 07 x
32 Byte Granularity - Disable(4 Bursts)

 

[Rapier]

Originally posted by: Shimmishim
try more voltage for the cpu.

just cuz it'll do it on one board at one voltage doesn't mean it will on a different board.

also, can you run superpi32M on the dfi board?

I've tried up to 1.62 volts on the core and it doesn't seem to help. She'll prime, Super Pi, and fold all day long. I can play CS:S for 20 mins and video shuts down and locks-up. No BSOD.

I has occurred to me that it could be a possible video card issue, since its a new card (BFG 6800gt PCI-e) and it always locks-up with a video shutdown and it only does it in CS:S. It'll Q4 and 3Dmark 2005 all day long, though. I notice the temp on the GPU gets highest with CS:S at a max I've seen of 204F. Just on the change I underclocked the 6800gt to its normally stock speed of 350mhz (the BFG it OC'ed out of the box at 370mhz)

 

[Thor86]

Maybe your CS:S is corrupt or video driver related. Have you tried 290FSB/HTT and play CS:S?

 

[rise]

try running rthdribl for a while and see if it is a temp issue.

not having your ram its difficult to dial in settings.

edit-btw, i don't think it is a heat issue but you matters well check. when i had the problem, every game was fine except morrowind.

 

[Rapier]

Originally posted by: Thor86
Maybe your CS:S is corrupt or video driver related. Have you tried 290FSB/HTT and play CS:S?

280FSB is no problem playing CS:S. I haven't tried to narrow it down from there. I do know at the 300FSB the CPU is~18F or so higher which adds to the case temp. Typically CS:S generates the highest temp on the Video card (even over Q4), but I'm running 4xAA in CS:S. 280 FSB and 300 FSB will show a 10F increase in the GPU core at a max of 204F. I figure most of its from the higher case temps. (its the only thing that makes sense)

 

[Rapier]

Originally posted by: rise4310
try running rthdribl for a while and see if it is a temp issue.

not having your ram its difficult to dial in settings.

edit-btw, i don't think it is a heat issue but you matters well check. when i had the problem, every game was fine except morrowind.

First I've heard of that program? Do you really think it'll generate higher temps then CS:S for me. I'll try it when I get home.

 

[coomar]

try rthdribl

 

[rise]

Originally posted by: Rapier
First I've heard of that program? Do you really think it'll generate higher temps then CS:S for me. I'll try it when I get home.

yeah, rthdribl is the heat miser. it will crank it up in no time

 

[Rapier]

Originally posted by: rise4310

Originally posted by: Rapier
First I've heard of that program? Do you really think it'll generate higher temps then CS:S for me. I'll try it when I get home.

yeah, rthdribl is the heat miser. it will crank it up in no time

Maybe I should overclock it at the same time at a known stable speed on the CPU (e.g. 280 FSB)

 

[Munky]

I notice the temp on the GPU gets highest with CS:S at a max I've seen of 204F

That is freakin hot right there. Did you try lowering your cpu/fsb clocks and play CS:S to see if it still locks up. It might be the video card overheating.

 

[rise]

Originally posted by: Rapier

Originally posted by: rise4310

Originally posted by: Rapier
First I've heard of that program? Do you really think it'll generate higher temps then CS:S for me. I'll try it when I get home.

yeah, rthdribl is the heat miser. it will crank it up in no time

Maybe I should overclock it at the same time at a known stable speed on the CPU (e.g. 280 FSB)

thats my final stability test actually, prime large and rthdribl. gets the chipset heated up too.

 

[coomar]

prime large doesn't seem to hit the cpu as much as the ram

rthdribl isolates the gpu

prime small ffts and rthdribl

 

[rise]

Originally posted by: coomar
prime large doesn't seem to hit the cpu as much as the ram

rthdribl isolates the gpu

prime small ffts and rthdribl

yeah, but by the end, i've already small primed it so i like the large then

 

[coomar]

i don't really see the point of large ffts, memtest is for the ram

 

[Shimmishim]

Originally posted by: coomar
i don't really see the point of large ffts, memtest is for the ram

agreed!!!