What's new
  • Please do not post any links until you have 3 posts as they will automatically be rejected to prevent SPAM. Many words are also blocked due to being used in SPAM Messages. Thanks!

DFI LanParty UT X58-T3eH8 LGA 1366 Motherboard Review

Status
Not open for further replies.

3oh6

Well-known member
Joined
Mar 18, 2007
Messages
1,049
Location
Edmonton, AB
System Benchmarks

System Benchmarks



SuperPi Mod v1.5<p style="text-align: justify;"><i>When running the 32M benchmark of SPi, we are calculating Pi to 32 million digits and timing the process. Obviously more CPU power helps in this intense calculation, but the memory sub-system also plays an important role, as does the operating system. SPi 32M has been a favorite amongst benchmarks for these very reasons and is admittedly the favorite benchmark of this reviewer.</i></p><center><img src="http://images.hardwarecanucks.com/image/3oh6/dfi/x58-t3eh8/sys_bench-1.png" alt=""></center><p style="text-align: justify;">After the bandwidth results the most anticipated system bench for us was 32M SuperPi. The reason being is that SuperPi is so dependent on memory bandwidth that it would show whether or not we actually did lose bandwidth or giant latency going from 2x2GB to 3x2GB, and it appears there is definitely something going on when we do. The six second difference isn't huge, and honestly less than we thought, but there is still evidence here that memory is being affected by dropping from triple to dual channel. With such a small difference at these clocks, it is hard to say whether the Everest latency results are responsible, or whether there is simply something involved dealing with the amount of DIMM slots and memory ranks being used. The Sandra memory bandwidth results are clearly removed from acceptability after the 32M results as the time difference would be well over ten seconds with that kind of change, so Everest and ScienceMark - with the edge to ScienceMark - appear to be better bandwidth gauges based on these results.</p>

PCMark Vantage<p style="text-align: justify;"><i>The latest iteration of the popular system benchmark is PCMark Vantage from the Futuremark crew. The PCMark series has always been a great way to either test specific areas of a system or to get a general over view of how your system is performing. For our results, we simply run the basic benchmark suite which involves a wide range of tests on all of the sub-systems of the computer.</i></p><center><img src="http://images.hardwarecanucks.com/image/3oh6/dfi/x58-t3eh8/sys_bench-2.png" alt=""></center><p style="text-align: justify;">The PCMark Vantage default bench results would flip flop back and forth from dual channel to triple channel scoring higher. In the end, the average for the dual channel results marginally outperforms the triple channel setup but realize that this difference easily falls into the margin for discrepancy from one run to the next.</p>

Cinebench R10<p style="text-align: justify;"><i>Another benchmarking community favorite, Cinebench renders an intense 2D scene relying on all the processing power it can. Cinebench R10 is another 64-bit capable application and is likely the most efficient program tested today at utilizing all cores of a processor. We will be running both the single threaded and multi-threaded benches here today.</i></p><center><img src="http://images.hardwarecanucks.com/image/3oh6/dfi/x58-t3eh8/sys_bench-3.png" alt=""></center><p style="text-align: justify;">Like PCMark Vantage, the Cinebench results show dual channel out performing triple channel but the difference can be accounted for by the run-to-run differences seen during testing. Cinebench is primarily a CPU influenced benchmark anyway.</p>

DivX Converter v7.1<p style="text-align: justify;"><i>Next up is a real life benchmark where we simply time a common task done on the computer. Encoding DVDs for viewing on the computer or other devices is an increasingly important task that the personal computer has taken on. We will take a VOB rip of the movie Office Space, and convert it into DivX using the default 720P setting of DivX converter v6.8.</i></p><center><img src="http://images.hardwarecanucks.com/image/3oh6/dfi/x58-t3eh8/sys_bench-4.png" alt=""></center><p style="text-align: justify;">After the SPi 32M and bandwidth/latency benchmark results, we were expecting some real world difference in programs like the DivX during encoding but that clearly was the case. Again, the dual channel setup is neck and neck with the triple channel configuration showing basically no difference. We are really starting to wonder about this whole triple channel marketing blitz for i7. It is really beginning to look like the i7 processor is already saturated with memory bandwidth with the onboard memory controller that triple channel memory is just not necessary in real world applications. Even with the additional memory from the third stick, Vista doesn't seem to be favoring the triple channel setup in any benchmarks thus far.</p>

