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

[soundx98]

Ix and Rog - You are not alone.

Initially I thought my Zalman 9700 just wasn't cutting it or I had a bad mount.
I've remounted 8 times using AS5, Ceramique, and AIT Cool Silver (Including reseating the processor itself).
The temps with the different TIMs all appear almost identical as I figured they would.

with 1.424v at 4300MHz idle remains at 50C for Core 1 and 44 for Core 2.
Load temps using latest OCCT or Prime96 v246 hit 78C on Core 1 and 72C on Core 2.
CoreTemp 0.96.1 is showing vid of 1.1125
I am glad that has not changed as it would seem to mean either the processor is "changing" or CoreTemp has an issue.
EDIT: Just read C-N's post above and I'll check to see if my vid is changing as I overclock/change voltage.
Course, now I am worried that my VID hasn't been changing

It's passed 4200MHz for an 8 hour Prime and OCCT at 1.4v.
No issues with stability on normal apps at 4300 but no joy passing Prime/OCCT (no issues with SuperPi either).
Core 1 (the hot one) fails.
(Everest produces the same temp readings of course)
From what I read I was hoping for mid 60s under load on this Intel chip.

I know the GTLs can make a huge difference and I appreciate all the tips on GTLs.
Hopefully Once I get them dialed in things will make more sense.
I need to do some further analysis and experimentation but it seems like my setup likes the CPU GTLs closer to 60.
I can't really speak to NB GTLs at this point but the 60 to 67 that Praz mentioned is the ballpark I have been using.

Really don't have a clue on my Memory setting on this week old build so I set to 2.1v and left most settings at default/auto.
So perhaps it's my mem settings that are causing failure.

I do feel the board is great so far.
An LT at stock other than the Enzotech low profile passive SB cooler on it.
no issues at all so far.
As I said earlier I couldn't even enter the bios at 1st as I was on the 10/05 Bios.
Once I flashed to the 109 with the Tmod/Loggan CD it was a breeze.

Be great if it was a glitch in Core Temp that causes these high temps but once I hit 1.4v my processor gets real hot very fast.
(not exactly cool at 1.35v either)

I've been watching CoreTemp during a 32Mb run of SuperPi and really amazed at how much Core 1 fluctuates.
Between 58 and 70 while Core 2 moves between 50 and 56.

Since the rig is still out of the case I may try a different orientation of the Zalman 9700 to see if it's a seating issue or something wonky with the IHS.

[Praz]

These 8400 processors have issues. Right now the best a person can do is go by instinct when determining temperatures.

Carl, remember the GTL values you set are relative not absolute. The values represent no actual percentage or voltage. They are a number linked to a voltage that changes as VTT is changed.

[soundx98]

This is the temp log from the 32M Super Pi run.
I adjusted the GTL on Core 1 to 59, GTL Core 2 61, and NB at 66
(actually I reversed the GTL settings for this run between Core 1 & 2.)
But it shows the fluctuation on Core #1 as well as it running hotter than Core #2

http://premium1.uploadit.org/soundx9...2m-superpi.txt

[soundx98]

These 8400 processors have issues. Right now the best a person can do is go by instinct when determining temperatures.

LOL, I shoulda smelled that one coming as well
I'm assuming you mean temperature issues?

Carl, remember the GTL values you set are relative not absolute. The values represent no actual percentage or voltage. They are a number linked to a voltage that changes as VTT is changed.

Thanks for the help John.
Yes I do understand that they are not an absolute but relative.
(why should it be easy)
I'll continue "tinkering" and hope that at least I get a better "grip" on understanding all the relationships.

Do I need to type something special under preferences for Prime (987654321 or something)?
I set it up as "custom", 2 threads with 800MB each, 8 Minimum FFT, 4096 Maximum, for 15 minutes to run each FFT.
Just trying to establish a consistent test method.

And I am having a lot of fun with this

[karateo]

