**Official DFI LanParty UT P35-T2R Review/Overclock/Guide Thread**

[Brother Esau]

GROOVY ....LOL....I guess I am not in Moving Overclock Violation with 9/13/07 Beta now


UPDATE:.........For those concerned with the limited space between X16 PCI-E Slot and RAM Slots for Corsair Dominator Ram Cooler Clearance issues " Don't worry"! It fits just fine (Just Barely) but it fits without creating permanent bend of GFX Card over time, just do what I did and put 3 layers of electrical tape on the "Convex" bend where the ram clips go.

[Booj]

I see a few of you guys are running close to or max of 1.6v cpu vtt. Is that suitable for short benching only?

I'm on the official 13/9 BIOS now but i'm still having trouble getting prime blend stable with my G0 Q6600 over 400x9. It will do small fft all day at that setting. I've spent some time tweaking a few things.. Best i've got to is about 50mins prime blend before failing. I'm lurking everyday at the Tech Repository for FCG/Tony BIOS guide

I stuck a B2 E6300 in and it was good for 480x7 large fft so It has to be an issue with the Quad. with the quad max fsb i've gotten is a 475x6 spi 1m.

Sorry that sounds negative, but actually I love the board. It get on well with my Team Xtreem PC8500 cas4 sticks.

[Raja@ASUS]

vcore around 1.4, GTl's to 115/115/155 @ VTT 1.6, vnb to 1.61. Vcore droop to disabled should see you start to climb, as long a dram parameters are correct..

regards
Raja

[RLM]

A:\AWDFLASH.EXE LP35D913.BIN /CD /CP /CC /PY /CKS /SN /QI /LD /WB /E

The last Switching Parameter /E brings you back to A:\ Prompt //// after you Flash at that point I re enter the whole shpeel above once more and Flash a second time which results in a cleaner Flash and less chance of anything not getting over written the first time.........My buddy... Robert...(Rgone) taught me that trick with my D.F.I Expert Board

Brother Esau, if you check out the autoexec.bat, all but the /E switch are already in there.

@echo off
cls
@ECHO OFF
A:\AWDFLASH LP35D913.BIN /cks/sn/py/cc/cd/cp/ld/qi/WB
echo "The version of BIOS was inaccurate,"
echo "Please remove the floppy, download the right one and re-flash."
@ECHO OFF

Something I've noticed with my usb key. If you just change hard disk boot priority to your usb key, then the autoexec doesn't automatically run.

To get autoexec.bat to run automatically, I've found changing the USB Storage Function to FDD, and selecting first boot device to USB/ZIP does the trick.

RLM

[RLM]

eva2000 you're a star ,

Thanks for taking the time to delve into this.

Likewise I've been convinced the CLK, had a lot to do with C1 problems.

Yesterday I was almost convinced I needed a .5 setting though.

Will check out your post again.

Thanks a lot.

RLM

[retrospooty]

mine's running fine too, 3.6ghz cam @ 1.39 on the 266 strap. Now trying to psuh 1.437 for 3.704, both on air. With most timings on more aggressive too.. Retail b3 next..

Raja

Mine is great as well. Running 24/7 as spec'd in my sig. I can run 4ghz (8x500) stable, but I need to crank up my water pump and fans to levels I don't want to hear 24/7, but it works great. I have no issues at all except the occasional no post after changing certain BIOS settings (which is definitely an Intel issue, not DFI) and that is fixed by simply hitting the reset button.

[Booj]

vcore around 1.4, GTl's to 115/115/155 @ VTT 1.6, vnb to 1.61. Vcore droop to disabled should see you start to climb, as long a dram parameters are correct..

regards
Raja

Great! Thanks Raja! That NB GTL ref is quite a bit higher than I had tried up until now. The extra CPU VTT surely helps too. I was reluctant to set any DFI voltage option to the max out of fear of the board going up in flames.

Heres a screen of 1hr blend at 400x9, Fingers crossed it can go a while longer.



I have some water cooling gear on the way. A Swiftech Apogee GT, MCR320 rad, MCP655 pump etc. I am very much looking forward to seeing where I can bench from here.

Cheers
Chris

[RLM]

Just to confirm. If you open autoexec.bat in notepad, and add the /e switch to the end and save, it will do the trick.

You then just need to type autoexec.bat to repeat the flash.

RLM

[Raja@ASUS]

Np Booj, you should start to climb upwards now. As for CLK timings. WIth the right ram and Cas 5 the board can run quads upto 463 fsb on the 266 strap (1.65 vnb) and around ddr 1160, a.latency a nice 48 or so (which gives nice 'intelligent volt' performance), all clock defaults to 'more aggressive'. Oskar already stated to try 1-2 digits away from the default clock parameters if you believe you are experiencing bouts of instability.