Lame Front End<p style="text-align: justify;"><i>Un-like the DivX conversion we just looked at, Lame Front End is not multi-threaded and only utilizes a single core of a processor. This will obviously limit performance but we should still recognize significant time savings going from the stock settings to the overclocked results. We will be encoding a WAV rip of the Blackalicious album, Blazing Arrow and converting it to MP3 using the VBR 0 quality preset.</i></p><center><img src="http://images.hardwarecanucks.com/image/3oh6/dfi/x58-t3eh8/sys_bench-5.png" alt=""></center><p style="text-align: justify;">With Lame Front End being a single threaded application we didn't expect much if any difference between the dual and triple channel setups and the that is what we see here.</p>

Photoshop CS4<p style="text-align: justify;"><i>Adobe Photoshop CS4 is fully x64 compliant and ready and able to use every single CPU cycle our processor has available including the implementation of GPU support utilizing the GTX 280 in our test system. It is just a shame it can't fully utilize all 8 threads of the i7 processor yet. We have changed our Photoshop benchmark to more of a standardized test configured by DriverHeaven.net. Their Photoshop benchmark utilizes 15 filters and effects on an uncompressed 109MB .JPG image that will test not only the CPU but also the memory subsystem of our test bench. Each portion of the benchmark is timed and added together for a final time that is compared below.</i></p><center><img src="http://images.hardwarecanucks.com/image/3oh6/dfi/x58-t3eh8/sys_bench-6.png" alt=""></center><p style="text-align: justify;">Expectations were again high for Photoshop to prove us all wrong and show that the triple channel memory still has worth on this setup but as you can see from the graph above, we were disappointed once again. At this point, after the DivX and now the Photoshop results, we are pretty much comfortable stating to perhaps re-think your purchasing decisions for your i7 setup. It may be tough finding i7 rated memory in dual channel configurations but if you are at the point where you are asking yourself whether you need triple or dual channel memory...you might want to think about what programs you are going to be running because the results we have seen before really don't justify the third stick of memory in any way.</p>

WinRAR 3.80<p style="text-align: justify;"><i>We all know what WinRAR is and does. It is a compression and decompression tool that has a built in benchmark, a way to tell just how fast a system can do this programs given task. We simply run the benchmark up to 500MB processed and time how long it takes.</i></p><center><img src="http://images.hardwarecanucks.com/image/3oh6/corsair/tr3x6g1866c7gtf/sys_bench-7.png" alt=""></center><p style="text-align: justify;">We finish up the system benchmarks with another highly influenced benchmark by memory bandwidth and performance and again, there is next to no difference between our overclocked setups.

There you have it, for those asking in forums, and those that didn't even know they were interested. Dual channel memory versus triple channel memory might not be that big of a difference after all. Of course, these conclusions are based on a single setup tested above with a limited number of programs constricted in their use, but there is definitely some questions to be asked after these results. Let's now see if gaming has any impact from the memory differences.</p>
 
Last edited by a moderator:

3oh6

Well-known member
Joined
Mar 18, 2007
Messages
1,049
Location
Edmonton, AB
Gaming Benchmarks

Gaming Benchmarks



Futuremark 3DMark Vantage<p style="text-align: justify;"><i>We have forced ourselves to step up to 3DMark Vantage results for all reviews because the public demands it. 3DMark Vantage is the newest in a long line of 3D benchmarking software from Futuremark and is the most elaborate to date. Featuring multiple presets for various system configurations, Vantage is the culmination of all 3DMarks past relying on system and GPU power for its results. We will stick to the Performance preset as it seems to be the most popular at this point in time.</i></p><center><img src="http://images.hardwarecanucks.com/image/3oh6/dfi/x58-t3eh8/3d_bench-1.png" alt=""></center><p style="text-align: justify;">We get a bit of a mixed bag of results from these two iterations of 3DMark. In 06 there is a definite drop in score going from triple channel to dual channel, but in Vantage on the Performance preset, there is no difference at all. We weren't expecting any loss in performance in either benchmark when removing a stick of memory so the 06 results caught us off guard, but in all three benchmark runs we did, the 600 point difference between the two setups was present.</p>

