DFI UT X48-T3RS LanParty - Living Review - Page 35

eva2000 · #**341** 20-08-2008, 10:50

Quote:

Originally Posted by WILSON

Got another Q820A670 so my guess is that its a funny batch as ive got the same problem with the probe on core2 being faulty

. Has anybody else got this batch and has the same problem?

EDIT when temp goes above 37 it works???? very strange as it stops at 37 when it drops back down.

E8600 temp sensors are out of wack for most folks regardless of boards i think or a bios update is needed i.e. i'm testing 5x E8600 Q820A599s and exhibit similar stuck temp sensors

Glennswe · #**342** 20-08-2008, 11:14

Well when I say stock it actually is 400x10 and having divider at 400/1600. I am on the 0725 bios also. I have tried a lot of different settings, copied Praz also and with adjustments and no go. Either I got bad sticks or bios needs some work at DFI. I think it's the last alternative but of course I could be wrong. My OCZ worked on another board without problems though.

eva2000 · #**343** 20-08-2008, 11:20

Quote:

Originally Posted by Glennswe

Well when I say stock it actually is 400x10 and having divider at 400/1600. I am on the 0725 bios also. I have tried a lot of different settings, copied Praz also and with adjustments and no go. Either I got bad sticks or bios needs some work at DFI. I think it's the last alternative but of course I could be wrong. My OCZ worked on another board without problems though.

so you've tried each ddram default skew model from 0 to 7 yet ?

WILSON · #**344** 20-08-2008, 12:49

Well i passed occt with 1.32v load .

Glennswe · #**345** 20-08-2008, 21:54

Quote:

Originally Posted by eva2000

so you've tried each ddram default skew model from 0 to 7 yet ?

Atm I have tested both rams only, the strange part is the skew model 4 seems to be the best setting but will not boot to OS. Praz had the same rams and had skew model 3. Testing continues with each stick to see if it's one of them that doesn't work properly.

Praz · #**346** 20-08-2008, 22:17

DLL models and drive strengths are a handful on this board. Settings that are optimal at one FSB may not only be wrong for another FSB but might prevent the board from booting at all. Having manual control of these settings is not a bad thing. On the DDR2 board it has allowed me to run my CellShock up to 1300MHz when before 1180 had to be forced.

There should be an auto setting that will allow the board to boot and run without user intervention. Then if one wishes to fine tune have the ability to manually enter the values. However, the BIOS in it's current form, requires the user to be the BIOS programmer. It's just another example of how the BIOS is still in the engineering stage rather then a finished product ready for public use.

BlackDragon24 · #**347** 21-08-2008, 09:12

Alright I've been readin this thread for awhile now and decided to hop into the fire....been postin over at dficlub for awhile but I guess we can use all the help we can get.

Equipment is in my sig....as well as my 24/7 OC. My E8400 will go 8 x 500 but I can't get the damn memory stable at 1666.

Anyways here is my quick update with the 725 BIOS:

The 333/1333 is now completely stable for me at 9 x 400 ddr3 1600 7-7-7-24 1T. Leaving everything on auto results in a PL7, which I think is the best I can hope for with these timings. Requires 1.53v in BIOS to nb for stability.

The really strange thing? If I switch to 400/1600 and leave everything else the same, it won't allow me into windows....it gives me an error message saying some type of hardware change prevented it from booting with some type of kernel error.....weird. Switching back to 333/1333 gives me windows and complete stability (HCI memtest).

If I try and run 9 x 425 on the 333/1333 the board hangs at post screen....even if i manually set timings to 8-8-8-27 2T and PL9.

So I guess its time to start working those drive strengths and DLL models