Gigabyte GA X38 DQ6 Blog

[Vbs]

Zenoth, nice to hear you found your memory was OK

Never tried HCI Memtest, I've been using Memtest86+ since my Athlon XP 1400 days (actually only Memtest86 existed back then, Memtest86+ came much after and from a different developer). I find it as fundamental as Prime95 to check memory o/cs, since it tests the whole memory with many different read/write patterns. Also since it uses it's own O/S and boots in ~5 seconds, it's very nice when you're in that "loop" trying to get the right memory timings (BIOS -> Memtest -> Reboot -> BIOS -> Memtest -> ...)

Cheers!

[Zenoth]

Alright, right now I'm testing at:

MB Intelligent Tweaker (MIT)
Robust Graphics Booster: Auto
CPU Clock Ratio: 9x
CPU Host Clock Control: Enabled
CPU Host Frequency(Mhz) : 400
PCI Express Frequency (Mhz) : 100
C.I.A.2: Disabled
Performance Enhance : Standard
System Memory Multiplier (SPD) : 2.66D (3:4)
Memory Frequency(Mhz): 1066
DRAM Timing Selectable : Manual

Standard Timing Control
CAS Latency Time: : 5
DRAM RAS# to CAS# : 5
DRAM RAS# Precharge : 5
Precharge Delay(tRAS) : 18

Advanced Timing Control
ACT to ACT Delay(tRRD) : 6
Rank Write to READ Delay : 6
Write To Precharge Delay : 8
Refresh to ACT Delay : 68
Read To Precharge Delay : 6
tRD : 7
tRD Phase Adjustment : 1
Command to #CS Timing: : 2

Clock Driving and Skew Control
CPU/PCIEX Clock Driving Control : 1000mv
CPU Clock Skew Control : Normal
(G)MCH Clock Skew Control : Normal

System Voltage Control : Manual
DDR2 OverVoltage Control : +0.25v (2.08v)
PCI-E OverVoltage Control : Normal
FSB OverVoltage Control : +0.20v
(G)MCH OverVoltage Control : +0.175v
MCH Reference Voltage Control : Normal
DDR Reference Voltage Control : Normal
DDR Termination Voltage Control : Normal
CPU GTLREF1 Voltage : Normal
CPU GTLREF2 Voltage : Normal
CPU Voltage Control : 1.31500v (1.296v in CPU-z)
Normal CPU Vcore : 1.22500v

And so far no errors in HCI Memtest. I will test with Orthos Blend right after I consider it to be "stable". By the way, I've noticed that HCI Memtest seems to stress the system noticeably more than even Orthos Blend does, or even when compared to Prime95. I mean when I was testing with Orthos I could easily launch any games I wanted and play them (with some hiccups here and there of course, it was slower but still playable), but now with HCI Memtest it took around 10 seconds to open up Firefox, and each web-page I'm going to takes around five seconds to finish loading completely (when compared to the usual "instant" speed I get, I rarely wait over two or three seconds for big pages filled with pictures).

Is it just me or it is indeed a "better" stress testing method?

[supershanks]

I've mixed feelings about both memtest. and tend to use both on occasions.

Neither are perfect - memtest86 biggest weakness is it doesn't test in a windows environment. HCI Memtest for windows biggest fault - it doesn't test all your memory.

I agree

it's very nice when you're in that "loop" trying to get the right memory timings (BIOS -> Memtest -> Reboot -> BIOS -> Memtest -> ...)

is good to tune ram., though there are many occasions when i've been memtest86 clear but still had memory errors in windows.

Tend to use '86 as an initial tool then HCI as a final check, between the 2 they'll do the job.

Is it just me or it is indeed a "better" stress testing method?

Think it's down to the amount of memory you allocate to the 2 sessions.

luck

PS I'd still be inclined to increase

PCI-E OverVoltage Control : Normal

to +.2v

[Marcus]

Hi guys I finally got my crucial ballistix 8500 to replace my hyperX 9600.

So far it goes a little bit better but I still cannot run prime95. As soon as I start boom...

I don't know what to try right now...I tried to increase the vcore but even at 1.5125v it does work.

please help
thanks :-)

Bios F5H