Crysis - Sphere benchmark<p style="text-align: justify;"><i>We all know what Crysis is and how much it beats up systems but we wanted to add it to the gaming benchmarks to see how system changes can improve performance on a mid-level system. Detail levels are all set to Very High with the resolution at 1680x1050 with 4xAA. We ran the benchmarks with a demo of the Sphere level in DX9 and 64-bit. The game looks great with this setup and plays just well enough to keep us happy.</i></p><center><img src="http://images.hardwarecanucks.com/image/3oh6/dfi/x58-t3eh8/3d_bench-2.png" alt=""></center><p style="text-align: justify;">Moving on to Crysis we see that the differences we just saw in 3DMark 06 do not translate in any way to in game benching of Crysis. In fact, things couldn't be much more even across the board again portraying just how little memory affects this game. The bottlenecks in Crysis happen much further up the line than memory with settings this high.</p>

FarCry 2<p style="text-align: justify;"><i>Another new fall release of this past silly season Far Cry 2 has some beautiful scenery but does lack that buttery smooth game play in places. A lot of moaning and groaning has occurred with Far Cry 2 but acceptable frame rates are much easier to achieve than Crysis and the game play is plenty smooth enough to enjoy. We were really able to crank up the settings with this benchmark on this setup.</i></p><center><img src="http://images.hardwarecanucks.com/image/3oh6/dfi/x58-t3eh8/3d_bench-3.png" alt=""></center><p style="text-align: justify;">The Far Cry 2 time demo shows about the same results as Crysis. There appears to be a slight drop in maximum frame rates achieved from the stock results to the other two sets of overclocked numbers, but the minimum and average frame rates are level down the line. Perhaps this isn't what anyone wants to hear, but with detail settings turned up high at 1680x1050 and a GTX 295 at stock clocks, the system plays a very small role in most games and certainly the ones we have tested here. With Core i7, the setup is just so powerful that even a hefty overclock really adds little to no performance. Even dropping a single stick of memory leaving us with 2x2GB shows little to no performance decrease. We aren't making this up, the results are hard to misconstrue. Obviously different setups will show different gains and losses, but this setup shows really no setback to dropping a stick of memory. Perhaps in actual gaming there is, but if the benchmarks are any indicator, there won't be a lick of difference in frame rates.</p>

Left 4 Dead<p style="text-align: justify;"><i>The newest game in our testing sweet, Left 4 Dead was just added after we were asked to include a Source powered game in our memory benchmarks. Being based on the Source engine, there is definitely a chance that system performance will heavily influence the results. We used FRAPs to measure frame per second on a custom time demo of the rooftop level.</i></p><center><img src="http://images.hardwarecanucks.com/image/3oh6/dfi/x58-t3eh8/3d_bench-4.png" alt=""></center><p style="text-align: justify;">The last of our game testing comes from a Source engine game, Left 4 Dead. The latest in a history of efficient games that play well on most any system, L4D is a high energy shooter and frame rate drops aren't something you can deal with in this game. As we can see from the results, no matter how we set this system up, frame rates with these components are not a problem. Like the other games we get pretty steady performance from the three configurations, but there is a little more variance than we have seen up until now. Again, the Source engine does rely on the system a bit more than most games so that would be the explanation for that, but the differences are definitely not significant in any way. Further evidence that with a setup like this, overclocking aide for benchmarking is all but pointless.</p>
 
Last edited by a moderator:

3oh6

Well-known member
Joined
Mar 18, 2007
Messages
1,049
Location
Edmonton, AB
Voltage Regulation

Voltage Regulation