Cas 5 gives a very good balance of performance/voltage on this board with speeds around 1120-1200mhz depending on fsb ratios. This is all micron D9 territory for the most part, with aggressive timings and some of the subtimings set manually...


regards
Raja

[cantankerous]

Just flashed to 9/13 without issues. Though I am not doing an aggressive overclock by any means I was able to use identical settings to what was used in 8/23 no problem. One thing I am wondering as I don't want to try until I have some confirmation, is the use of the 333/1066 divider? When I tried this on the 8/10 and 8/23 bios it ended up in an instant no post with a C1 error even if ram was left at default speeds as I am running PC2-8500 based ram with timings at Auto. From what I understand this was a problem with defaults being set too high and they needed to be changed or loosened before the 5:8 divider would work without issues. Am I the only one with this problem or can anyone share some info on what may be going wrong to cause a no post C1 error when using that divider? I have just been using the 333/800 and overclocking from there to avoid hassles. Thanks.

[Praz]

A:\AWDFLASH.EXE LP35D913.BIN /CD /CP /CC /PY /CKS /SN /QI /LD /WB /E

Something I've noticed with my usb key. If you just change hard disk boot priority to your usb key, then the autoexec doesn't automatically run.

To get autoexec.bat to run automatically, I've found changing the USB Storage Function to FDD, and selecting first boot device to USB/ZIP does the trick.

What works for me with BIOS default settings is changing A:\AWDFLASH.EXE to C:\AWDFLASH.EXE. I choose the USB drive in the hard drive list using the Escape key and and the flash sequence starts automatically.

[Brother Esau]

Brother Esau, if you check out the autoexec.bat, all but the /E switch are already in there.



Something I've noticed with my usb key. If you just change hard disk boot priority to your usb key, then the autoexec doesn't automatically run.

To get autoexec.bat to run automatically, I've found changing the USB Storage Function to FDD, and selecting first boot device to USB/ZIP does the trick.

RLM

Good Morning RLM I was sent the 9/13/07 Beta by Andre and it was just the .bin file and the Award Flash utility so I ran my own switching parameters and did everything manually.

[RLM]

Well still squealing like a little piggy, but seem to be making some headroom with the 9/13 bios. A thumbs up there.

Went for the double flash like Brother Esau, and a cmos flush.

Haven't nailed the gtl refs yet. 110/110/115 no different to 115/115/115. Would probably be more evident with longer prime runs. Thinking of reducing the vcore a tad, so barely stable and see what setting give me the longest stability in prime. Need a bit of time on that one.

Memory also needs work. At 1:1 4-4-4-12 with fast settings, prime failed after about 15 minutes. That was with higher NB, Vdimm and VTT than I have here. Will have to experiment there.

Hopefully can get a bit of work done now We'll see.

Large FTT 425x9 3.825ghz Memory 850 mhz 4-4-4-12-36 Perf lev 7


RLM

[Praz]

Anyone using the multi-threaded version of Prime95 might want to grab version 25.4. 25.3 had a pretty severe memory leak.

[Brother Esau]

Update: well here I am not 24 hrs into using this board and so far @ 3.2ghz and only cpu vcore bumped and Nbridge @ 1.45v CPU VTT @ 1.28v and Ram @ 1:1 DDR2 800 1.90v it for one has that High Pitched Noise we have all come to hate referred to as "Squeal" and also I have the Transpiper and copper plate on and my NB/ PWM are both at about 48c @ idle and oh yea my CPU at the same clocks as my ABIT IP35 PRO are 6c dearer at Idle and 10c more under load Way to go D.F.I and this is honestly a freaking joke for a $300.00 board and Smart Guardian is about as worthless as it comes these days too!

EDIT: I would like to just add for the Record that the above post made by me is wrong!
I opened my case up today to put a higher CFM Fan in the Tuniq 120 due to sub par Temps as stated above and to my dismay ......OK...I am a MEAT HEAD not only did I forget that I reversed the position of my Tuniq Tower and Forgot to take the fan out and reverse that as well so guess why my temps were higher all around CPU / PWM /NB .???? Thats right I'm a meat head thats why Sorry for the untrue statements on the cooling on the board because now my temps are 6c cooler at idle and 10c cooler under load I guess it helps when you don't have you're exaust blowing into the case

[dzeuk_ph]

Um, excuse me please,, is the 9/13 official bios different from the 9/13 beta bios? thanks!..

@all,

will memory settings hinder my system to go into windows?.. even if all settings were on auto?.. because I can't go to windows at greater than 4.1 gigs no matter how high the voltage..it keeps on restarting just right after the boot screen,,