MB Intelligent Tweaker (MIT)
Robust Graphics Booster: Auto
CPU Clock Ratio: 9
CPU Host Clock Control: Enabled
CPU Host Frequency(Mhz) : 400
PCI Express Frequency (Mhz) :100
C.I.A.2: Disabled
Performance Enhance : Standard
System Memory Multiplier (SPD) 2.66d
Memory Frequency(Mhz): 1064
DRAM Timing Selectable : Manual  
Standard Timing ControlCAS Latency Time: : 5
DRAM RAS# to CAS# :7
DRAM RAS# Precharge :7
Precharge Delay(tRAS) :12
Advanced Timing Control 
ACT to ACT Delay(tRRD) :3 - auto
Rank Write to READ Delay :3 -auto
Write To Precharge Delay :6 - auto
Refresh to ACT Delay : 35
Read To Precharge Delay: 3 - auto
tRD :Auto
tRD Phase Adjustment :Auto
Command to #CS Timing: :2T
Clock Driving and Skew Control
CPU/PCIEX Clock Driving Control : 1000
CPU Clock Skew Control : Normal 
(G)MCH Clock Skew Control : Normal
System Voltage Control Manual
DDR2 OverVoltage Control : 0.35
PCI-E OverVoltage Control : 0.35
FSB OverVoltage Control : 0.2
(G)MCH OverVoltage Control :0.175
MCH Reference Voltage Control : Normal
DDR Reference Voltage Control : Normal
DDR Termination Voltage Control : Normal
CPU GTLREF1 Voltage* : Normal
CPU GTLREF2 Voltage* : Normal
CPU Voltage Control : 1.45
Normal CPU Vcore : 1.2625

[supershanks]

Hi Marcus

tRD :Auto

--> 7 if still unstable try 8 though performance takes a hit

DRAM RAS# to CAS# :7

--> 5

DRAM RAS# Precharge :7

-->5

Precharge Delay(tRAS) :12

**
**= If stable after adjusting above try reducing to 10 , you should be able to run fine & faster


luck

[Marcus]

Originally Posted by supershanks

Hi Marcus

--> 7 if still unstable try 8 though performance takes a hit

--> 5
-->5
**
**= If stable after adjusting above try reducing to 10 , you should be able to run fine & faster


luck

I already tried that :-(

now I'm trying 9x multiplier
so

9x 285
5,5,5,15
ACT 35
reste auto
1.45v

Ps what is TRD? the tRead Value ??

[supershanks]

I already tried that :-(

did you try 8??


tRD is Read Delay , also called Performance in Memset see The Clock Crossing Procedure and MCH Read Delay (tRD)

On the DQ6, it' the value that generally causes issues. Especially if left on auto as explained already hereOverview

The biggest problem setting is with the Static tRead Value Trd The value is modified according to the value of the Performance Enhance Settimg ([Standard], [Turbo] & [Extreme]) and strap used. The value selected on auto is often too tight. If running >400 FSB it’s best to use a minimum value of 7. The other option is to run at a lower Performance setting, with the corresponding performance hit.

luck

[Marcus]

Well I dropped the fsb to 385x9 just to make sure and it still crashes in prime95 after few seconds....

I'm on water and the temps get a little warm at 1.45v....60-65C

I might try to put arctique silver 5 and make my tubes smaller to increase the flow a bit.
But what is the voltage I should put to make sure all works...well to start with will be more appropriate lets say :-)

[Zenoth]

Something I've just noticed...

According to Station-Drivers, the beta BIOS version F8c fixes the following:

"Fix Strap 2.66, 2.00A, 2.50A and 3.00A"

GIGABYTE GA-X38-DQ6

Maybe that most of my issues were related to whatever bug was found with F7 and those Straps? Because I've been using them often, and in fact I am using Strap 2.66D right now. I'm not sure if I'm going to flash to F8c, but I will definitely flash to the final version of F8 whenever it's released, I think that Gigabyte are doing a nice job.

[supershanks]

Marcus,
what vcore depends to some extent on the vid of your cpu. you'll find the vid of your cpu from coretemp Death's vid & coretemp download mine is 1.2625v

To hit 9x400 my 9x400 settings There are also some adjustments i found i could make later further down the post.
I managed it at 1.40625 ~1.425v
A rough starting point for you might be 1.425v/ My VId (1.2625) x whatever your VID is.

DDR2 OverVoltage Control : 0.35

Try 0.40v rest look ok.

Zenoth,
Good find think i'd have flashed by now
Let us know how it goes.

how did

And so far no errors in HCI Memtest. I will test with Orthos Blend right after I consider it to be "stable"

go ??

did you try

PCI-E OverVoltage Control : Normal to +.2v

??

luck