<p style="text-align: justify;">What you set in the BIOS is definitely the voltage being supplied in reality...correct? Well, that is not always the case. In fact, it is rarely the case. Then there is the discussion about whether or not what the software voltage readings are providing are accurate. The standard way to test for actual supplied voltage is to measure directly from the motherboard with a digital multi-meter (DMM). Recent high end motherboards have made this a dead simple task by providing onboard, easy to reach, read points for various voltages. ASUS started the trend with the Rampage Extreme II and the EVGA X58-SLI also offered a limited selection of voltage read points. Not to be outdone, DFI has provided a class leading eight voltage read points down in south bridge corner.</p><center>
voltage-1.jpg
<p style="text-align: justify;">These read pads are quite easy to access for those working with the motherboard on an open bench setup. In our particular setup here, they are in the ideal spot. With the EVGA X58-SLI we had to solder leads to their read points just to access them but with the DFI, that won't be necessary. We would still like to see test leads that can connect to these points to provide continuous reading like the Rampage Extreme II offers, but we certainly can't complain with the sheer number of voltages DFI has routed to this location for easy access. Before we take a look at how well voltage is regulated on the LanParty X58-T3eH8, we will use the onboard read points to determine exactly how accurate the BIOS settings for voltages are. Below is a chart of what we set in the BIOS, what is read in Windows by software at idle/load, as well as what the DMM picks up from the read points on the board at both idle/load. For the DMM, we will be using our trusty calibrated UEI DM393 True RMS multi-meter that provides three digits after the decimal for accuracy. Below are the results of this testing with our overall overclocked settings (w/vDROOP disabled) we have already used for benching. Load will be taken after 10 minutes of OCCT CPU test load.</p><center><table border="0" bgcolor="#666666" cellpadding="5" cellspacing="1" width="697"><tr><td align="center" bgcolor="#cc9999" width="99px"></td><td align="center" bgcolor="#cc9999" width="99px"><b>BIOS Set</b></td><td align="center" bgcolor="#cc9999" width="99px"><b>BIOS Report</b></td><td align="center" bgcolor="#cc9999" width="99px"><b>Smart Guardian<br />Idle</b></td><td align="center" bgcolor="#cc9999" width="99px"><b>Smart Guardian<br />Load</b></td><td align="center" bgcolor="#cc9999" width="99px"><b>DMM<br />Idle</b></td><td align="center" bgcolor="#cc9999" width="99px"><b>DMM<br />Load</b></td></tr><tr><td align="center" bgcolor="#ececec" width="99px">CPU VID</td><td align="center" bgcolor="#ececec" width="99px">1.375v</td><td align="center" bgcolor="#ececec" width="99px">1.38v</td><td align="center" bgcolor="#ececec" width="99px">1.38v</td><td align="center" bgcolor="#ececec" width="99px">1.39v</td><td align="center" bgcolor="#ececec" width="99px">1.381</td><td align="center" bgcolor="#ececec" width="99px">1.388v</td></tr><tr><td align="center" bgcolor="#ececec" width="99px">DRAM Bus</td><td align="center" bgcolor="#ececec" width="99px">1.695v</td><td align="center" bgcolor="#ececec" width="99px">v</td><td align="center" bgcolor="#ececec" width="99px">1.67v</td><td align="center" bgcolor="#ececec" width="99px">1.67v</td><td align="center" bgcolor="#ececec" width="99px">1.698v</td><td align="center" bgcolor="#ececec" width="99px">1.698v</td></tr><tr><td align="center" bgcolor="#ececec" width="99px">CPU VTT</td><td align="center" bgcolor="#ececec" width="99px">1.40v</td><td align="center" bgcolor="#ececec" width="99px">1.39v</td><td align="center" bgcolor="#ececec" width="99px">1.39v</td><td align="center" bgcolor="#ececec" width="99px">1.4v</td><td align="center" bgcolor="#ececec" width="99px">1.390v</td><td align="center" bgcolor="#ececec" width="99px">1.417v</td></tr><tr><td align="center" bgcolor="#ececec" width="99px">CPU PLL</td><td align="center" bgcolor="#ececec" width="99px">1.80v</td><td align="center" bgcolor="#ececec" width="99px">x</td><td align="center" bgcolor="#ececec" width="99px">x</td><td align="center" bgcolor="#ececec" width="99px">x</td><td align="center" bgcolor="#ececec" width="99px">1.803v</td><td align="center" bgcolor="#ececec" width="99px">1.803v</td></tr><tr><td align="center" bgcolor="#ececec" width="99px">IOH/ICH</td><td align="center" bgcolor="#ececec" width="99px">1.11v</td><td align="center" bgcolor="#ececec" width="99px">1.10v</td><td align="center" bgcolor="#ececec" width="99px">1.1v</td><td align="center" bgcolor="#ececec" width="99px">1.1v</td><td align="center" bgcolor="#ececec" width="99px">1.112v</td><td align="center" bgcolor="#ececec" width="99px">1.113v</td></tr><tr><td align="center" bgcolor="#ececec" width="99px">IOH Analog</td><td align="center" bgcolor="#ececec" width="99px">1.10v</td><td align="center" bgcolor="#ececec" width="99px">x</td><td align="center" bgcolor="#ececec" width="99px">x</td><td align="center" bgcolor="#ececec" width="99px">x</td><td align="center" bgcolor="#ececec" width="99px">1.111v</td><td align="center" bgcolor="#ececec" width="99px">1.111v</td></tr><tr><td align="center" bgcolor="#ececec" width="99px">ICH 1.5</td><td align="center" bgcolor="#ececec" width="99px">1.5v</td><td align="center" bgcolor="#ececec" width="99px">x</td><td align="center" bgcolor="#ececec" width="99px">x</td><td align="center" bgcolor="#ececec" width="99px">x</td><td align="center" bgcolor="#ececec" width="99px">1.502</td><td align="center" bgcolor="#ececec" width="99px">1.502</td></tr><tr><td align="center" bgcolor="#ececec" width="99px">ICH 1.05V</td><td align="center" bgcolor="#ececec" width="99px">1.05v</td><td align="center" bgcolor="#ececec" width="99px">x</td><td align="center" bgcolor="#ececec" width="99px">x</td><td align="center" bgcolor="#ececec" width="99px">x</td><td align="center" bgcolor="#ececec" width="99px">1.059v</td><td align="center" bgcolor="#ececec" width="99px">1.059v</td></tr></table></center><p style="text-align: justify;">It is quite apparent that we have vDROOP disabled in the BIOS as vCORE not only didn't drop, it actually raised the slightest bit under load. The actual voltage really isn't that far off what the vCORE was set to in the BIOS so overall we are quite pleased. With vDROOP enabled, there is about a 0.04v drop from idle to load with the same setup as used above. The next very impressive voltage tested is vDIMM. Here we see a rock solid vDIMM output with the exception that the software reading is just slightly low. What is actually being fed to the memory, however, is as close as it gets to what we set in the BIOS. After suffering through the EVGA X58-SLI vDIMM giant droop, this DFI LanParty X58-T3eH8 certainly has us pleased with the voltage regulation. This will be confirmed shortly with a look at the OCCT chart. The rest of the voltages are pretty much bang on to what is set in the BIOS with minor fluxuations to VTT. At idle VTT is a hair below what we set in the BIOS, and under load it is a hair high. The movement is in quite an acceptable range though. Before we look at the voltage charts for vCORE, vDIMM, VTT, and the IOH/ICH (north bridge), let's have a look at the effects of enabling vDROOP VS disabling it.</p><center><table cellpadding="10px" cellspacing="0"><tr><td width="50%"><b><center>vDROOP Chart from OCCT - vDROOP Enabled</b>
voltage-2.png
</center></td><td width="50%"><b><center>vDROOP Chart from OCCT - vDROOP Disabled</b>
voltage-4.png
</center></td></tr></table></center><p style="text-align: justify;">I think the line in the images tells the story. Without vDROOP disabled, our configuration shows heavy droop from idle to load. Keep in mind this is the software reading but it still coincides with the DMM readings we were getting at the same time. With vDROOP enabled in the BIOS, we get a slight rise in vCORE in our DMM testing but from idle to load in OCCT we see a completely steady line. The two schools of thought on vDROOP are all over the internet. Some say it is necessary and should be enabled, while others feel vDROOP should be eliminated so that you have lower idle voltages. However you look at it, no conclusive evidence has been linked to enabling or disabling vDROOP. There hasn't been an apparent rash of damaged processors since vDROOP elimination options started showing up in BIOSs, and there has been no public outcry from Intel asking MB manufacturers to remove the option to allow vDROOP to happen. Either way, the option on the X58-T3eH8 works, and works well. Use it if you want, or don't if you choose not to. Here now are the rest of the voltage charts from OCCT that were captured during testing for the above chart under the same conditions.</p><center>
voltage-5.png
voltage-6.png
voltage-7.png
</center><p style="text-align: justify;">As we mentioned above, vDIMM is rock solid, all the way across. Even with the DMM and its four digit accuracy, it very rarely flickered off of 1.698v at any point. VTT shows a little variation, as we expected after the chart of voltages from idle to load showed above. There is nothing of too much concern here but keep in mind, VTT does rise slightly at these settings under load. On the whole, the DFI X58-T3eH8 has really excellent voltage regulation, and where it counts the most. Memory clocking should be quite consistent on this motherboard as we have found out and whether you want or don't want vDROOP, the DFI has you covered.</p>
 