need your inputs guys.. thanks..

[Praz]

will memory settings hinder my system to go into windows?.. even if all settings were on auto?.. because I can't go to windows at greater than 4.1 gigs no matter how high the voltage..it keeps on restarting just right after the boot screen

Possibly. Depending on system configuration Auto timings at times can be too tight. At 4.1GHz if it's the Q6600 in your sig it will most likely come down to GTL settings and/or board voltages.

[gandalfone]

In the LN2 session I had a Vcore read in bios at 1.88v but in win, smart G. and cpuz 1.41 1.93v
http://www.xtremesystems.org/forums/...d.php?t=159655

In the first screen cpuz read 1.936v but bios 1.88...mmm

Do you know a point to misure for read Vcore??

[Brother Esau]

Anyone using the multi-threaded version of Prime95 might want to grab version 25.4. 25.3 had a pretty severe memory leak.

Thanks John Priming right now after my 8hr warm up at defaults.

Can someone with the same G-Skill Ram post up their accurate sub timings please?

[Raja@ASUS]

updated thread here with 450fsb prime stable run and bios settings..

http://csd.dficlub.org/forum/showpos...8&postcount=19

[terroristone]

i want to kill my dfi t2r, was running all fine, i can home today and tryed to turn it on...C1 error, i tried removing one stik of ram, clear cmos, no good, tryed cheat ram and cleared cmos, no good, ahhhh any pointers???
Andrew.

[Raja@ASUS]

try to pull the psu power connectors from the board for 5 minutes and clear the cmos. Sounds like maybe your OC was not totally stable...

regards
Raja

[Seanie's Show]

I see a few of you guys are running close to or max of 1.6v cpu vtt. Is that suitable for short benching only?

I'm on the official 13/9 BIOS now but i'm still having trouble getting prime blend stable with my G0 Q6600 over 400x9. It will do small fft all day at that setting. I've spent some time tweaking a few things.. Best i've got to is about 50mins prime blend before failing. I'm lurking everyday at the Tech Repository for FCG/Tony BIOS guide

I stuck a B2 E6300 in and it was good for 480x7 large fft so It has to be an issue with the Quad. with the quad max fsb i've gotten is a 475x6 spi 1m.

Sorry that sounds negative, but actually I love the board. It get on well with my Team Xtreem PC8500 cas4 sticks.

I know exactly how you feel, my G0 stepping quad posts and boots to windows vista at 3.8-3.9ghz, but I am struggling to get it stable anything over 400mhz FSB on this board (3.6ghz), upto 400mhz I have the following settings and will blend prime all day and all week with my crucial ballistix 667mhz at 1000mhz:

CPU = 1.45v, RAM = 2.23v, FSB VTT = 1.38v, NB = 1.45v, SB = 1.15v, GTL's all currently Disabled, Clock Gen = 3.45v, mem is running at 4-4-4-12 @ 1000mhz.

However even at 401 FSB everything becomes unstable, I just dont get it, ive tried bumping up voltages etc and it doesnt seem to make any difference, im not willing to run the NB at 1.6v 24/7 as it already gets hot enough (47oC with a fan on it whilst blending).

I was testing memory earlier incase that was the problem, and the memory was stable no matter what dividers I used all the way upto 1000mhz 4-4-4-12, some of this testing was done with the board and the CPU at stocks, others required the FSB moving up and the multiplier on the CPU dropping to keep the CPU at stocks, but once again, the minuite I pushed the FSB over 400 it was failing memtest again, I think the setting I had on the ram at the time was 333/800. at 400FSB it was at 960mhz so I pushed the FSB to 416 to put the ram at 999mhz (1000mhz) and like I said it was failing memtest.

Below is a kind of review I just typed up for myself to keep myself in check, so I knew what I had tried and what I had'nt, feel free to download it and have a look, then hopefully someone might beable to answer both of our issues.

[RLM]

CPU = 1.45v, RAM = 2.23v, FSB VTT = 1.38v, NB = 1.45v, SB = 1.15v, GTL's all currently Disabled, Clock Gen = 3.45v, mem is running at 4-4-4-12 @ 1000mhz.

You need to up your VTT and NB. No avoiding it. You might not want to hit 1.6+v, but you will have to try 1.5+v.

Gtl refs, I've found around the x67 start point pretty good, say NB=1.55 (1.57) VTT = 1.53 (1.55) Gtl refs 105/105/112. There's no guarantee, but this has worked for me.

Well on the cpu side of things anyway.

RLM

[Praz]

GTL's all currently Disabled

Going to be different depending on the individual board/processor but a person isn't going to get far without adjustment of GTL settings. Higher clocks can be forced with the use of voltage but not much will be gained.