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

[runmc]

I'm siked to be getting close to 24/7 with this one. This chip is so much better than my other, it's just ridiculous.

Here's the same clock with lower nb and vtt, priority 9 blend 2hrs...



Still with 1.13vtt and 1.32nb I used 59/59/59 gtls. Any lower and I bottomed out, for example, crashed orthos in about 20min at 57/57/57 with those same voltage settings. 59 seems to be the sweet spot for these settings / my setup.

Edit - I'm using Bios 01/09

Very nice chip Can you show us more settings? I can't quit run as good as you are but I'm running stock hsf. With stock cooling I want to stay under 1.3V.

[mrcape]

Sure, I can. I have this profile in Cmos reloaded, so let me look at it and I'll put the bios settings in the template in about 30 minutes.

[mrcape]

took some quick pics instead. Very basic for that run, have tuned memory since then.

But this is exact settings in that run -

[mad_skills]

I've reached 24/7 stability on 3.8GHz (8x475MHz) @ 1.5V for my E6750.
Used 1.4V NB vcore and GTL settings 96/95/96. Not bad at all.
Gonna try some more MHz and voltage tomorrow.

[runmc]

Sure, I can. I have this profile in Cmos reloaded, so let me look at it and I'll put the bios settings in the template in about 30 minutes.

Thank you for the help. I'll keep tweaking

[emoners]

I've reached 24/7 stability on 3.8GHz (8x475MHz) @ 1.5V for my E6750.
Used 1.4V NB vcore and GTL settings 96/95/96. Not bad at all.
Gonna try some more MHz and voltage tomorrow.

looking good dude! what's your temp?

[fireice2]

@mon

I think we got a not so good chip out here. requires over 1.4v to be stable at 4ghz.

I'm planning of getting another. hehehe

[emoners]

@Matt: i know kinda sucks...and there are no more stocks of these procs in our place. Well that's living in the 3rd world...no good stuff ever comes to us

[kitfit1]

Hey guys,

Wanted to run something past you, thats makeing my life a bit difficult with this board.

OK, as I posted a page or 2 back, I have 4ghz 12hrs prime stable at 1.32v. Ive also run memtest overnight, to check my memory settings are ok.

However, sometimes when switch on my PC it freezes on the windows loading screen for no apparent reason. I have to restart a few times, and sometimes even that doesnt work. In which case I have to clear cmos and manually set all my individual settings. It seems cmos reloaded doesnt even allow it to boot (its like its not applying the settings correctly).

Once ive manually re-entered the settings, it boots fine, and runs windows. Ive even primed it again to make sure.

Its really quite frustrating, and it also makes it hard to push the chip further, cos your not sure if windows is freezing because of a bad overclock or not.

Im on 0109 bios, so maybe its a BETA bios issue? Any thoughts?

Yep, same thing here as well. I don't think it is the bios revision as such, because it does the same with the 12/24/07. I think i have narrowed the cause down a bit though. Like you i have a good stable 24/7 clock, as the link in my sig shows. What i have noticed is that the "Clock setting fine delay" returns different values than my stable values, if set using Cmos reloaded. It also returns different values if you input your basic ram settings manually, rather than leaving them on auto. As it happens my workround is the same as yours, as it's the only way to get the "fine delay" settings i need. If we had full control over the "fine delay" settings, i think it would help to solve the problem. Unlike you though, my problem only rears it's head when when using Cmos reloaded, not from a cold boot.

[splmann]

Where can i get a Bioschip for the DFI LP UT P35-T2R in Europe ?

Regards

SPLMANN

[Mav451]

Is anyone noticing significant changes in vdroop at certain Vcore settings?

E.g. I changed vcore from 1.306 (BIOS) to 1.318 (BIOS). It wasn't till I saw SuperPI flake out easily that I noticed that my vcore hadn't increased a bit. I was like, wtF?! The same vcore I had at 1.306, was the same one I was seeing at load for the 1.318 setting. Kinda disappointing, given what I had seen from this board up to this point (basically 0 vdroop).

Is anyone experiencing similar problems? Depending on how I set up my vcore with the "VID special add", it seems to be popping up randomly. E.g. With 1.3V x 102.36%, I'm seeing vdroop yet again. I have a feeling if I find another % to work with, it won't show up.

[MikeMK]

Yep, same thing here as well. I don't think it is the bios revision as such, because it does the same with the 12/24/07. I think i have narrowed the cause down a bit though. Like you i have a good stable 24/7 clock, as the link in my sig shows. What i have noticed is that the "Clock setting fine delay" returns different values than my stable values, if set using Cmos reloaded. It also returns different values if you input your basic ram settings manually, rather than leaving them on auto. As it happens my workround is the same as yours, as it's the only way to get the "fine delay" settings i need. If we had full control over the "fine delay" settings, i think it would help to solve the problem. Unlike you though, my problem only rears it's head when when using Cmos reloaded, not from a cold boot.

Thats very interesting. At least im not the only one! Just a bit frustrating thats all - especially as there are sooo many bios options to set manually - ive tweaked all the sub timings too! I guess im gonna have to live with it for the minuite, or play around with timings? Maybe I'll see if leaving clock setting fine delay on auto helps the problem.

[ixtapalapaquetl]