Last edited by a moderator:

3oh6

Well-known member
Joined
Mar 18, 2007
Messages
1,049
Location
Edmonton, AB
Heat & Acoustical Testing

Heat & Acoustical Testing

<p style="text-align: justify;">With no fans active on the DFI LanParty X58-T3eH8, there obviously isn't going to be any acoustic testing. What we will look at, however, is the much advertised Flame Freezer heat sink attachment that is designed to help cool the passive heat sink - in particular - the digital PWM. We will simply be running our maximum overclock again with OCCT as the method for loading the system. What we want to test for is the difference between our test setup with and without the Flame Freezer attachment, and then what happens when we remove all but the fan attached to the Thermalright Ultra-120 eXtreme cooling the CPU. Let's look at some photos of the setup first.</p><center>
heat-1.jpg
heat-2.jpg
</center><p style="text-align: justify;">The photo above on the left is where we applied a small amount of thermal paste on the heat sink fins. We then mounted the Flame Freezer attachment and in the photo on the right we are showing what the attachment looks like after being mounted. Clearly there is some decent contact but we are still a bit skeptical that the cooling fins interfacing with the heat pipe of the Flame Freezer attachment with such a small surface area will have any impact on PWM temperatures.</p><center>
heat-3.jpg
heat-4.jpg
</center><p style="text-align: justify;">These next two photos outline the second and third setups in the graph we are about to look at. On the left is the single fan setup and the right, our normal three fan setup. The TRUE has two 120mm Ultra Kaze's in a push/pull configuration with a third acting the role as memory cooler. The third fan also directs a lot of air down toward the NB and PWM heat sink. We feel removing this fan will definitely impact the systems temperatures.</p><center>
heat-5.jpg
heat-6.jpg
</center><p style="text-align: justify;">These last two photos are just some more glamour shots of the setup during testing. Let's now go over the results of the three setups that include the three fan setup with no Flame Freezer attachment, a three fan setup with the attachment, and then a single fan setup again; with the Flame Freezer.</p><center>
heat-9.png
</center><p style="text-align: justify;">We were expecting some impact from the lack of fans in the third setup depicted with the blue line in the graph, but not that large of a difference. Both three fan setups hover just above and just below 70C while the single fan setup sky rockets to over 90C for the majority of the 20 minute stress test. The difference between the three fan setups with and without the Flame Freezer is minimal but there definitely seems to be a 2-3C drop with the Flame Freezer attached. The fact that we see any sort of distinct performance difference is a bit of a surprise but it does appear the Flame Freezer helps the PWM temps out marginally, nothing to get excited about but enough of a difference to make it worth attaching to the motherboard.