soundx98 how much VTT do you need for 4Ghz?
The stock is 1.1 (according to DFI's beta bios) so 1.3 isn't it too much?

I use VTT 1.3-1.2v for 4000-4050 and <1.35vcore but orthos fails immediately.
However, I can play FSX for half an hour (haven't tried more) and serf the net without problems



EDIT:
I wonder what is the methodology to overclock on a DFI mobo.
I mean the basics. Start increasing fsb until unstable and then add vcore.
But then what? What about Special Vid and VTT?
Is there any guide out there? I came from a P5B dlx which was REALLY simple compared to this baby :p

I just need to point me to the right direction

[soundx98]

Please remember I am a n00b that a week ago was still running his NF4 939.

I am afraid, as Praz said, that I am using "brute force" instead of "finesse".
Really don't remember the 4G settings but I'll try and test and report back.

With Vcore at 1.4v x0.023%. Been using 1.36v CPU VTT at 4th 200-4300 (not sure why, may have just seen that number somewhere on the net, figured I'd need to jack it up).
I know I left it at default at 3.5G Prime run and I don't have a clue where it was for 4 or 4.2.

But your point is well taken.
I need to do a systematic OC procedure and then make sure my testing procedures are correct.
Being an oldfaht I know I should have more patience, but I guess I got a little excited once I saw 4G running

[mrcape]

These 8400 processors have issues.

Can you elaborate on this statement? I'm wondering what specifically the issues are.

Is there any data that it's not the chipset or the bios having issues with 45nm? Not speaking only about reading temps here.

[karateo]

Being an oldfaht I know I should have more patience, but I guess I got a little excited once I saw 4G running

exactly!
I set bios to 450x9 and then I tried to adjust volts which is completely wrong

[Praz]

Can you elaborate on this statement? I'm wondering what specifically the issues are.

Is there any data that it's not the chipset or the bios having issues with 45nm? Not speaking only about reading temps here.

No, really can't. There no sense stating the "what" without being able to provide the how or why. The same things have been seen with the 9650 and the limited number of 8500 processors that are out. For most there's nothing ground shaking here but needs further looking into anyway. Right now it's not even known what the temperature reporting issue is. Incorrectly calibrated or broken DTS or faulty IHS contact? If I can ever get through these boards I'm working with I may de-lid an 8400 and see if there's any difference with the reported temps.

I am afraid, as Praz said, that I am using "brute force" instead of "finesse".

Once you find some 24/7 stable settings then go back and fine tune. The "brute force" first approach is the fastest especially until it's known what the board and components prefer.

[Roger_D25]

Guys, thank you very much for being willing to extend the conversation about the E8400 chips on this board, much apprecaited! It was great to read your posts soundx98, at least now I know I'm not the only one having these "issues". I'm totally bummed because today is my longest day at school (8hrs of actual in-class time, man graduate school can really suck sometimes)! By the way soundx98, your not the only old fart. I was in my mid 20's before even starting college!

Anway I'll be looking forward to reading through the thread when I get home tonight from school. Plus I will do much testing tomorrow (got the day off from work and school) and will post my results ASAP!

[soundx98]

Geez Rog, Grad School?
That's like kindergarden without the naps and cookies isn't it.
I thought all one did was ogle the co-eds and sleep late in Grad School.

Seriously, I think there are a lot of us wondering about the temps from what I have read around the web.

If anyone wants to come up with a suggested methodology for testing this board and 45nm (E8400)just let me know and I'll try and duplicate it as well.
A template has already been posted.

Praz and others, am I setting up Prime 95 correctly?
And incidentally, the latest v256 and latest OCCT do seem to get my CPU "hotter" that older versions as I remember.

Since it's the **Official DFI LanParty UT P35-T2R Review/Overclock/Guide Thread** I can say I haven't had any issues with the board.
Very impressive so far.

[Brother Esau]

Please remember I am a n00b that a week ago was still running his NF4 939.

I am afraid, as Praz said, that I am using "brute force" instead of "finesse".
Really don't remember the 4G settings but I'll try and test and report back.

With Vcore at 1.4v x0.023%. Been using 1.36v CPU VTT at 4th 200-4300 (not sure why, may have just seen that number somewhere on the net, figured I'd need to jack it up).
I know I left it at default at 3.5G Prime run and I don't have a clue where it was for 4 or 4.2.

But your point is well taken.
I need to do a systematic OC procedure and then make sure my testing procedures are correct.
Being an oldfaht I know I should have more patience, but I guess I got a little excited once I saw 4G running

Well me knows you aint a noob for sure Are you having fun with the New DFI Expert in Intel clothing Carl? Might I suggest a Tuniq Tower 120 as it works out quite well in that board with no clearance issues and it Kept my Q6600 @ 3.6ghz around 61c full swing Prime95

[RGone]

google search temp + issues + E8400 47,100 hits. Seems every brand has problems. The Lenovo thing is what caught me eye and made me link to get away from so much speculation that has no real answers with the newer stuffs.

anna99, the temp probs in the E8400 are stuffed. The Coolest (the guy who makes coretemp) reports that according to Intels spec, his program is reading the temps correctly. In other words, coretemp is reading what the cpu is telling it. Basically the blame gose to intel because they stuffed up and now the temp probes don't work. Case and point, my E8400. According to coretemp, one core is locked at 43c, the other at 51c. They will not read any lower than this, ever... Once the temp moves above these values its starts to rise, but other report completely frozen probs (sometimes just reading 7c!). My motherboard reports 34c on the cpu all the time, i have never seen it move off this value (this may be fixed in future bios though).

Lenovo, the major laptop vendor, has sent back all thier E8xxx cpus because of "issues with temperature sensors" (i saw this in another thread here, so i have no referance, srry).

So basically we are stuck. I personaly choose to beleve my reported temps(when they move), but there is no eveidance pointing to the fact i should. In short, you are not alone. Every single E8x00 seems to have these issues. I think it requires a new stepping to fix myself, so i don't think it will ever change. Lets hope i'm wrong.

[zfactor]

wow great info rgone..this doesnt seem good

[RGone]

Another google search and what the user did about his temps on E8400 >>> It seems that many, if not most Wolfdales have flawed core sensor diodes which give false temp. readings, especially at idle and low temps. Many E8400 have "stuck" cores which show much higher idle temps in one core than the other core. That stuck core temp reading only becomes "unstuck" when temps exceed that frozen mark.

Some Wolfdale's are also giving false core LOAD temperatures, which is troubling, especially if you have a temp controlled fan setup. These processors are flawed and probably should be returned (unless it's a great o/c'er). The cpus which have only the "idle temp bug" are probably not warranted a replacement. E8400 owners have been told by some retailers to ignore their core temperature readings as only the cpu temps are accurate.

I don't believe this is a motherboard issue and can be be fixed by an bios update. CoreTemp reads the temp readings right from these core diodes, regardless of the bios.

My first E8400 had 17/34C core temps. Under load, the lower core would increase in temp to match the other core, then they would both go up in unison from there. But what were the real temp readings? I really doubt that one core was 17C (7C below room temp?)

I took that cpu back to my local retailer and he exchanged it without question...with another cpu from the exact same batch! The good news is my new cpu reads 38/36C at idle (4.0GHz) with 47/52C load temps, which I can only assume are more accurate. Edited: 01/29/2008

No board change, no bios change just cpu change. Some QX9650 have had same type issue. Ace-R-Rue had one of those high-dollar problem ones with temp issues. But for that money they likey may have less problems.

I ordered E8400 mini-thing since E8500s are vaporware where I order from and will see if I am "lucky" or have shett for luck as is sometimes the case.

[kitfit1]

Please remember I am a n00b that a week ago was still running his NF4 939.

Don't look like much of "nOOb" to me Carl Me thinks a nOOb would be well happy with a clock like yours I think we can now chuck out all nOObish talk in regards of movement to the "Darkside"

[MikeMK]

Case and point, my E8400. According to coretemp, one core is locked at 43c, the other at 51c. They will not read any lower than this, ever... Once the temp moves above these values its starts to rise, but other report completely frozen probs (sometimes just reading 7c!).

Rgone - I can confirm its not just Wolfdale's. My Yorkie QX9650 has the exact same problem. Two of my cores are locked at 37 degrees (the other 2 idle at around 30 degrees), until the temp rises above that. At first I thought I had a bad mount on my waterblock, but after 3 remounts I gave up. Then when I primed I realised that after the temps got past 37 degrees, they came in line with the other 2 cores.
Bit of a pain, but at least they arent locked as high as yours are!

[mrcape]

I didn't notice funny temps, or temps being stuck at stock. It wasn't until after I over clocked and tested the chip that one core was getting flaky. Could the current chipset / board / bios' be causing damage sensors on a new, more fragile chip?

Aside from temp sensors and readings, what are the chances that boards designed for 65nm cpus are delivering voltage in a dangerous (to 45nm) manner? Meaning with over clocked settings.

Now don't get me wrong here, I'm absolutely in love with the board, I just want to explore the possibility that currently offered boards, chipsets or bios' are out of sync with these new chips and something besides the chip itself is causing problems. Maybe this post should be in another thread?

It would be nice if someone with access to several P35, X38, X48 boards from different manufacturers could test the same chip in all of them and share the data. And if there's a P45 reference board anywhere how is that doing with these?

[Praz]

This has absolutely nothing to do at the board level. Voltages from all power planes are at Intel specs. The issues are inherent to the 45nm family of processors.

[emoners]

This has absolutely nothing to do at the board level. Voltages from all power planes are at Intel specs. The issues are inherent to the 45nm family of processors.

That's why I LOVE this board!

[turtletrax]

My proc has the "stuck" temps, but it seems that they are not rediculously high, and at load are only off by about 3-4C.

I will keep my eye on things over the next little while and perhaps RMA it when they get this all sorted. Still, 4.05Ghz at 1.25V keeps me happy

[thesaucier]

Seems I cant get this to boot if I pass 400 fsb no matter what. Im I missing a setting here?

[mrcape]

Just put a brand new e8400 - Q745A576 into this board. The temps look low now, just like the last one, and they change in sync as I load the cpu. I'll be interested to see if that changes over time.

Core temp at stock settings -

[soundx98]

Is your sig correct?
This is an Intel thread.
If this is a DFI P35T2R you may need to flash to a later bios if you are using an E84/500.
A lot of assumptions here but we really need to know what we are dealing with in terms of components./

[thesaucier]

Is your sig correct?
This is an Intel thread.
If this is a DFI P35T2R you may need to flash to a later bios if you are using an E84/500.
A lot of assumptions here but we really need to know what we are dealing with in terms of components./

My sig is good now.