Its really quite frustrating, and it also makes it hard to push the chip further, cos your not sure if windows is freezing because of a bad overclock or not.

I wish I had your problem!

I can't reboot at all! It doesn't matter whether I'm in XP or Vista, tweaked or default settings, even rebooting from BIOS - they all require a CMOS reset. The rig shuts down and shows "88" on restart. I don't even get to "C1"! I finally found that saving CMOS settings with Mode 1 enabled in BIOS allows me to have one boot up. So I load this saved BIOS, tweak what I want to tweak, make sure I'm in Mode 1, and I get to test it out with one successful boot before having to clear CMOS and repeat. Annoying, but not that big of a deal. I haven't even seriously tried to solve the problem yet.

I wonder if it has anything to do with popping off my IHS...

[mad_skills]

looking good dude! what's your temp?

Tnx dude.
Temps, measured by CoreTemp 0.96, are 34C idle and 58C full load in Orthos though i think that in other circumstances they are even smaller.
Ambiental is around 20ish C, perhaps 22C.
I though of swaping this one for some 45nm since it couldn't do above 3.6GHz but the new bios helped a lot and pulled some more MHz out of this "old" girl.
Also GTL enhancing brought some more stability.
Looking good, tonight i try above 1.5V and targeting 3.9GHz i hope..

[Solarfall]

did this during the week end... i know the super pi isnt very good i was only testing how high i can push the cpu with my new cascade

[Lestat]

took some quick pics instead. Very basic for that run, have tuned memory since then.

But this is exact settings in that run -

thats a sick chip dude.
and its not even 100% your cpu, your mobo doesnt NEED higher NB or PLL or VTT voltages to get those clocks.

you have a very nice marriage of cpu and mobo there!
i'd hold on to that beast.

[Lestat]

hey i wanted to say thanks to MrCape for posting his results.

i been tinkering with my E8400 and my P35 Dark for days having troubles finding its sweet spot.

i just did the EXACT same settings as his pictures posted except for ( GTL is x.67 and vcore is 1.44 actual)

my E8400 is crap compared to many i have seen but its still sitting very comfortably at 4.2ghz using Cape's settings.

i have seen amny threads on the various P35/38 boards all offering a different take on what the voltages should be, and to be honest i never thought capes really low settings coupled with a 500mhz fSB would work but they are, and they are working GREAT!
and mine isnt the T2R board its the T2R/S Dark.

Thanks MrCape for posting those screen shots.

i will prime for about an hour then go in and lower the vcore and see what she does.

i often wondered how higher VTT/PLL/NB/SB voltages effected overclocks and it looks like the higher they are the worse the overclock,, atleast from what i have tested..

maybe some of you gent's might want to try MrCape's settings and see what you get.

[MikeMK]

It looks like enabling EIST solves my boot problem described above. Presumably because vista loads at lower clocks than the overclock? Obviously I cant confirm that, as I cant see what its clocked at. All I know is that it no longer hangs on the loading screen when I do a cold boot. Very good news, although I'd prefer not to be using speedstep really, but its less annoying than having to clear cmos and reset every single bios setting manually every time u switch on the PC! LOL!

[Sparda]

Would you kindly fill the BIOS template for this settings for us pls.

Hey guys,





.

[mrcape]

Thanks MrCape for posting those screen shots.

Hey no problem man. It took a while as it wasn't really the obvious settings for me either. I took a look at what Praz did with gtls at auto and that tripped me out, so I tried similar settings and got a really really low voltage 4ghz with 9x.

But then as I ramped it further up I tried the to switch to 8 and 8.5x because 9x didn't react well to auto and low voltages over 4.1ghz. I found the best clock with vcore under 1.3 and notched everything back down to this setting and that's that.

Glad it works for you too.

[Mav451]

i often wondered how higher VTT/PLL/NB/SB voltages effected overclocks and it looks like the higher they are the worse the overclock,, atleast from what i have tested..

maybe some of you gent's might want to try MrCape's settings and see what you get.

Yeah, I've basically left all of those alone - I'm thinking I could probably drop VTT down to stock as well...but that's for a rainy day to test. I'm still a bit hesitant to mess with GTLs yet.

[Broyler]

did this during the week end... i know the super pi isnt very good i was only testing how high i can push the cpu with my new cascade

Very nice results Look this:
http://www.hwbot.org/result.do?resultId=698678
http://www.hwbot.org/result.do?resultId=698675
it`s my cascade :




and this is max FSB for that CPU in this board :


Now shows-63 stably, at loading(Wprime1024 or SuperPI_32m) Е6850_1.82V(vid)_4860MHz.

[AAdjuster]

I was wondering if anybody has tried this program yet? Used to save cmos reload setting and then share them with others.

It's from the DFI download page.

http://csd.dficlub.org/tikiwiki192/t..._WinReload_Eng

There is also a dos version.

[cantankerous]

Wow, this sure is neat and would be very helpful to those who want to mirror image someones settings without having to manually type them all in.

I could also see this being useful for people who want to backup their own CMOS reloaded settings to be reflashed at a later date since there is only 4 slots available in total which may not be enough in some cases.

EDIT... won't work for me, tells me wrong chipset selected even though I chose the right one. There is only two to choose from total.

[mad_skills]

Seems like a useful little thing.