Our biggest concern with this testing though is the result of a single fan setup. Clearly the silent heat sink setup of the DFI X58-T3eH8 can't cope with a highly overclocked system without a bit of help. If you are mounting this system in a case for daily use, you are definitely going to want to cater your fan setup to provide the motherboard heat sink the cooling it needs. The PWM may be designed to run that hot, but we certainly don't like seeing it run that hot when a little bit of air can help out drastically.</p>
 
Last edited by a moderator:

3oh6

Well-known member
Joined
Mar 18, 2007
Messages
1,049
Location
Edmonton, AB
Conclusion

Conclusion

<p style="text-align: justify;">The enthusiast computer user is definitely hard to please. The competition in the market is fierce and this has led to manufacturers really having to step up their game in order to compete. The introduction of the Intel Core i7 has created a motherboard feeding frenzy. We literally can't keep up with the demand of manufacturers for reviews. What this has done is made it difficult for any single manufacturer to stand out. The features available on these high end X58 based motherboards is tremendous and every time a board is released, another feature is added. DFI has been at the top of the enthusiast level of motherboards for a long time. The LanParty name is synonymous with enthusiasts for being the must have overclocking motherboard. The DFI LanParty UT X58-T3eH8 that we have looked at today is definitely a true LanParty board providing a feature set that rivals that of any other i7 motherboard available right now.

The color scheme is of typical DFI LanParty fashion offering UV reactive components on the motherboard for the case modders that want to show the motherboard off. Of course colors are a personal choice but the point is that DFI has made an attempt to make their board stand out. Features like the split 16X PCI-E slot layout, onboard voltage read points, onboard power/reset/CMOS clear buttons, and LED display all cater to the enthusiast. Overclockers in particular will enjoy these and many more features offered by the DFI X58-T3eH8. The Genie BIOS and its features like the CMOS Reloaded are also key factors for DFI LanParty users as they have become use to the luxury these features offer, but this is also where we were a little let down.</p><center>
conclusion-1.jpg
</center><p style="text-align: justify;">The Genie BIOS on the X58-T3eH8 is more than capable in providing all but the most advanced overclockers all they need. Exquisite voltage selection, stability, comfortable layout, and all the standard options are present. But the Genie BIOS on previous LanParty boards has always catered to memory enthusiasts in particular with usually more memory options than most other motherboards combined. That is not the case at all with the X58-T3eH8. Our other X58 motherboards we have tested offer more in the way of memory tweaking than this LanParty board does. Of course, that might not even factor in for most users. In fact, the somewhat simplified BIOS on this LanParty motherboard actually facilitates an easier and better experience for the average overclocker. Many of us familiar with DFI motherboards have been quite impressed with just how easy this X58-T3eH8 has been to overclock. That is definitely a plus for the majority of users, especially those that feel the LanParty name may intimidate them, this board won't.

Overclocking memory, despite the lack of timing options, is still very capable taking our Dominator-GT modules to incredible clocks. So good in fact that we choose to use this motherboard instead of the EVGA X58-SLI for the Dominator-GT review. Our CPU overclocks were also as good as on any other motherboard and allowed for some impressive overclocks with basic air cooling and 100% stability with the solid digital PWM. Bios updates seem to be coming at a steady pace from DFI and each one seems to slightly improve on a number of items so that is certainly encouraging for down the road. Overall, we are quite pleased with the DFI LanParty UT X58-T3eH8 and proudly stamp it with the Hardware Canucks Dam Good award. From overclocking enthusiasts to average users looking to run a solid Core i7 system, the DFI LanParty UT X58-T3eH8 is definitely a solid choice, and one that will stand out from the crowd.</p>

<b>Pros:</b>
  • Typical DFI quality from build to BIOS
  • All the onboard features enthusiast overclockers are looking for in a motherboard
  • Great overclocks on both CPU and memory, with very little effort and no frustration
  • A color scheme that makes the board stand out from the crowd in the light or dark
  • Among the best layouts, perhaps even better than the EVGA X58-SLI

<b>Cons:</b>
  • The memory BIOS options were not up to the LanParty standard in our opinion
  • The fan less MB cooling showed signs of needing some help from case cooling in our thermal testing
  • As much a positive as the color scheme is, some people just aren't going to like yellow and green


<center><table><tr><td><img src="http://images.hardwarecanucks.com/image/3oh6/dam_good.jpg" alt=" " /></td></tr></table></center>

<center><b><i>We would like to thank all of the folks over at DFI for the opportunity to review the DFI LanParty UT X58-T3eH8.</i></b>

If you have any question or comments, please feel free to post in the comment thread on our forums </center>
 
Last edited by a moderator:
Status
Not open for further replies.

Latest posts

Top