Reviews http://www.maximumpc.com/taxonomy/term/40/ en AMD Radeon R9 290 Benchmarks http://www.maximumpc.com/amd_radeon_r9_290_benchmarks <!--paging_filter--><h3>AMD's Radeon R9 290: A Mid-range Monster</h3> <p><img src="http://www.maximumpc.com/files/u302/amdrad_r9_290_flatangle_rgb_24in_small.png" alt="Radeon R9 290" title="Radeon R9 290" width="250" height="167" style="float: right;" />Today <a href="http://www.maximumpc.com/tags/amd">AMD</a> is launching the <strong>Radeon R9 290</strong>, which is the second card in its all-new Hawaii series of GPUs designed to take on <a href="http://www.maximumpc.com/tags/nvidia">Nvidia's</a> GK110-based super GPUs. This particular card is extremely similar to its big brother, the <a href="http://www.maximumpc.com/amd_radeon_r9_290x_benchmarks">R9 290X</a>, but has slightly lower clock speeds and fewer stream processors, allowing it to come in at a slightly lower price point of <strong>$400</strong>. Though it was originally designed to take on the formerly $400 GTX 770, AMD is now positioning it to compete with the GTX 780 due to Nvidia's recent price drops on both cards to $500 and $329, respectively. Read on to see how it handles the heat, both literally and figuratively.</p> <h3>Little Hawaii</h3> <p>As the second, lower-priced Hawaii board you might assume this card has been neutered more than a made-for-TV version of The Big Lebowski, but you would be wrong. Thankfully, AMD has left almost everything from the R9 290X intact, choosing to only reduce its texture units from 176 to 160, its Stream Processors from 2,816 to 2,560, and its maximum clock speed from 1,000MHz to 947MHz. It still has the same 4GB of memory, the same 512-bit memory bus, and is otherwise the exact same GPU. It also has the same PowerTune hardware and software that lets you dictate maximum fan speeds and core temps. Before we jump in, let's take a look at the specs for the Hawaii cards along with their Nvidia counterparts:</p> <p>&nbsp;</p> <p style="text-align: center;"><img src="/files/u302/specs_take_2_0.jpg" alt="Radeon Specs" title="Radeon Specs" width="462" height="472" /></p> <p style="text-align: center;"><strong>*We are putting an asterick next to the AMD cards' TDP because it's not a quoted spec but "standard board power."</strong></p> <p style="text-align: left;">As the spec chart shows, this card is almost exactly the same as the R9 290X, just like the <a href="http://www.maximumpc.com/article/news/geforce_gtx_780_benchmarks">GTX 780</a> and <a href="http://www.maximumpc.com/article/features/nvidia_geforce_titan_%E2%80%93_benchmarks2013">GTX Titan</a> in that you have two cards with the same die but one is a bit less powerful. The two cards are the same physical size at 11 inches, both require a six-pin and an eight-pin power connector, and both cards draw a bit over 300 watts too. AMD listed the TDP for the 290X as 250w, but it hedged that answer and never gave it as an official number, but rather an estimate. It didn't reply to our emails asking for the TDP of the R9 290, so we'll just put 250w there with an asterick.</p> <p style="text-align: left;"><img src="/files/u302/amdrad_r9_290_flatangle_rgb_24in_small_1.png" alt="R9 290" title="R9 290" width="600" height="401" /></p> <p style="text-align: center;"><strong>The R9 290 is exactly the same size as the R9 290X at 11 inches, and it also features the same 250w-ish TDP. </strong></p> <p style="text-align: center;">&nbsp;</p> <h3 style="text-align: left;">PowerTune, TrueAudio, and XDMA</h3> <p style="text-align: left;">Like it's larger, more-powerful sibling, the R9 290 comes with all the baked in features that define the top-tier of this generation of GPUs, namely revamped PowerTune controls, TrueAudio technology, and XDNA Crossfire. TrueAudio and XDMA Crossfire are exclusive to the R9 290/X series of cards, though the current iteration of PowerTune is found on all Rx based cards, and TrueAudio is also found on the $140 R7 260X board.</p> <p style="text-align: left;">&nbsp;</p> <p style="text-align: center;"><img src="/files/u302/powertune_1.jpg" alt="PowerTune" title="PowerTune" width="600" height="701" /></p> <p style="text-align: center;"><strong>The new PowerTune controls let you set maximum limits for fan speeds and temperature. We preferred the sliders though, as we found that moving the reticle in the map caused unpredictable results. </strong></p> <p style="text-align: left;">Briefly, AMD has changed the PowerTune interface found in the Catalyst Control Center to give you an easier way to control clock, memory, and fan speeds. It also now has a slider that lets you dictate the maximum fan speed and maximum temperature, just like Nvidia is doing with its GPU Boost 2.0 technology found in its 700-series GPUs. You can tell the software to force the card to run at 90C, for example, and it'll throttle the clock speeds in order to maintain those temperatures. Additionally, if you're sensitive to acoustics, you can also set a limit on the fan speed while letting the other settings run at maximum value as well. It's also provided a "2-dimensional heat map" which we found confusing. We also found in testing that moving some of the sliders too far would cause the entire system to hard lock and then experience trouble rebooting, so tread carefully here.<strong> By default the fan on the R9 290 runs at a maximum speed of 47%</strong>.<strong><br /></strong></p> <p style="text-align: left;"><strong>TrueAudio</strong> is also found on the R9 290, and whether or not it'll make a big difference in the life of an average gamer remains to be seen as no games that use it have been released yet. Gordon wrote an extremely in-depth article about it however, so <a href="http://www.maximumpc.com/everything_you_wanted_know_about_amd%E2%80%99s_new_trueaudio_technology_2013">head on over</a> to it and you'll have all your questions answered.</p> <p style="text-align: left;">Finally, <strong>XDMA </strong>is a new technology appearing for the first time in the Radeon R9 290 series of cards. It eschews the ribbon cable we've grown so un-fond of over all these years and instead uses hardware built into the GPUs and also lets the cards communicate over the PCI-Express bus. Though AMD had seemingly wrangled its frame pacing issues with its <a href="http://www.maximumpc.com/amd_delivers_frame_pacing_fix_driver_update135">recent fix</a>, it's software-based and still available for R9 280X cards and lower. For the R9 290 series though, those changes are built into the drivers and handled through XDMA. The previous GPUs based on Tahiti and lower will still have to use the ribbon cable as there's no exclusive hardware built into the GPUs to handle that transaction, but this is not surprising. It is also reasonable to assume that going forward all new GPUs will use XDMA.</p> <p style="text-align: left;">The main reason for XDMA is to handle the increased traffic resulting from the proliferation of multiple displays as well as 4k panels. If AMD continued using the old ribbon cable there simply wouldn't be enough bandwidth to drive the displays at 60Hz, so XDMA was both a necessity to prepare for the future as well as a great way to allow for smoother CrossFire at super-high resolutions. AMD claims there is no performance penalty at all to this configuration, but unfortunatley there's not really any way to run Apples to Apples testing since the Crossfire connectors are removed on the cards (though the electrical contacts are still intact). We also don't have a second R9 290X or R9 290 card to test Crossfire currently, but we hope to get a second card in soon.</p> <p style="text-align: center;">&nbsp;</p> <p style="text-align: center;"><img src="/files/u302/xdma.jpg" alt="XDMA" title="XDMA" width="650" height="362" /></p> <p style="text-align: center;"><strong>Only the R9 and R9 290X get the built-in XDMA engine for CrossFire over the PCIe bus. Hopefully it'll come to all of AMD's new cards in the future.</strong></p> <p style="text-align: left;">&nbsp;</p> <p style="text-align: left;"><em>Hit the next page for what really matters - benchmarks, power, heat, and overclocking, and our final thoughts.</em></p> <h3 style="text-align: left;"> <hr /></h3> <h3 style="text-align: left;">Testing the R9 290</h3> <p style="text-align: left;">Testing the R9 290 was a straight-forward affair as we had already tested the R9 290X, and this new card doesn't have any new features though it does have one semi-notable feature removed, which is the Uber and Quiet modes. The physical switch is still there on the edge of the PCB, and it still lets you toggle between two BIOSes, but it has no effect on fan speed. On the R9 290X the switch would adjust the maximum fan speed from 40 percent in Quiet mode to 55 percent in Uber mode. The R9 290 still has dual BIOSes, and one is write-protected while the other isn't.&nbsp; Otherwise there's nothing new that needs testing on this card that doesn't exist on the R9 290X, so let's get it on.</p> <p style="text-align: left;">To start off, let’s have a look at how things compare at 2560x1600:</p> <p style="text-align: center;"><strong>2560x1600 Benchmarks</strong></p> <p style="text-align: center;"><strong><img src="/files/u302/r9290_2560_1.jpg" alt="2560 Benchmarks" title="2560 Benchmarks" width="321" height="492" /></strong></p> <p style="text-align: center;"> <!--[if gte mso 9]><xml> <w:WordDocument> <w:View>Normal</w:View> <w:Zoom>0</w:Zoom> <w:TrackMoves /> <w:TrackFormatting /> <w:PunctuationKerning /> <w:ValidateAgainstSchemas /> <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid> <w:IgnoreMixedContent>false</w:IgnoreMixedContent> <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText> <w:DoNotPromoteQF /> <w:LidThemeOther>EN-US</w:LidThemeOther> <w:LidThemeAsian>X-NONE</w:LidThemeAsian> <w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript> <w:Compatibility> <w:BreakWrappedTables /> <w:SnapToGridInCell /> <w:WrapTextWithPunct /> <w:UseAsianBreakRules /> <w:DontGrowAutofit /> <w:SplitPgBreakAndParaMark /> <w:EnableOpenTypeKerning /> <w:DontFlipMirrorIndents /> <w:OverrideTableStyleHps /> </w:Compatibility> <m:mathPr> <m:mathFont m:val="Cambria Math" /> <m:brkBin m:val="before" /> <m:brkBinSub m:val="&#45;-" /> <m:smallFrac m:val="off" /> <m:dispDef /> <m:lMargin m:val="0" /> <m:rMargin m:val="0" /> <m:defJc m:val="centerGroup" /> <m:wrapIndent m:val="1440" /> <m:intLim m:val="subSup" /> <m:naryLim m:val="undOvr" /> </m:mathPr></w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:WordDocument> <w:View>Normal</w:View> <w:Zoom>0</w:Zoom> <w:TrackMoves /> <w:TrackFormatting /> <w:PunctuationKerning /> <w:ValidateAgainstSchemas /> <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid> <w:IgnoreMixedContent>false</w:IgnoreMixedContent> <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText> <w:DoNotPromoteQF /> <w:LidThemeOther>EN-US</w:LidThemeOther> <w:LidThemeAsian>X-NONE</w:LidThemeAsian> <w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript> <w:Compatibility> <w:BreakWrappedTables /> <w:SnapToGridInCell /> <w:WrapTextWithPunct /> <w:UseAsianBreakRules /> <w:DontGrowAutofit /> <w:SplitPgBreakAndParaMark /> <w:EnableOpenTypeKerning /> <w:DontFlipMirrorIndents /> <w:OverrideTableStyleHps /> </w:Compatibility> <m:mathPr> <m:mathFont m:val="Cambria Math" /> <m:brkBin m:val="before" /> <m:brkBinSub m:val="&#45;-" /> <m:smallFrac m:val="off" /> <m:dispDef /> <m:lMargin m:val="0" /> <m:rMargin m:val="0" /> <m:defJc m:val="centerGroup" /> <m:wrapIndent m:val="1440" /> <m:intLim m:val="subSup" /> <m:naryLim m:val="undOvr" /> </m:mathPr></w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="false" DefSemiHidden="false" DefQFormat="false" DefPriority="99" LatentStyleCount="371"> <w:LsdException Locked="false" Priority="0" QFormat="true" Name="Normal" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 1" /> <w:LsdException Locked="false" Priority="9" SemiHidden="true" UnhideWhenUsed="true" QFormat="true" Name="heading 2" /> <w:LsdException Locked="false" Priority="9" SemiHidden="true" UnhideWhenUsed="true" QFormat="true" Name="heading 3" /> <w:LsdException Locked="false" Priority="9" SemiHidden="true" UnhideWhenUsed="true" QFormat="true" Name="heading 4" /> <w:LsdException Locked="false" Priority="9" SemiHidden="true" UnhideWhenUsed="true" QFormat="true" Name="heading 5" /> <w:LsdException Locked="false" Priority="9" SemiHidden="true" UnhideWhenUsed="true" QFormat="true" Name="heading 6" /> <w:LsdException Locked="false" Priority="9" SemiHidden="true" UnhideWhenUsed="true" QFormat="true" Name="heading 7" /> <w:LsdException Locked="false" Priority="9" SemiHidden="true" UnhideWhenUsed="true" QFormat="true" Name="heading 8" /> <w:LsdException Locked="false" Priority="9" SemiHidden="true" UnhideWhenUsed="true" QFormat="true" Name="heading 9" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="index 1" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="index 2" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="index 3" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="index 4" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="index 5" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="index 6" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="index 7" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="index 8" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="index 9" /> <w:LsdException Locked="false" Priority="39" SemiHidden="true" UnhideWhenUsed="true" Name="toc 1" /> <w:LsdException Locked="false" Priority="39" SemiHidden="true" UnhideWhenUsed="true" Name="toc 2" /> <w:LsdException Locked="false" Priority="39" SemiHidden="true" UnhideWhenUsed="true" Name="toc 3" /> <w:LsdException Locked="false" Priority="39" SemiHidden="true" UnhideWhenUsed="true" Name="toc 4" /> <w:LsdException Locked="false" Priority="39" SemiHidden="true" UnhideWhenUsed="true" Name="toc 5" /> <w:LsdException Locked="false" Priority="39" SemiHidden="true" UnhideWhenUsed="true" Name="toc 6" /> <w:LsdException Locked="false" Priority="39" SemiHidden="true" UnhideWhenUsed="true" Name="toc 7" /> <w:LsdException Locked="false" Priority="39" SemiHidden="true" UnhideWhenUsed="true" Name="toc 8" /> <w:LsdException Locked="false" Priority="39" SemiHidden="true" UnhideWhenUsed="true" Name="toc 9" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Normal Indent" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="footnote text" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="annotation text" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="header" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="footer" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="index heading" /> <w:LsdException Locked="false" Priority="35" SemiHidden="true" UnhideWhenUsed="true" QFormat="true" Name="caption" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="table of figures" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="envelope address" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="envelope return" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="footnote reference" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="annotation reference" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="line number" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="page number" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="endnote reference" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="endnote text" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="table of authorities" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="macro" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="toa heading" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List Bullet" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List Number" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List 2" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List 3" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List 4" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List 5" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List Bullet 2" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List Bullet 3" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List Bullet 4" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List Bullet 5" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List Number 2" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List Number 3" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List Number 4" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List Number 5" /> <w:LsdException Locked="false" Priority="10" QFormat="true" Name="Title" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Closing" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Signature" /> <w:LsdException Locked="false" Priority="1" SemiHidden="true" UnhideWhenUsed="true" Name="Default Paragraph Font" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Body Text" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Body Text Indent" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List Continue" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List Continue 2" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List Continue 3" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List Continue 4" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List Continue 5" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Message Header" /> <w:LsdException Locked="false" Priority="11" QFormat="true" Name="Subtitle" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Salutation" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Date" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Body Text First Indent" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Body Text First Indent 2" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Note Heading" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Body Text 2" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Body Text 3" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Body Text Indent 2" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Body Text Indent 3" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Block Text" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Hyperlink" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="FollowedHyperlink" /> <w:LsdException Locked="false" Priority="22" QFormat="true" Name="Strong" /> <w:LsdException Locked="false" Priority="20" QFormat="true" Name="Emphasis" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Document Map" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Plain Text" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="E-mail Signature" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="HTML Top of Form" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="HTML Bottom of Form" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Normal (Web)" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="HTML Acronym" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="HTML Address" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="HTML Cite" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="HTML Code" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="HTML Definition" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="HTML Keyboard" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="HTML Preformatted" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="HTML Sample" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="HTML Typewriter" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="HTML Variable" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Normal Table" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="annotation subject" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="No List" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Outline List 1" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Outline List 2" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Outline List 3" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Simple 1" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Simple 2" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Simple 3" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Classic 1" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Classic 2" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Classic 3" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Classic 4" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Colorful 1" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Colorful 2" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Colorful 3" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Columns 1" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Columns 2" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Columns 3" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Columns 4" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Columns 5" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Grid 1" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Grid 2" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Grid 3" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Grid 4" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Grid 5" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Grid 6" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Grid 7" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Grid 8" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table List 1" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table List 2" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table List 3" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table List 4" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table List 5" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table List 6" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table List 7" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table List 8" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table 3D effects 1" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table 3D effects 2" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table 3D effects 3" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Contemporary" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Elegant" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Professional" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Subtle 1" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Subtle 2" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Web 1" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Web 2" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Web 3" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Balloon Text" /> <w:LsdException Locked="false" Priority="39" Name="Table Grid" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Theme" /> <w:LsdException Locked="false" SemiHidden="true" Name="Placeholder Text" /> <w:LsdException Locked="false" Priority="1" QFormat="true" Name="No Spacing" /> <w:LsdException Locked="false" Priority="60" Name="Light Shading" /> <w:LsdException Locked="false" Priority="61" Name="Light List" /> <w:LsdException Locked="false" Priority="62" Name="Light Grid" /> <w:LsdException Locked="false" Priority="63" Name="Medium Shading 1" /> <w:LsdException Locked="false" Priority="64" Name="Medium Shading 2" /> <w:LsdException Locked="false" Priority="65" Name="Medium List 1" /> <w:LsdException Locked="false" Priority="66" Name="Medium List 2" /> <w:LsdException Locked="false" Priority="67" Name="Medium Grid 1" /> <w:LsdException Locked="false" Priority="68" Name="Medium Grid 2" /> <w:LsdException Locked="false" Priority="69" Name="Medium Grid 3" /> <w:LsdException Locked="false" Priority="70" Name="Dark List" /> <w:LsdException Locked="false" Priority="71" Name="Colorful Shading" /> <w:LsdException Locked="false" Priority="72" Name="Colorful List" /> <w:LsdException Locked="false" Priority="73" Name="Colorful Grid" /> <w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 1" /> <w:LsdException Locked="false" Priority="61" Name="Light List Accent 1" /> <w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 1" /> <w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 1" /> <w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 1" /> <w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 1" /> <w:LsdException Locked="false" SemiHidden="true" Name="Revision" /> <w:LsdException Locked="false" Priority="34" QFormat="true" Name="List Paragraph" /> <w:LsdException Locked="false" Priority="29" QFormat="true" Name="Quote" /> <w:LsdException Locked="false" Priority="30" QFormat="true" Name="Intense Quote" /> <w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 1" /> <w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 1" /> <w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 1" /> <w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 1" /> <w:LsdException Locked="false" Priority="70" Name="Dark List Accent 1" /> <w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 1" /> <w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 1" /> <w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 1" /> <w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 2" /> <w:LsdException Locked="false" Priority="61" Name="Light List Accent 2" /> <w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 2" /> <w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 2" /> <w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 2" /> <w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 2" /> <w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 2" /> <w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 2" /> <w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 2" /> <w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 2" /> <w:LsdException Locked="false" Priority="70" Name="Dark List Accent 2" /> <w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 2" /> <w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 2" /> <w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 2" /> <w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 3" /> <w:LsdException Locked="false" Priority="61" Name="Light List Accent 3" /> <w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 3" /> <w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 3" /> <w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 3" /> <w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 3" /> <w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 3" /> <w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 3" /> <w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 3" /> <w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 3" /> <w:LsdException Locked="false" Priority="70" Name="Dark List Accent 3" /> <w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 3" /> <w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 3" /> <w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 3" /> <w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 4" /> <w:LsdException Locked="false" Priority="61" Name="Light List Accent 4" /> <w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 4" /> <w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 4" /> <w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 4" /> <w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 4" /> <w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 4" /> <w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 4" /> <w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 4" /> <w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 4" /> <w:LsdException Locked="false" Priority="70" Name="Dark List Accent 4" /> <w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 4" /> <w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 4" /> <w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 4" /> <w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 5" /> <w:LsdException Locked="false" Priority="61" Name="Light List Accent 5" /> <w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 5" /> <w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 5" /> <w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 5" /> <w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 5" /> <w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 5" /> <w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 5" /> <w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 5" /> <w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 5" /> <w:LsdException Locked="false" Priority="70" Name="Dark List Accent 5" /> <w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 5" /> <w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 5" /> <w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 5" /> <w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 6" /> <w:LsdException Locked="false" Priority="61" Name="Light List Accent 6" /> <w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 6" /> <w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 6" /> <w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 6" /> <w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 6" /> <w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 6" /> <w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 6" /> <w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 6" /> <w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 6" /> <w:LsdException Locked="false" Priority="70" Name="Dark List Accent 6" /> <w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 6" /> <w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 6" /> <w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 6" /> <w:LsdException Locked="false" Priority="19" QFormat="true" Name="Subtle Emphasis" /> <w:LsdException Locked="false" Priority="21" QFormat="true" Name="Intense Emphasis" /> <w:LsdException Locked="false" Priority="31" QFormat="true" Name="Subtle Reference" /> <w:LsdException Locked="false" Priority="32" QFormat="true" Name="Intense Reference" /> <w:LsdException Locked="false" Priority="33" QFormat="true" Name="Book Title" /> <w:LsdException Locked="false" Priority="37" SemiHidden="true" UnhideWhenUsed="true" Name="Bibliography" /> <w:LsdException Locked="false" Priority="39" SemiHidden="true" UnhideWhenUsed="true" QFormat="true" Name="TOC Heading" /> <w:LsdException Locked="false" Priority="41" Name="Plain Table 1" /> <w:LsdException Locked="false" Priority="42" Name="Plain Table 2" /> <w:LsdException Locked="false" Priority="43" Name="Plain Table 3" /> <w:LsdException Locked="false" Priority="44" Name="Plain Table 4" /> <w:LsdException Locked="false" Priority="45" Name="Plain Table 5" /> <w:LsdException Locked="false" Priority="40" Name="Grid Table Light" /> <w:LsdException Locked="false" Priority="46" Name="Grid Table 1 Light" /> <w:LsdException Locked="false" Priority="47" Name="Grid Table 2" /> <w:LsdException Locked="false" Priority="48" Name="Grid Table 3" /> <w:LsdException Locked="false" Priority="49" Name="Grid Table 4" /> <w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark" /> <w:LsdException Locked="false" Priority="51" Name="Grid Table 6 Colorful" /> <w:LsdException Locked="false" Priority="52" Name="Grid Table 7 Colorful" /> <w:LsdException Locked="false" Priority="46" Name="Grid Table 1 Light Accent 1" /> <w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 1" /> <w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 1" /> <w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 1" /> <w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 1" /> <w:LsdException Locked="false" Priority="51" Name="Grid Table 6 Colorful Accent 1" /> <w:LsdException Locked="false" Priority="52" Name="Grid Table 7 Colorful Accent 1" /> <w:LsdException Locked="false" Priority="46" Name="Grid Table 1 Light Accent 2" /> <w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 2" /> <w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 2" /> <w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 2" /> <w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 2" /> <w:LsdException Locked="false" Priority="51" Name="Grid Table 6 Colorful Accent 2" /> <w:LsdException Locked="false" Priority="52" Name="Grid Table 7 Colorful Accent 2" /> <w:LsdException Locked="false" Priority="46" Name="Grid Table 1 Light Accent 3" /> <w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 3" /> <w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 3" /> <w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 3" /> <w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 3" /> <w:LsdException Locked="false" Priority="51" Name="Grid Table 6 Colorful Accent 3" /> <w:LsdException Locked="false" Priority="52" Name="Grid Table 7 Colorful Accent 3" /> <w:LsdException Locked="false" Priority="46" Name="Grid Table 1 Light Accent 4" /> <w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 4" /> <w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 4" /> <w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 4" /> <w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 4" /> <w:LsdException Locked="false" Priority="51" Name="Grid Table 6 Colorful Accent 4" /> <w:LsdException Locked="false" Priority="52" Name="Grid Table 7 Colorful Accent 4" /> <w:LsdException Locked="false" Priority="46" Name="Grid Table 1 Light Accent 5" /> <w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 5" /> <w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 5" /> <w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 5" /> <w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 5" /> <w:LsdException Locked="false" Priority="51" Name="Grid Table 6 Colorful Accent 5" /> <w:LsdException Locked="false" Priority="52" Name="Grid Table 7 Colorful Accent 5" /> <w:LsdException Locked="false" Priority="46" Name="Grid Table 1 Light Accent 6" /> <w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 6" /> <w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 6" /> <w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 6" /> <w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 6" /> <w:LsdException Locked="false" Priority="51" Name="Grid Table 6 Colorful Accent 6" /> <w:LsdException Locked="false" Priority="52" Name="Grid Table 7 Colorful Accent 6" /> <w:LsdException Locked="false" Priority="46" Name="List Table 1 Light" /> <w:LsdException Locked="false" Priority="47" Name="List Table 2" /> <w:LsdException Locked="false" Priority="48" Name="List Table 3" /> <w:LsdException Locked="false" Priority="49" Name="List Table 4" /> <w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark" /> <w:LsdException Locked="false" Priority="51" Name="List Table 6 Colorful" /> <w:LsdException Locked="false" Priority="52" Name="List Table 7 Colorful" /> <w:LsdException Locked="false" Priority="46" Name="List Table 1 Light Accent 1" /> <w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 1" /> <w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 1" /> <w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 1" /> <w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 1" /> <w:LsdException Locked="false" Priority="51" Name="List Table 6 Colorful Accent 1" /> <w:LsdException Locked="false" Priority="52" Name="List Table 7 Colorful Accent 1" /> <w:LsdException Locked="false" Priority="46" Name="List Table 1 Light Accent 2" /> <w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 2" /> <w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 2" /> <w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 2" /> <w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 2" /> <w:LsdException Locked="false" Priority="51" Name="List Table 6 Colorful Accent 2" /> <w:LsdException Locked="false" Priority="52" Name="List Table 7 Colorful Accent 2" /> <w:LsdException Locked="false" Priority="46" Name="List Table 1 Light Accent 3" /> <w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 3" /> <w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 3" /> <w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 3" /> <w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 3" /> <w:LsdException Locked="false" Priority="51" Name="List Table 6 Colorful Accent 3" /> <w:LsdException Locked="false" Priority="52" Name="List Table 7 Colorful Accent 3" /> <w:LsdException Locked="false" Priority="46" Name="List Table 1 Light Accent 4" /> <w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 4" /> <w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 4" /> <w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 4" /> <w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 4" /> <w:LsdException Locked="false" Priority="51" Name="List Table 6 Colorful Accent 4" /> <w:LsdException Locked="false" Priority="52" Name="List Table 7 Colorful Accent 4" /> <w:LsdException Locked="false" Priority="46" Name="List Table 1 Light Accent 5" /> <w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 5" /> <w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 5" /> <w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 5" /> <w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 5" /> <w:LsdException Locked="false" Priority="51" Name="List Table 6 Colorful Accent 5" /> <w:LsdException Locked="false" Priority="52" Name="List Table 7 Colorful Accent 5" /> <w:LsdException Locked="false" Priority="46" Name="List Table 1 Light Accent 6" /> <w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 6" /> <w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 6" /> <w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 6" /> <w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 6" /> <w:LsdException Locked="false" Priority="51" Name="List Table 6 Colorful Accent 6" /> <w:LsdException Locked="false" Priority="52" Name="List Table 7 Colorful Accent 6" /> </w:LatentStyles> </xml><![endif]--><!--[if gte mso 9]><xml> <w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="false" DefSemiHidden="false" DefQFormat="false" DefPriority="99" LatentStyleCount="371"> <w:LsdException Locked="false" Priority="0" QFormat="true" Name="Normal" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 1" /> <w:LsdException Locked="false" Priority="9" SemiHidden="true" UnhideWhenUsed="true" QFormat="true" Name="heading 2" /> <w:LsdException Locked="false" Priority="9" SemiHidden="true" UnhideWhenUsed="true" QFormat="true" Name="heading 3" /> <w:LsdException Locked="false" Priority="9" SemiHidden="true" UnhideWhenUsed="true" QFormat="true" Name="heading 4" /> <w:LsdException Locked="false" Priority="9" SemiHidden="true" UnhideWhenUsed="true" QFormat="true" Name="heading 5" /> <w:LsdException Locked="false" Priority="9" SemiHidden="true" UnhideWhenUsed="true" QFormat="true" Name="heading 6" /> <w:LsdException Locked="false" Priority="9" SemiHidden="true" UnhideWhenUsed="true" QFormat="true" Name="heading 7" /> <w:LsdException Locked="false" Priority="9" SemiHidden="true" UnhideWhenUsed="true" QFormat="true" Name="heading 8" /> <w:LsdException Locked="false" Priority="9" SemiHidden="true" UnhideWhenUsed="true" QFormat="true" Name="heading 9" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="index 1" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="index 2" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="index 3" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="index 4" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="index 5" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="index 6" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="index 7" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="index 8" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="index 9" /> <w:LsdException Locked="false" Priority="39" SemiHidden="true" UnhideWhenUsed="true" Name="toc 1" /> <w:LsdException Locked="false" Priority="39" SemiHidden="true" UnhideWhenUsed="true" Name="toc 2" /> <w:LsdException Locked="false" Priority="39" SemiHidden="true" UnhideWhenUsed="true" Name="toc 3" /> <w:LsdException Locked="false" Priority="39" SemiHidden="true" UnhideWhenUsed="true" Name="toc 4" /> <w:LsdException Locked="false" Priority="39" SemiHidden="true" UnhideWhenUsed="true" Name="toc 5" /> <w:LsdException Locked="false" Priority="39" SemiHidden="true" UnhideWhenUsed="true" Name="toc 6" /> <w:LsdException Locked="false" Priority="39" SemiHidden="true" UnhideWhenUsed="true" Name="toc 7" /> <w:LsdException Locked="false" Priority="39" SemiHidden="true" UnhideWhenUsed="true" Name="toc 8" /> <w:LsdException Locked="false" Priority="39" SemiHidden="true" UnhideWhenUsed="true" Name="toc 9" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Normal Indent" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="footnote text" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="annotation text" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="header" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="footer" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="index heading" /> <w:LsdException Locked="false" Priority="35" SemiHidden="true" UnhideWhenUsed="true" QFormat="true" Name="caption" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="table of figures" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="envelope address" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="envelope return" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="footnote reference" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="annotation reference" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="line number" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="page number" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="endnote reference" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="endnote text" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="table of authorities" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="macro" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="toa heading" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List Bullet" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List Number" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List 2" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List 3" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List 4" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List 5" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List Bullet 2" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List Bullet 3" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List Bullet 4" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List Bullet 5" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List Number 2" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List Number 3" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List Number 4" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List Number 5" /> <w:LsdException Locked="false" Priority="10" QFormat="true" Name="Title" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Closing" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Signature" /> <w:LsdException Locked="false" Priority="1" SemiHidden="true" UnhideWhenUsed="true" Name="Default Paragraph Font" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Body Text" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Body Text Indent" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List Continue" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List Continue 2" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List Continue 3" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List Continue 4" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List Continue 5" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Message Header" /> <w:LsdException Locked="false" Priority="11" QFormat="true" Name="Subtitle" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Salutation" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Date" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Body Text First Indent" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Body Text First Indent 2" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Note Heading" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Body Text 2" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Body Text 3" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Body Text Indent 2" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Body Text Indent 3" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Block Text" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Hyperlink" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="FollowedHyperlink" /> <w:LsdException Locked="false" Priority="22" QFormat="true" Name="Strong" /> <w:LsdException Locked="false" Priority="20" QFormat="true" Name="Emphasis" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Document Map" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Plain Text" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="E-mail Signature" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="HTML Top of Form" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="HTML Bottom of Form" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Normal (Web)" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="HTML Acronym" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="HTML Address" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="HTML Cite" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="HTML Code" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="HTML Definition" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="HTML Keyboard" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="HTML Preformatted" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="HTML Sample" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="HTML Typewriter" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="HTML Variable" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Normal Table" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="annotation subject" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="No List" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Outline List 1" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Outline List 2" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Outline List 3" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Simple 1" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Simple 2" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Simple 3" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Classic 1" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Classic 2" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Classic 3" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Classic 4" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Colorful 1" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Colorful 2" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Colorful 3" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Columns 1" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Columns 2" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Columns 3" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Columns 4" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Columns 5" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Grid 1" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Grid 2" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Grid 3" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Grid 4" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Grid 5" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Grid 6" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Grid 7" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Grid 8" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table List 1" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table List 2" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table List 3" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table List 4" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table List 5" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table List 6" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table List 7" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table List 8" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table 3D effects 1" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table 3D effects 2" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table 3D effects 3" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Contemporary" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Elegant" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Professional" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Subtle 1" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Subtle 2" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Web 1" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Web 2" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Web 3" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Balloon Text" /> <w:LsdException Locked="false" Priority="39" Name="Table Grid" /> <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Theme" /> <w:LsdException Locked="false" SemiHidden="true" Name="Placeholder Text" /> <w:LsdException Locked="false" Priority="1" QFormat="true" Name="No Spacing" /> <w:LsdException Locked="false" Priority="60" Name="Light Shading" /> <w:LsdException Locked="false" Priority="61" Name="Light List" /> <w:LsdException Locked="false" Priority="62" Name="Light Grid" /> <w:LsdException Locked="false" Priority="63" Name="Medium Shading 1" /> <w:LsdException Locked="false" Priority="64" Name="Medium Shading 2" /> <w:LsdException Locked="false" Priority="65" Name="Medium List 1" /> <w:LsdException Locked="false" Priority="66" Name="Medium List 2" /> <w:LsdException Locked="false" Priority="67" Name="Medium Grid 1" /> <w:LsdException Locked="false" Priority="68" Name="Medium Grid 2" /> <w:LsdException Locked="false" Priority="69" Name="Medium Grid 3" /> <w:LsdException Locked="false" Priority="70" Name="Dark List" /> <w:LsdException Locked="false" Priority="71" Name="Colorful Shading" /> <w:LsdException Locked="false" Priority="72" Name="Colorful List" /> <w:LsdException Locked="false" Priority="73" Name="Colorful Grid" /> <w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 1" /> <w:LsdException Locked="false" Priority="61" Name="Light List Accent 1" /> <w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 1" /> <w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 1" /> <w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 1" /> <w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 1" /> <w:LsdException Locked="false" SemiHidden="true" Name="Revision" /> <w:LsdException Locked="false" Priority="34" QFormat="true" Name="List Paragraph" /> <w:LsdException Locked="false" Priority="29" QFormat="true" Name="Quote" /> <w:LsdException Locked="false" Priority="30" QFormat="true" Name="Intense Quote" /> <w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 1" /> <w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 1" /> <w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 1" /> <w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 1" /> <w:LsdException Locked="false" Priority="70" Name="Dark List Accent 1" /> <w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 1" /> <w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 1" /> <w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 1" /> <w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 2" /> <w:LsdException Locked="false" Priority="61" Name="Light List Accent 2" /> <w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 2" /> <w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 2" /> <w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 2" /> <w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 2" /> <w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 2" /> <w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 2" /> <w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 2" /> <w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 2" /> <w:LsdException Locked="false" Priority="70" Name="Dark List Accent 2" /> <w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 2" /> <w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 2" /> <w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 2" /> <w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 3" /> <w:LsdException Locked="false" Priority="61" Name="Light List Accent 3" /> <w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 3" /> <w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 3" /> <w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 3" /> <w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 3" /> <w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 3" /> <w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 3" /> <w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 3" /> <w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 3" /> <w:LsdException Locked="false" Priority="70" Name="Dark List Accent 3" /> <w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 3" /> <w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 3" /> <w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 3" /> <w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 4" /> <w:LsdException Locked="false" Priority="61" Name="Light List Accent 4" /> <w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 4" /> <w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 4" /> <w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 4" /> <w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 4" /> <w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 4" /> <w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 4" /> <w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 4" /> <w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 4" /> <w:LsdException Locked="false" Priority="70" Name="Dark List Accent 4" /> <w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 4" /> <w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 4" /> <w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 4" /> <w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 5" /> <w:LsdException Locked="false" Priority="61" Name="Light List Accent 5" /> <w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 5" /> <w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 5" /> <w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 5" /> <w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 5" /> <w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 5" /> <w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 5" /> <w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 5" /> <w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 5" /> <w:LsdException Locked="false" Priority="70" Name="Dark List Accent 5" /> <w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 5" /> <w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 5" /> <w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 5" /> <w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 6" /> <w:LsdException Locked="false" Priority="61" Name="Light List Accent 6" /> <w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 6" /> <w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 6" /> <w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 6" /> <w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 6" /> <w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 6" /> <w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 6" /> <w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 6" /> <w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 6" /> <w:LsdException Locked="false" Priority="70" Name="Dark List Accent 6" /> <w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 6" /> <w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 6" /> <w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 6" /> <w:LsdException Locked="false" Priority="19" QFormat="true" Name="Subtle Emphasis" /> <w:LsdException Locked="false" Priority="21" QFormat="true" Name="Intense Emphasis" /> <w:LsdException Locked="false" Priority="31" QFormat="true" Name="Subtle Reference" /> <w:LsdException Locked="false" Priority="32" QFormat="true" Name="Intense Reference" /> <w:LsdException Locked="false" Priority="33" QFormat="true" Name="Book Title" /> <w:LsdException Locked="false" Priority="37" SemiHidden="true" UnhideWhenUsed="true" Name="Bibliography" /> <w:LsdException Locked="false" Priority="39" SemiHidden="true" UnhideWhenUsed="true" QFormat="true" Name="TOC Heading" /> <w:LsdException Locked="false" Priority="41" Name="Plain Table 1" /> <w:LsdException Locked="false" Priority="42" Name="Plain Table 2" /> <w:LsdException Locked="false" Priority="43" Name="Plain Table 3" /> <w:LsdException Locked="false" Priority="44" Name="Plain Table 4" /> <w:LsdException Locked="false" Priority="45" Name="Plain Table 5" /> <w:LsdException Locked="false" Priority="40" Name="Grid Table Light" /> <w:LsdException Locked="false" Priority="46" Name="Grid Table 1 Light" /> <w:LsdException Locked="false" Priority="47" Name="Grid Table 2" /> <w:LsdException Locked="false" Priority="48" Name="Grid Table 3" /> <w:LsdException Locked="false" Priority="49" Name="Grid Table 4" /> <w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark" /> <w:LsdException Locked="false" Priority="51" Name="Grid Table 6 Colorful" /> <w:LsdException Locked="false" Priority="52" Name="Grid Table 7 Colorful" /> <w:LsdException Locked="false" Priority="46" Name="Grid Table 1 Light Accent 1" /> <w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 1" /> <w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 1" /> <w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 1" /> <w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 1" /> <w:LsdException Locked="false" Priority="51" Name="Grid Table 6 Colorful Accent 1" /> <w:LsdException Locked="false" Priority="52" Name="Grid Table 7 Colorful Accent 1" /> <w:LsdException Locked="false" Priority="46" Name="Grid Table 1 Light Accent 2" /> <w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 2" /> <w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 2" /> <w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 2" /> <w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 2" /> <w:LsdException Locked="false" Priority="51" Name="Grid Table 6 Colorful Accent 2" /> <w:LsdException Locked="false" Priority="52" Name="Grid Table 7 Colorful Accent 2" /> <w:LsdException Locked="false" Priority="46" Name="Grid Table 1 Light Accent 3" /> <w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 3" /> <w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 3" /> <w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 3" /> <w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 3" /> <w:LsdException Locked="false" Priority="51" Name="Grid Table 6 Colorful Accent 3" /> <w:LsdException Locked="false" Priority="52" Name="Grid Table 7 Colorful Accent 3" /> <w:LsdException Locked="false" Priority="46" Name="Grid Table 1 Light Accent 4" /> <w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 4" /> <w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 4" /> <w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 4" /> <w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 4" /> <w:LsdException Locked="false" Priority="51" Name="Grid Table 6 Colorful Accent 4" /> <w:LsdException Locked="false" Priority="52" Name="Grid Table 7 Colorful Accent 4" /> <w:LsdException Locked="false" Priority="46" Name="Grid Table 1 Light Accent 5" /> <w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 5" /> <w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 5" /> <w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 5" /> <w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 5" /> <w:LsdException Locked="false" Priority="51" Name="Grid Table 6 Colorful Accent 5" /> <w:LsdException Locked="false" Priority="52" Name="Grid Table 7 Colorful Accent 5" /> <w:LsdException Locked="false" Priority="46" Name="Grid Table 1 Light Accent 6" /> <w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 6" /> <w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 6" /> <w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 6" /> <w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 6" /> <w:LsdException Locked="false" Priority="51" Name="Grid Table 6 Colorful Accent 6" /> <w:LsdException Locked="false" Priority="52" Name="Grid Table 7 Colorful Accent 6" /> <w:LsdException Locked="false" Priority="46" Name="List Table 1 Light" /> <w:LsdException Locked="false" Priority="47" Name="List Table 2" /> <w:LsdException Locked="false" Priority="48" Name="List Table 3" /> <w:LsdException Locked="false" Priority="49" Name="List Table 4" /> <w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark" /> <w:LsdException Locked="false" Priority="51" Name="List Table 6 Colorful" /> <w:LsdException Locked="false" Priority="52" Name="List Table 7 Colorful" /> <w:LsdException Locked="false" Priority="46" Name="List Table 1 Light Accent 1" /> <w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 1" /> <w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 1" /> <w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 1" /> <w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 1" /> <w:LsdException Locked="false" Priority="51" Name="List Table 6 Colorful Accent 1" /> <w:LsdException Locked="false" Priority="52" Name="List Table 7 Colorful Accent 1" /> <w:LsdException Locked="false" Priority="46" Name="List Table 1 Light Accent 2" /> <w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 2" /> <w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 2" /> <w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 2" /> <w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 2" /> <w:LsdException Locked="false" Priority="51" Name="List Table 6 Colorful Accent 2" /> <w:LsdException Locked="false" Priority="52" Name="List Table 7 Colorful Accent 2" /> <w:LsdException Locked="false" Priority="46" Name="List Table 1 Light Accent 3" /> <w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 3" /> <w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 3" /> <w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 3" /> <w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 3" /> <w:LsdException Locked="false" Priority="51" Name="List Table 6 Colorful Accent 3" /> <w:LsdException Locked="false" Priority="52" Name="List Table 7 Colorful Accent 3" /> <w:LsdException Locked="false" Priority="46" Name="List Table 1 Light Accent 4" /> <w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 4" /> <w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 4" /> <w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 4" /> <w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 4" /> <w:LsdException Locked="false" Priority="51" Name="List Table 6 Colorful Accent 4" /> <w:LsdException Locked="false" Priority="52" Name="List Table 7 Colorful Accent 4" /> <w:LsdException Locked="false" Priority="46" Name="List Table 1 Light Accent 5" /> <w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 5" /> <w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 5" /> <w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 5" /> <w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 5" /> <w:LsdException Locked="false" Priority="51" Name="List Table 6 Colorful Accent 5" /> <w:LsdException Locked="false" Priority="52" Name="List Table 7 Colorful Accent 5" /> <w:LsdException Locked="false" Priority="46" Name="List Table 1 Light Accent 6" /> <w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 6" /> <w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 6" /> <w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 6" /> <w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 6" /> <w:LsdException Locked="false" Priority="51" Name="List Table 6 Colorful Accent 6" /> <w:LsdException Locked="false" Priority="52" Name="List Table 7 Colorful Accent 6" /> </w:LatentStyles> </xml><![endif]--><!--[if gte mso 10]> <mce:style><! /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin-top:0in; mso-para-margin-right:0in; mso-para-margin-bottom:8.0pt; mso-para-margin-left:0in; line-height:107%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin;} --><!--[if gte mso 10]> <mce:style><! /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin-top:0in; mso-para-margin-right:0in; mso-para-margin-bottom:8.0pt; mso-para-margin-left:0in; line-height:107%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin;} --><!--[endif] --><!--[endif] --></p> <p class="MsoNormalCxSpFirst" style="line-height: 150%; text-align: center;"><em><span style="font-size: 10.5pt; line-height: 150%; font-family: &quot;Arial&quot;,&quot;sans-serif&quot;; color: black; border: none windowtext 1.0pt; mso-border-alt: none windowtext 0in; padding: 0in; background: white;">Best scores are bolded. Our test bed is a 3.33GHz Core i7 3960X Extreme Edition in an Asus Rampage IV Extreme motherboard with 16GB of DDR3/1600 and a Thermaltake ToughPower 1,050W PSU. The OS is 64-bit Windows 8. All games are run at 2560x1600 with 4X AA except for the 3DMark tests.</span></em></p> <p>&nbsp;</p> <p style="text-align: left;">At 2560x1600 the R9 290 trades blows with the more-expensive GTX 780, making it the better alternative considering it costs $100 less. The two cards were more or less equal throughout testing, though the GTX 780 was noticeably faster in Far Cry 3, which is odd considering this is an AMD title. The GTX 780 also held the upper hand in Unigine Valley, Metro, 3DMark, and Battlefield 3, with the other tests going to the R9 290. Of course, one area where the GTX 780 is a clear winner is in watts consumed and overall noise, as it was much quieter and also sucked less juice from the wall socket as well. This is nothing new, as the R9 cards run ridiculously hot, and though the R9 290 isn't annoyingly loud, it's certainly louder than the GTX 780. It also ran about 10C hotter than the GTX 780 as well. If the cards were evenly priced, we'd say the Nvidia card gets the nod due to its acoustics and power consumption, but given the $100 price disparity between the two we have to say the AMD card is the better value. Heat and power consumption don't matter that much on the desktop, and the R9 290 card is rock stable, so given its price advantage it takes the win in this category.</p> <p style="text-align: left;">&nbsp;</p> <p style="text-align: left;">Now, let's look at how the R9 290 stacks up to all the cards in this class at 2560x1600.</p> <p style="text-align: center;"><strong>2560x1600 Benchmarks</strong></p> <p style="text-align: center;"><img src="/files/u302/r9_group_bench.jpg" alt="R9 Group Benchmarks" title="R9 Group Benchmarks" width="524" height="492" /></p> <p style="text-align: center;"><em><span style="font-size: 10.5pt; line-height: 150%; font-family: &quot;Arial&quot;,&quot;sans-serif&quot;; color: black; border: none windowtext 1.0pt; mso-border-alt: none windowtext 0in; padding: 0in; background: white;">Best scores are bolded. Our test bed is a 3.33GHz Core i7 3960X Extreme Edition in an Asus Rampage IV Extreme motherboard with 16GB of DDR3/1600 and a Thermaltake ToughPower 1,050W PSU. The OS is 64-bit Windows 8. All games are run at 2560x1600 with 4X AA except for the 3DMark tests.</span></em></p> <p style="text-align: left;">As you can see from this chart the R9 290X is faster than the R9 290 by quite a bit in many tests, and also beats the GTX Titan in several tests as well. None of this is new information, but when we ran the R9 290X tests before we didn't have enough time to test with Nvidia's latest 331.65 driver, so this chart represents the current leader board in the GPU world. It's all the fastest cards, tested with the latest drivers. You can see the R9 290X and Titan trading blows, which is a situation Nvidia hopes to correct with its <a href="http://www.maximumpc.com/nvidia_announces_gtx_780_ti_launch_date_price_shield_update_and_780770_price_cuts_2013">GTX 780 Ti</a> launch later this week.</p> <p style="text-align: left;">&nbsp;</p> <p style="text-align: left;">We also received some requests for a few benchmarks showing what this card can do at <strong>1080p</strong> going up against the less expensive GeForce GTX 770, so here they are:</p> <p style="text-align: center;"><strong>1080p Benchmarks</strong></p> <p style="text-align: center;"><img src="/files/u302/1080p_benchmarks_0.jpg" alt="1080p Benchmarks" title="1080p Benchmarks" width="326" height="428" /></p> <address style="text-align: center;"><em><span style="font-size: 10.5pt; line-height: 150%; font-family: &quot;Arial&quot;,&quot;sans-serif&quot;; color: black; border: none windowtext 1.0pt; mso-border-alt: none windowtext 0in; padding: 0in; background: white;">Best scores are bolded. Our test bed is a 3.33GHz Core i7 3960X Extreme Edition in an Asus Rampage IV Extreme motherboard with 16GB of DDR3/1600 and a Thermaltake ToughPower 1,050W PSU. The OS is 64-bit Windows 8. All games are run at 1920x1080 with 4X AA.</span></em></address> <p style="text-align: left;">Not much explanation is needed here as this card is the clear winner over the GTX 770 at 1080p. It is absolutly perfect at this resolution as it hits that silky-smooth 60fps target in most of the games we use for testing. Metro: Last Light barely runs at 30fps, but that's not too surprising as it can punish even the burliest GPU, and it's heavy use of PhysX favors Nvidia cards. Overall though, this card crushes it at 1080p, but costs $70 more than the GTX 770 so it's a trade-off for sure.</p> <h3 style="text-align: left;">4k Benchmarks</h3> <p style="text-align: left;">Both Nvidia and AMD are pushing 4k big time with their latest GPUs, so naturally we've run some tests at this resolution. Games at 4K look absolutely amazing, but boy oh boy do you need some serious firepower to run any of the latest games at full detail. In fact, they are so demanding at this 3840x2160 resolution that we have to disable AA otherwise it is simply unplayable, even on these premium GPUs. As an aside, it's interesting to see what they can do at 4K but it's also not terribly relevant right now due to the cost of the panels. The panel we used in the <a href="http://www.maximumpc.com/dream_machine_2013">Dream Machine</a> cost $3,500, and the Sharp panel we used for these tests (which we believe is the exact same unit) costs $5,300, so we seriously doubt even hardcore gamers are running these bad boys yet. It is simply too bleeding edge, unless you can run dual or three-way Titans or R9 290X cards. We never though we'd say it, but that's even too rich for our blood. Regardless, here are the numbers:</p> <p style="text-align: center;"><strong>4K Benchmarks</strong></p> <p style="text-align: center;"><img src="/files/u302/4k_r9_290.jpg" alt="R9 290 4K" title="R9 290 4K" width="333" height="428" /></p> <p style="text-align: center;"><em><span style="font-size: 10.5pt; line-height: 150%; font-family: &quot;Arial&quot;,&quot;sans-serif&quot;; color: black; border: none windowtext 1.0pt; mso-border-alt: none windowtext 0in; padding: 0in; background: white;">Best scores are bolded. Our test bed is a 3.33GHz Core i7 3960X Extreme Edition in an Asus Rampage IV Extreme motherboard with 16GB of DDR3/1600 and a Thermaltake ToughPower 1,050W PSU. The OS is 64-bit Windows 8. All games are run at 3840x2160 with AA disabled.</span></em></p> <p style="text-align: left;">In our 4k tests there is not a clear winner as it's five wins for AMD, and four wins for Nvidia, though, once again, the fact that the R9 290 costs $100 less than the GTX 780 gives it an advantage considering their performance parity. The R9 290 is the clear winner is Crysis 3, Far Cry 3, Tomb Raider (all AMD games, by the way), Battlefield 3, and Hitman, whereas the GTX 780 is only significantly faster in Metro: Last Light, which is an Nvidia title with physics that are not friendly to AMD's cards at all. All in all though, it's an impressive showing for a $400 GPU.</p> <h3>Power, Heat, and Overclocking</h3> <p style="text-align: left;">Just like its big brother R9 290X the R9 290 ran hot, made a little bit of noise, and wasn’t able to be overclocked beyond its base "max" clock of 947MHz. AMD lists its clock speed as “up to 947MHz” and in testing that is how it goes, spinning up to 947MHz when it can, then backing off that clock a bit when temperatures get too extreme. Once it has achieved that delicate balance, it continues to throttle clock speeds up and down by 50Mhz or so under load always staying around 93 or 94C the entire time. Yes, it’s very hot, especially compared to Nvidia’s cards, which typically never get hotter than 83C or so overclocked, but the R9 290 was totally, 100 percent stable throughout testing. Once again we looped Heaven 4.0 over the weekend, and our test bed had no issues whatsoever. The R9 290 sat there at about 94C the entire weekend, and never crashed. Overclocking though, is out of the question. The card already runs hot enough to make the GPU throttle in stock trim, so it's not possible to push the card any further at its stock settings. We could have pushed the fan beyond 47 percent, sure, but it gets very loud very quickly, even at 50 percent, so we don't imagine most users will want to run this GPU at that noise level.</p> <p style="text-align: left;">The stock cooling mechanism AMD built for this card does a good job of exhausting heat however, even though it looks a bit plain, especially in comparison to the sleek coolers on the GTX 780/Titan. When the card is hovering over 90C you can still put your hand one half-inch away from it and feel almost no heat whatsoever, so it seems to exhaust well and run totally fine despite its sky-high temperatures. We know it's weird seeing a card run at 94C, and it takes some getting used to. AMD has assured us that is how the card is designed, so it should be able to run at those temps for its entire life without issues. We certainly had no issues in testing, and it was always stable, so we have to give it a passing grade. Just like with the super-hot R9 290X we cannot wait to see what aftermarket cooling mechanisms do for this card's heat output and overclocking potential. Just like how you can overclock a GTX 780 to match a Titan, we're sure the R9 290 could be pumped up to match the 290X with enough cooling. We will have to wait and see if those cards from Asus, Gigabyte, MSI, Sapphire, XFX, and others ever materialize, but we believe they will, and we're excited to check them out when they do arrive, hopefully before the holidays.</p> <h3 style="text-align: left;"><strong>Final Thoughts</strong></h3> <p style="text-align: left;">When AMD launched the R9 290X last week it was an assault on Nvidia's single-GPU dominance in the premium video card space, and it was a shot that certainly hit its target. The R9 290X exceeded the GTX 780's performance while costing $100 less, so that is a clear-cut victory for AMD. Undaunted, Nvidia responded by dropping the GTX 780's price down to $500, essentially wiping out the R9 290X's advantage in that matchup. The Titan is still threatened by the R9 290X though, but Nvidia doesn't seem to bothered by it, so for now it's leaving the Titan alone. Now that we have the R9 290 though, the GTX 780 is once again under some serious pressure from AMD because the 290 is just as fast, and once again, costs $100 less. If you have $400 burning a hole in your pocket, the R9 290 is clearly the fastest GPU at that price point. We didn't test it against the GTX 770 simply because that is a card we test at 1080p, and the R9 290 is a 2560x1600 card, but it would certainly be faster than the GTX 770 as well since it can beat a GTX 780 in many tests.</p> <p style="text-align: left;">Overall, the R9 290 is another excellent GPU from AMD with a tremendous price-to-performance ratio that Nvidia simlply cannot match at this time. It definitely runs hotter and makes a bit more noise than it's next of kin on the green team, but for $100 we would bet most consumers would be willing to put on some headphones. Plus it's almost winter, so the heat will probably come in handy for a lot of folks. On a serious note though, we did not find the heat or noise created by this card to be a problem, so don't let it scare you off.</p> <p style="text-align: left;">From here we wait for two events to occur - the GTX 780 Ti launch later this week, which Nvidia is hoping will allow it to once again wrest control of the trophy for "fastest single GPU" since the R9 290X has muddied the waters a bit and put its Titan in peril, at least when it comes to gaming. Also, it's possible that the R9 290 launch will cause Nvidia to lower the price on the GTX 780 even further to be more competitive. As always we will have to wait and see what happens.</p> <p style="text-align: left;">Finally, there are still unknowns in both camps at this time. AMD has its <a href="http://www.maximumpc.com/amd_r9_290x_will_be_much_faster_titan_battlefield_4">Mantle</a> API and <a href="http://www.maximumpc.com/everything_you_wanted_know_about_amd%E2%80%99s_new_trueaudio_technology_2013">TrueAudio</a>, both of which are untested at this time. Nvidia has <a href="http://www.maximumpc.com/nvidia_announces_nvidia_g-sync_gamestream_and_much_more">G-Sync monitors</a>, ShadowPlay, its <a href="http://www.maximumpc.com/nvidias_geforce_gtx_holiday_bundles_feature_free_games_and_shield_discounts2013">Holiday Game Bundle</a>, GameStream/Shield, and of course, better acoustics and lower overall temps due to Kepler's efficiency. We've yet to test frame pacing using AMD's new XDMA setup, but reports indicate it's finally as good if not better than Nvidia's SLI at this time. Regardless, both AMD and Nvidia have very unique and exclusive features at this time, making the choice between one camp or the other more difficult than it's ever been.</p> <p style="text-align: left;">All in all, we can't remember a time when competition has been as white hot and fierce between AMD and Nvidia as it is right now. AMD has really come out swinging for the fences with its Hawaii GPUs, which have already resulted in both price drops and a new GPU on the way in the form of the GTX 780 Ti. Whether or not today's launch of the R9 290 results in even more price cuts or GPU offspring remains to be seen, but one thing is certain -- it's an awesome time to be in the GPU market.</p> http://www.maximumpc.com/amd_radeon_r9_290_benchmarks#comments amd r9 290 radeon Video cards Reviews Videocards Tue, 05 Nov 2013 06:17:58 +0000 Josh Norem 26610 at http://www.maximumpc.com Haswell-E Review http://www.maximumpc.com/haswell-e_review_2014 <!--paging_filter--><h3>Haswell-E: Meet Intel’s new eight-core game changing CPU</h3> <p>After three long years of going hungry with quad-cores, red meat is finally back on the menu for enthusiasts. And not just any gamey slab full of gristle with shared cores, either. With its new eight-core Haswell-E CPU, Intel may have served up the most mouth-watering, beautifully seared piece of red meat in a long time.</p> <p>And it’s a good thing, too, because enthusiast’s stomachs have been growling. Devil’s Canyon? That puny quad-core was just an appetizer. And that dual-core highly overclockable Pentium K CPU? It’s the mint you grab on your way out of the steak house.</p> <p><iframe src="//www.youtube.com/embed/_h9ggGZHFtU" width="620" height="349" frameborder="0"></iframe></p> <p>No, what enthusiasts have craved and wanted ever since Intel’s original clock-blocking job on the original Sandy Bridge-E was a true, overclockable enthusiast chip with eight cores. So if you’re ready for a belt loosening, belly full of enthusiast-level prime rib, pass the horse radish, get that damned salad off our table, and read on to see if Intel’s Haswell-E is everything we hoped it would be.&nbsp;</p> <p><strong>Meet the Haswell-E parts</strong></p> <p><span style="color: #ff0000;"><img src="/files/u154082/haswell-e_comparison_chart.png" alt="haswell e comparison chart" title="haswell e comparison chart" width="620" height="241" /></span></p> <p>&nbsp;</p> <p><img src="/files/u154082/lga2011v3socket.jpg" alt="haswell e socket" title="haswell e socket" width="620" height="626" /></p> <p><strong>Despite its name, the LGA2011-v3 socket is not same as the older LGA2011 socket. Fortunately, the cooling offsets are exactly the same, so almost all older coolers and accessories should work just fine.&nbsp;</strong></p> <p><img src="/files/u154082/lga2011socket1.jpg" alt="lga2011" title="lga2011" width="620" height="556" /></p> <p><strong>Though they look the same, LGA2011’s socket has arms that are actually arranged differently than the new LGA2011-v3 that replaces it. And no, you can’t drop a newer Haswell-E into this socket and make it work.</strong></p> <h4>Haswell-E</h4> <p><strong>The first consumer Intel eight-core arrives at last</strong></p> <p>Being a card-carrying member of the PC enthusiast class is not an easy path to follow. Sure, you get the most cores and priciest parts, but it also means you get to wait a hell of a long time in between CPU upgrades. And with Intel’s cadence the last few years, it also means you get the leftovers. It’s been that way ever since Intel went with its two-socket strategy with the original LGA1366/LGA1156. Those who picked the big-boy socket and stuck to their guns on Pure PC performance always got the shaft.&nbsp;</p> <p>The original Ivy Bridge in LGA1156 socket, for example, hit the streets in April of 2012. As a reward for having the more efficient and faster CPU, Intel rewarded the small-socket crowd with its Haswell in June of 2013. It wasn’t until September of 2013 that big-boy socket users finally got Ivy Bridge-E for their LGA2011s. But with Haswell already out and tearing up the benchmarks, who the hell cared?</p> <p>Well, that time has come with Haswell-E, Intel’s first replacement for the aging LGA2011 platform since 2011. This time though, Intel isn’t just shuffling new parts into its old stack. For the first since the original Pentium 4 Extreme Edition, paying the price premium actually nets you more: namely, the company’s first consumer eight-core CPU.</p> <p><strong>Meet the T-Rex of consumer CPUs: The Core i7-5960X</strong></p> <p>We were actually a little leery of Haswell when it first launched last year. It was, after all, a chip seemingly tuned for the increasingly mobile/laptoppy world we were told was our post PC-apocalyptic future. Despite this, we recognized the chip as the CPU to have for new system builders. Clock for clock, its 22nm process, tri-gate transistors put everything else to shame—even the six-core Core i7-3930K chip in many tasks. So it’s no surprise that when Intel took a quad-core Haswell, put it in the Xerox machine, and hit the copy x2 button , we’d be ecstatic. Eight cores are decidedly better than six cores or four cores when you need them.&nbsp;</p> <p>The cores don’t come without a cost though, and we don’t mean the usual painful price Intel asks for its highest-end CPUs. It’s no secret that more cores means more heat, which means lower clock speeds. That’s one of the rationales Intel used with the original six-core Core i7-3960X. Although sold as a six-core, the original Sandy Bridge-E was built using an eight-core die on which Intel had permanently switched off two cores. Intel said it wanted to balance the needs of the many versus the needs of the few—that is, by turning off two of the cores, the part could hit higher clock speeds. Indeed, the Core i7-3960X had a base clock of 3.3GHz and Turbo Boost of 3.9GHz, and most could overclock it to 5GHz. The same chip packaged as a Xeon with all eight cores working—the Xeon E5-2687W—was locked down at 3.1GHz and mostly buzzed along at 3.4GHz.</p> <p>With the new Core i7-5960X—the only eight-core of the bunch—the chip starts at a seemingly pedestrian 3GHz with a Turbo Boost of one core up to 3.5GHz. Those subsonic clock speeds won’t impress against the Core i7-4790K, which starts at 4GHz. You’ll find more on how well Haswell-E performs against Haswell in our performance section, but that’s the price to be paid, apparently, to get a chip with this many cores under the heat spreader. Regarding thermals, in fact, Intel has increased the TDP rating to 140 watts versus 130 watts of Ivy Bridge-E and Sandy Bridge-E.&nbsp;</p> <p>If the low clocks annoy you, the good news is the part is fully unlocked, so the use of overclocking has been approved. For our test units, we had very early hardware and tight deadlines, so we didn’t get very far with our overclocking efforts. Talking with vendors, however, most seem very pleased with the clock speeds they were seeing. One vendor told us overclocks of all cores at 4.5GHz was already obtainable and newer microcode updates were expected to improve that. With even the vaunted Devil’s Canyon Core i7-4790K topping out at 4.7GHz to 4.8GHz, a 4.5GHz is actually a healthy overclock for an eight-core CPU.</p> <p><span style="white-space: pre;"> </span>When you dive down into the actual cores though, much is the same, of course. It’s based on a 22nm process. It has “3D” tri-gate transistors and integrated voltage regulation. Oh, and it’s also the first CPU to feature an integrated DDR4 memory controller.</p> <p><strong>Click the next page to read about DDR4</strong></p> <hr /> <p>&nbsp;</p> <h4>DDR4 details</h4> <p>If you think Haswell-E has been a long wait, just think about DDR3, which made its debut as main memory in systems since 2007. Yes, 2007. The only component that has lasted seven years in most enthusiasts systems might be the PSU, but it’s even rare to find anyone kicking a 500-watt PSU from 2007 these days.&nbsp;</p> <p><span style="white-space: pre;"> </span>DDR4 has been in gestation seemingly as long, so why the delay? From what we can tell, resistance to yet another new memory standard during a time when people thought the desktop PC and the PC in general were dying has been the root delay. It didn’t help that no one wanted to stick their head out first, either. RAM makers didn’t want to begin producing it DDR4 in volume until AMD or Intel made chipsets for it, and AMD and Intel didn’t want to support it because of the costs it would add to PCs at a time when people were trying to lower costs. The stalemate finally ends with Haswell-E, which integrates a quad-channel memory controller into its die.</p> <p>Initial launch speeds of DDR4 clock in at DDR4/2133. For those already running DDR3 at 3GHz or higher, a 2,133 data rate is a snooze, but you should realize that anything over 2133 is overclocked RAM. With DDR4, the JEDEC speeds (the body that sets RAM standards) already has target data rates of 3200 on the map. RAM vendors we’ve talked to are already shopping DIMMS near that speed.</p> <p>The best part of DDR4 may be its density message, though. For years, consumer DDR3 has topped out at 8GB on a DIMM. With DDR4, we should see 16B DIMMs almost immediately, and stacking of chips is built into the standard, so it’s possible we’ll see 32GB DIMMs over its lifetime. On a quad-channel, eight-DIMM motherboard, you should expect to be able to build systems with 128GB of RAM using non-ECC DIMMs almost immediately. DDR4 also brings power savings and other improvements, but the main highlights enthusiasts should expect are higher densities and higher clocks. Oh, and higher prices. RAM prices haven’t been fun for anyone of late, but DDR4 will definitely be a premium part for some time. In fact, we couldn’t even get exact pricing from memory vendors as we were going to press, so we’re bracing for some really bad news.</p> <h4>PCIe lanes: now a feature to be blocked</h4> <p>Over the years, we’ve come to expect Intel to clock-block core counts, clock speeds, Hyper-Threading, and even cache for “market segmentation” purposes. What that means is Intel has to find ways to differentiate one CPU from another. Sometimes that’s by turning off Hyper-Threading (witness Core i5 and Core i7) and sometimes its locking down clock speeds. With Haswell-E though, Intel has gone to new heights with its clock-blocking by actually turning off PCIe lanes on some Haswell-E parts to make them less desirable. At the top end, you have the 3GHz Core i7-5960X with eight cores. In the midrange you have the six-core 3.5GHz Core i7-5930K. And at the “low-end” you have the six-core 3.3GHz Core i7-5820K. The 5930K and the 5820K are virtually the same in specs except for one key difference: The PCIe lanes get blocked. Yes, while the Core i7-5960X and Core i7-5930K get 40 lanes of PCIe 3.0, the Core i7-5820K gets an odd 28 lanes of PCIe 3.0. That means those who had hoped to build “budget” Haswell-E boxes with multiple GPUs may have to think hard and fast about using the lowest-end Haswell-E chip. The good news is that for most people, it won’t matter. Plenty of people run Haswell systems with SLI or CrossFire, and those CPUs are limited to 16 lanes. Boards with PLX switches even support four-way GPU setups.</p> <p>Still, it’s a brain bender to think that when you populate an X99 board with the lowest-end Haswell-E, the PCIe configuration will change. The good news is at least they’ll work, just more slowly. Intel says it worked with board vendors to make sure all the slots will function with the budget Haswell-E part.&nbsp;</p> <p><img src="/files/u154082/mpc_haswell_front-back_1.jpg" alt="haswell e chip" title="haswell e chip" width="620" height="413" /></p> <p><strong>There have been clock-blocking rumors swirling around about the Haswell being a 12-core Xeon with four cores turned off. That’s not true and Intel says this die-shot proves it.&nbsp;</strong></p> <p><img src="/files/u154082/ivbe.jpg" alt="ivy bridge e" title="ivy bridge e" width="620" height="550" /></p> <p><strong>Ivy Bridge-E’s main advantage over Sandy Bridge-E was a native six-core die and greatly reduced power consumption. And, unfortunately, like its Ivy Bridge counterpart, overclocking yields on Ivy Bridge-E were greatly reduced over its predecessor, too, with few chips hitting more than 4.7GHz at best.</strong></p> <p><img src="/files/u154082/snbe.jpg" alt="sandy bridge e" title="sandy bridge e" width="308" height="260" /></p> <p><strong>Sandy Bridge-E and Sandy Bridge will long be remembered for its friendliness to overclocking and having two of its working cores killed Red Wedding–style by Intel.</strong></p> <p><strong>Click the next page to read about X99.</strong></p> <hr /> <p>&nbsp;</p> <h4>X99&nbsp;</h4> <p><strong>High-end enthusiasts finally get the chipset they want, sort of</strong></p> <p><img src="/files/u154082/x99blockdiagram.jpg" alt="x99 block diagram" title="x99 block diagram" width="620" height="381" /></p> <p><strong>Intel overcompensated in SATA on X99 but oddly left SATA Express on the cutting-room floor.</strong></p> <p>You know what we won’t miss? The X79 chipset. No offense to X79 owners, while the Core i7-4960X can stick around for a few more months, X79 can take its under-spec’ed butt out of our establishment. Think we’re being too harsh? We don’t.</p> <p>X79 has no native USB 3.0 support. And its SATA 6Gb/s ports? Only two. It almost reads like a feature set from the last decade to us. Fortunately, in a move we wholly endorse, Intel has gone hog wild in over-compensating for the weaknesses of X79.&nbsp;</p> <p>X99 has eight USB 2.0 ports and six USB 3.0 ports baked into the peripheral controller hub in it. For SATA 6Gb/s, Intel adds 10 ports to X99. Yes, 10 ports of SATA 6Gb/s. That gazongo number of SATA ports, however, is balanced out by two glaring omission in X99: no official SATA Express or M.2 support that came with Z97. Intel didn’t say why it left off SATA Express or M.2 in the chipset, but it did say motherboard vendors were free to implement it using techniques they gleaned from doing it on Z97 motherboards. If we had to hazard a guess, we’d say Intel’s conservative nature led it to leave the feature off the chipset, as the company is a stickler for testing new interfaces before adding official support. At this point, SATA Express has been a no-show. After all, motherboards with SATA Express became available in May with Z97, yet we still have not seen any native SATA Express drives. We expect most motherboard vendors to simply add it through discrete controllers; even our early board sample had a SATA Express port.&nbsp;</p> <p>One potential weakness of X99 is Intel’s use of the DMI 2.0. That offers roughly 2.5GB/s of transfer speed between the CPU and the south bridge or PCH, but with the board hanging 10 SATA devices, USB 3.0, Gigabit Ethernet, and 8 PCIe Gen 2.0 lanes off that link, there is the potential for massive congestion—but only in a worst-case scenario. You’d really have to a boat load of hardware lit up and sending and receiving data at once to cause the DMI 2.0 to bottleneck. Besides, Intel says, you can just hang the device off the plentiful PCIe Gen 3.0 from the CPU.</p> <p>That does bring up our last point on X99: the PCIe lanes. As we mentioned earlier, there will be some confusion over the PCIe lane configuration on systems with Core i7-5820K parts. With only 28 lanes of PCIe lanes available from that one chip, there’s concern that whole slots on the motherboard will be turned off. That won’t happen, Intel says. Instead, if you go with the low-rent ride, you simply lose bandwidth. Take an X99 mobo and plug in the Core i7-5930K and you get two slots at x16 PCIe, and one x8 slot. Remove that CPU and install the Core i7-5820K, and the slots will now be configured as one x16, one x8 and one x4. It’s still more bandwidth than you can get from a normal LGA1150-based Core i7-4770K but it will be confusing nonetheless. We expect motherboard vendors to sort it out for their customers, though.</p> <p>Haswell-E does bring one more interesting PCIe configuration though: the ability to run five graphics cards in the PCIe slots at x8 speeds. Intel didn’t comment on the reasons for the option but there only a few apparent reasons. The first is mining configurations where miners are already running six GPUs. Mining, however, doesn’t seem to need the bandwidth a x8 slot would provide. The other possibility is a five-way graphics card configuration being planned by Nvidia or AMD. At this point it’s just conjecture, but one thing we know is that X99 is a welcome upgrade. Good riddance X79.&nbsp;</p> <h4>Top Procs Compared</h4> <p><span style="color: #ff0000;"><span style="white-space: pre;"><img src="/files/u154082/top_processors.png" alt="top processors compared" title="top processors compared" width="620" height="344" /></span></span></p> <h4>Core Competency&nbsp;</h4> <p><strong>How many cores do you really need?</strong></p> <p><img src="/files/u154082/haswelletaskamanger.png" alt="haswell task manager" title="haswell task manager" width="620" height="564" /></p> <p><strong>It is indeed a glorious thing to see a task manager with this many threads, but not everyone needs them.</strong></p> <p>Like the great technology philosopher Sir Mix-A-Lot said, we like big cores and we cannot lie. We want as many cores as legally available. But we recognize that not everyone rolls as hard as we do with a posse of threads. With Intel’s first eight-core CPU, consumers can now pick from two cores all the way to eight on the Intel side of the aisle—and then there’s Hyper-Threading to confuse you even more. So, how many cores do you need? We’ll give you the quick-and-dirty lowdown.</p> <p><strong>Two cores</strong></p> <p>Normally, we’d completely skip dual-cores without Hyper-Threading because the parts tend to be the very bottom end of the pool Celerons. Our asterisk is the new Intel Pentium G3258 Anniversary Edition, or “Pentium K,” which is a real hoot of a chip. It easily overclocks and is dead cheap. It’s not the fastest in content creation by a long shot, but if we were building an ultra-budget gaming rig and needed to steal from the CPU budget for a faster GPU, we’d recommend this one. Otherwise, we see dual-cores as purely ultra-budget parts today.</p> <p><strong>Two cores with Hyper-Threading</strong></p> <p>For your parents who need a reliable, solid PC without overclocking (you really don’t want to explain how to back down the core voltage in the BIOS to grandma, do you?), the dual-core Core i3 parts fulfill the needs of most people who only do content creation on occasion. Hyper-Threading adds value in multi-threaded and multi-tasking tasks. You can almost think of these chips with Hyper-Threading as three-core CPUs.&nbsp;</p> <p><strong>Four cores</strong></p> <p>For anyone who does content creation such as video editing, encoding, or even photo editing with newer applications, a quad-core is usually our recommended part. Newer game consoles are also expected to push min specs for newer games to quad-cores or more as well, so for most people who carry an Enthusiast badge, a quad-core part is the place to start.</p> <p><strong>Four cores with Hyper-Threading</strong></p> <p>Hyper-Threading got a bad name early on from the Pentium 4 and existing software that actually saw it reduce performance when turned on. Those days are long behind us though, and Hyper-Threading offers a nice performance boost with its virtual cores. How much? &nbsp;A 3.5GHz Core i7 quad-core with Hyper-Threading generally offers the same performance on multi-threaded tasks as a Core i5 running at 4.5GHz. The Hyper-Threading helps with content creation and we’d say, if content creation is 30 percent or less of your time, this is the place to be and really the best fit for 90 percent of enthusiasts.</p> <p><strong>Six cores with Hyper-Threading</strong></p> <p>Once you pass the quad-core mark, you are moving pixels professionally in video editing, 3D modeling, or other tasks that necessitate the costs of a six-core chip or more. We still think that for 90 percent of folks, a four-core CPU is plenty, but if losing time rendering a video costs you money (or you’re just ADD), pay for a six-core or more CPU. How do you decide if you need six or eight cores? Read on.&nbsp;</p> <p><strong>Eight cores with Hyper-Threading</strong></p> <p>We recognize that not everyone needs an eight-core processor. In fact, one way to save cash is to buy the midrange six-core chip instead, but if time is money, an eight-core chip will pay for itself. For example, the eight-core Haswell-E is about 45 percent faster than the four-core Core i7-4790K chip. If your render job is three hours, that’s more time working on other paying projects. The gap gets smaller between the six-core and the eight-core of course, so it’s very much about how much your time is worth or how short your attention span is. But just to give you an idea, the 3.3GHz Core i7-5960X is about 20 percent faster than the Core i7-4960X running at 4GHz.</p> <p><strong>Click the next page to see how Haswell-E stacks up against Intel's other top CPUs.</strong></p> <hr /> <p>&nbsp;</p> <h4 style="font-size: 10px;">Intel’s Top Guns Compared</h4> <p><img src="/files/u154082/cpus17918.jpg" alt="haswell" title="haswell" width="620" height="413" /></p> <p><strong><strong>The LGA2011-based Core i7-4960X (left) and the LGA2011-v3-based Core i7-5960X (middle) dwarf the Core i7-4790K chip (right). Note the change in the heat spreader between the older 4960X and 5960X, which now has larger “wings” that make it easier to remove the CPU by hand. The breather hole, which allows for curing of the thermal interface material (solder in this case), has also been moved. Finally, while the chips are the same size, they are keyed differently to prevent you from installing a newer Haswell-E into an older Ivy Bridge-E board.</strong></strong></p> <h4>Benchmarks</h4> <p><strong>Performance junkies, rejoice! Haswell-E hits it out of the ballpark</strong></p> <p><img src="/files/u154082/x99-gaming_5-rev10.jpg" alt="x99 gigabyte" title="x99 gigabyte" width="620" height="734" /></p> <p><strong>We used a Gigabyte X99 motherboard (without the final heatsinks for the voltage-regulation modules) for our testing.</strong></p> <p>For our testing, we set up three identical systems with the fastest available CPUs for each platform. Each system used an Nvidia GeForce GTX 780 with the same 340.52 drivers, Corsair 240GB Neutron GTX SSDs, and 64-bit Windows 8.1 Enterprise. Since we’ve had issues with clock speeds varying on cards that physically look the same, we also verified the clock speeds of each GPU manually and also recorded the multiplier, bclock, and speeds the parts run at under single-threaded and multi-threaded loads. So you know, the 3GHz Core i7-5960X’s would run at 3.5GHz on single-threaded tasks but usually sat at 3.33GHz on multi-threaded tasks. The 3.6GHz Core i7-4960X ran everything at 4GHz, including multi-threading tasks. The 4GHz Core i7-4790K part sat at 4.4GHz on both single- and multi-threaded loads.</p> <p>For Z97, we used a Gigabyte Z97M-D3H mobo with a Core i7-4790K “Devil’s Canyon” chip aboard. &nbsp;An Asus Sabertooth X79 did the duty for our Core i7-4960X “Ivy Bridge-E” chip. Finally, for our Core i7-5960X chip, we obtained an early Gigabyte X99-Gaming 5 motherboard. The board was pretty early but we feel comfortable with our performance numbers as Intel has claimed the Core i7-5960X was “45 percent” faster than a quad-core chip, and that’s what we saw in some of our tests.&nbsp;</p> <p>One thing to note: The RAM capacities were different but in the grand scheme of things and the tests we run, it has no impact. The Sabertooth X79 &nbsp;had 16GB of DDR3/2133 in quad-channel mode, the Z97M-D3H had 16GB of DDR3/2133 in dual-channel mode. Finally, the X99-Gaming 5 board had 32GB of Corsair DDR4/2133. All three CPUs will overclock, but we tested at stock speeds to get a good baseline feel.&nbsp;</p> <p>For our benchmarks, we selected from a pile of real-world games, synthetic tests, as well as real-world applications across a wide gamut of disciplines. Our gaming tests were also run at very low resolutions and low-quality settings to take the graphics card out of the equation. We also acknowledge that people want to know what they can expect from the different CPUs at realistic settings and resolutions, so we also ran all of the games at their highest settings at 1920x1080 resolution, which is still the norm in PC gaming.&nbsp;</p> <p><strong>The results</strong></p> <p>We could get into a multi-sentence analysis of how it did and slowly break out with our verdict but in a society where people get impatient at the microwave, we’ll give you the goods up front: Holy Frakking Smokes, this chip is fast! The Core i7-5960X is simply everything high-end enthusiasts have been dreaming about.&nbsp;</p> <p>Just to give you an idea, we’ve been recording scores from $7,000 and $13,000 PCs in our custom Premiere Pro CS6 benchmark for a couple of years now. The fastest we’ve ever seen is the Digital Storm Aventum II that we reviewed in our January 2014 issue. The 3.3GHz Core i7-5960X was faster than the Aventum II’s Core i7-4960X running at 4.7GHz. Again, at stock speeds, the Haswell-E was faster than the fastest Ivy Bridge-E machine we’ve ever seen.</p> <p>It wasn’t just Premiere Pro CS6 we saw that spread in either. In most of our tests that stress multi-threading, we saw roughly a 45 percent to 50 percent improvement going from the Haswell to the Haswell-E part. The scaling gets tighter when you’re comparing the six-core Core i7-4960X but it’s still a nice, big number. We generally saw a 20 percent to 25 percent improvement in multi-threaded tasks.&nbsp;</p> <p>That’s not even factoring in the clock differences between the parts. The Core i7-4790K buzzes along at 4.4GHz—1.1GHz faster than the Core i7-5960X in multi-threaded tasks—yet it still got stomped by 45 to 50 percent. The Core i7-4960X had a nearly 700MHz clock advantage as well over the eight-core chip.</p> <p>The whole world isn’t multi-threaded, though. Once we get to workloads that don’t push all eight cores, the higher clock speeds of the other parts predictably take over. ProShow Producer 5.0, for example, has never pushed more than four threads and we saw the Core i7-5960X lose by 17 percent. The same happened in our custom Stitch.Efx 2.0 benchmark, too. In fact, in general, the Core i7-4790K will be faster thanks to its clock speed advantage. If you overclocked the Core i7-5960X to 4GHz or 4.4GHz on just four cores, the two should be on par in pure performance on light-duty workloads.</p> <p>In gaming, we saw some results from our tests that are a little bewildering to us. At low-resolution and low-quality settings, where the graphics card was not the bottleneck, the Core i7-4790K had the same 10 percent to 20 percent advantage. When we ran the same tests at ultra and 1080p resolution, the Core i7-5960X actually had a slight advantage in some of the runs against the Core i7-4790K chip. We think that may be from the bandwidth advantage the 5960X has. Remember, we ran all of the RAM at 2,133, so it’s not DDR4 vs. DDR3. It’s really quad-channel vs. dual-channel.</p> <p>We actually put a full breakdown of each of the benchmarks and detailed analysis on MaximumPC.com if you really want to nerd out on the performance.</p> <p><strong>What you should buy</strong></p> <p>Let’s say it again: The Core i7-5960X stands as the single fastest CPU we’ve seen to date. It’s simply a monster in performance in multi-threaded tasks and we think once you’ve overclocked it, it’ll be as fast as all the others in tasks that aren’t thread-heavy workloads.</p> <p>That, however, doesn’t mean everyone should start saving to buy a $1,000 CPU. No, for most people, the dynamic doesn’t change. For the 80 percent of you who fall into the average Joe or Jane nerd category, a four-core with Hyper-Threading still offers the best bang for the buck. It won’t be as fast as the eight-core, but unless you’re really working your rig for a living, made of money, or hate for your Handbrake encodes to take that extra 25 minutes, you can slum it with the Core i7-4790K chip. You don’t even have to heavily overclock it for the performance to be extremely peppy.</p> <p>For the remaining 20 percent who actually do a lot of encoding, rendering, professional photo editing, or heavy multi-tasking, the Core i7-5960X stands as the must-have CPU. It’s the chip you’ve been waiting for Intel to release. Just know that at purely stock speeds, you do give up performance to the Core i7-4790K part. But again, the good news is that with minor overclocking tweaks, it’ll be the equal or better of the quad-core chip.</p> <p>What’s really nice here is that for the first time, Intel is giving its “Extreme” SKU something truly extra for the $999 they spend. Previous Core i7 Extreme parts have always been good overclockers, but a lot of people bypassed them for the midrange chips such as the Core i7-4930K, which gave you the same core counts and overclocking to boot. The only true differentiation Extreme CPU buyers got was bragging rights. With Haswell-E, the Extreme buyers are the only ones with eight-core parts.</p> <p>Bang-for-the-buck buyers also get a treat from the six-core Core i7-5820K chip. At $389, it’s slightly more expensive than the chip it replaces—the $323 Core i7-4820K—but the extra price nets you two more cores. Yes, you lose PCIe bandwidth but most people probably won’t notice the difference. We didn’t have a Core i7-5820K part to test, but we &nbsp;believe on our testing with the Core i7-5960X that minor overclocking on the cheap Haswell-E would easily make it the equal of Intel’s previous six-core chips that could never be had for less than $580.</p> <p>And that, of course, brings us to the last point of discussion: Should you upgrade from your Core i7-4960X part? The easy answer is no. In pure CPU-on-CPU &nbsp;showdowns, the Core i7-4960X is about 20 percent slower in multi-threaded tasks, and in light-duty threads it’s about the same, thanks to the clock-speed advantage the Core i7-4960X has. There are two reasons we might want to toss aside the older chip, though. The first is the pathetic SATA 6Gb/s ports, which, frankly, you actually need on a heavy-duty work machine. The second reason would be the folks for whom a 20 percent reduction in rendering time would actually be worth paying for.&nbsp;</p> <p><strong>Click the next page to check out our Haswell-E benchmarks.</strong></p> <hr /> <h4><span style="font-size: 1.17em;">Haswell-E Benchmarks</span></h4> <p><strong>Haswell-E benchmarks overview</strong></p> <p><span style="font-size: 1.17em;">&nbsp;</span><img src="/files/u154082/haswell_e_benchmarks.png" alt="haswell e benchmarks" title="haswell e benchmarks" width="541" height="968" /></p> <p>&nbsp;</p> <p>&nbsp;</p> <p><strong>Benchmark Breakdown</strong></p> <p>We like to give you the goods on a nice table but not everyone is familiar with what we use to test and what exactly the numbers means so let’s break down some of the more significant results for you.&nbsp;</p> <p>&nbsp;</p> <p>&nbsp;</p> <p><img src="/files/u154082/cinebenchsinglethreaded.png" alt="cinebench 15 single" title="cinebench 15 single" width="620" height="472" /></p> <p><strong>Cinebench 15 single-threaded performance</strong></p> <p><span style="color: #000000;">We used Maxon’s Cinebench 15 benchmark to see just how fast the trio of chips would run this 3D rendering test. Cinebench 15 allows you to restrict it from using all of the cores or just one core. For this test, we wanted to see how the Core i7-5960X “Haswell-E” would do against the others by measuring a single core. The winner here is the Core i7-4790K “Devil’s Canyon” chip. That’s no surprise—it uses the same microarchitecture as the big boy Haswell-E but it has a ton more clock speed on default. The Haswell-E is about 21 percent slower running at 3.5GHz. The Devil’s Canyon part is running about 900MHz faster at 4.4GHz. Remember, on default, the Haswell-E only hits 3.5GHz on single-core loads. The Haswell-E better microarchitecture also loses to the Core i7-4960X “Ivy Bridge-E,” but not by much and that’s with the Ivy Bridge-E’s clock speed advantage of 500MHz. Still, the clear winner in single-threaded performance is the higher-clocked Devil’s Canyon chip.&nbsp;</span></p> <p><span style="color: #333399;">Winner: Core i7-4790K</span></p> <p><span style="color: #000000;"><img src="/files/u154082/cinebenchmulti.png" alt="cinebench 15 multi" title="cinebench 15 multi" width="620" height="428" /></span></p> <p><span style="color: #000000;"><strong>Cinebench 15 multi-threaded performance</strong></span></p> <p><span style="color: #000000;">You don’t buy an eight-core CPU and then throw only single-thread workloads at it, so we took the handcuffs off of Cinebench 15 and let it render with all available threads. On the Haswell-E part, that’s 16 threads of fun, on Ivy Bridge-E it’s 12-threads, and on Devil’s Canyon we’re looking at eight-threads. The winner by a clear margin is the Haswell-E part. Its performance is an astounding 49 percent faster than the Devil’s Canyon and about 22 percent faster than Ivy Bridge-E. We’ll just have to continue to remind you, too: this is with a severe clock penalty. That 49-percent-faster score is with all eight cores running at 3.3GHz vs all four of the Devil’s Canyon cores buzzing along at 4.4GHz. That’s an 1,100MHz clock speed advantage. Ivy Bridge-E also has a nice 700MHz clock advantage than Haswell-E. Chalk this up as a big, huge win for Haswell-E.&nbsp;</span></p> <p><span style="color: #333399;">Winner: Core i7-5960X</span></p> <p><span style="color: #000000;"><img src="/files/u154082/povray.png" alt="pov-ray" title="pov-ray" width="620" height="491" /></span></p> <p><span style="color: #000000;"><strong>POV-Ray performance</strong></span></p> <p><span style="color: #000000;">We wanted a second opinion on rendering performance, so we ran POV-Ray, a freeware ray tracer that has roots that reach back to the Amiga. Again, Haswell-E wins big-time with a 47 percent performance advantage over Devil’s Canyon and a 25 percent advantage over Ivy Bridge-E. Yeah, and all that stuff we said about the clock speed advantage the quad-core and six-core had, that applies here, too. Blah, blah, blah.</span></p> <p><span style="color: #333399;">Winner: Core i7-5960X</span></p> <p><span style="color: #000000;"><img src="/files/u154082/premierepro.png" alt="premiere pro" title="premiere pro" width="620" height="474" /></span></p> <p><span style="color: #000000;"><strong>Premiere Pro CS6 performance</strong></span></p> <p><span style="color: #000000;">One sanity check (benchmark results Intel produces to let you know what kind of performance to expect) said Haswell-E would outperform quad-core Intel parts by 45 percent in Premiere Pro Creative Cloud when working with 4K content. Our benchmark, however, doesn’t use 4K content yet, so we wondered if our results would be similar. For our test, we render out a 1080p-resolution file using source material shot by us on a Canon EOS 5D Mk II using multiple timelines and transitions. We restrict it to the CPU rather than using the GPU as well. Our result? The 3.3GHz Haswell-E was about 45 percent faster than the 4.4GHz Devil’s Canyon chip. Bada-bing! The two extra cores also spit out the render about 19 percent faster than the six-core Ivy Bridge-E. That’s fairly consistent performance we’re seeing between the different workload disciplines of 3D rendering and video encoding so far, and again, big, big wins for the Haswell-E part.&nbsp;</span></p> <p><span style="color: #333399;">Winner: Core i7-5960X</span></p> <p><span style="color: #000000;"><img src="/files/u154082/handbrake.png" alt="handbrake" title="handbrake" width="620" height="407" /></span></p> <p><span style="color: #000000;"><strong>Handbrake Encoding performance</strong></span></p> <p><span style="color: #000000;">For our encoding test, we took a 1080p-resolution video file and used Handbrake 0.9.9 to transcode it into a file using the Android tablet profile. Handbrake is very multi-threaded and leverages the CPU for its encoding and transcoding. Our results were still fairly stellar, with Haswell-E CPU performing about 38 percent faster than the Devil’s Canyon part. Things were uncomfortably close with the Ivy Bridge-E part though, with the eight-core chip coming in only about 13 percent faster than the six-core chip. Since the Ivy Bridge-E cores are slower than Haswell cores clock-for-clock, we were a bit surprised at how close they were. In the past, we have seen memory bandwidth play a role in encoding, but not necessarily Handbrake. Interestingly, despite locking all three parts down at 2,133MHz, the Ivy Bridge-E does provide more bandwidth than the Haswell-E part. One other thing we should mention: Intel’s “sanity check” numbers to let the media know what to expect for Handbrake performance showed a tremendous advantage for the Haswell-E. Against a Devil’s Canyon chip, Haswell-E was 69 percent faster and 34 percent faster than the Ivy Bridge-E chip. Why the difference? The workload. Intel uses a 4K-resolution file and transcodes it down to 1080p. We haven’t tried it at 4K, but we may, as Intel has provided the 4K-resolution sample files to the media. If true, and we have no reason to doubt it, it’s a good message for those who actually work at Ultra HD resolutions that the eight-cores can pay off. Overall, we’re declaring Haswell-E the winner here.</span></p> <p><span style="color: #333399;">Winner: Core i7-5960X</span></p> <p><span style="color: #000000;"><img src="/files/u154082/x264pass1.png" alt="x264 pass 1" title="x264 pass 1" width="620" height="496" /></span></p> <p><span style="color: #000000;"><strong>X264 HD 5.01 Pass 1 performance</strong></span></p> <p><span style="color: #000000;">We’ve been using TechArp.com’s X264 HD 5.0.1 benchmark to measure performance on new PCs. The test does two passes using the freeware x264 encoding library. The first pass is seemingly a little more sensitive to clock speeds and memory bandwidth rather than just pure core count. A higher frame rate is better. The first pass isn’t as core-sensitive, and memory bandwidth clock speed have more dividends here. Haswell still gives you a nice 36 percent boost over the Devil’s Canyon but that Ivy Bridge-E chip, despite its older core microarchitecture, comes is only beaten by 12 percent—too close for comfort. Of course, we’d throw in the usual caveat about the very large clock differences between the chips, but we’ve already said that three times. Oh, and yes, we did actually plagiarize by lifting two sentences from a previous CPU review for our description. That’s OK, we gave ourselves permission.&nbsp;</span></p> <p><span style="color: #333399;">Winner: Core i7-5960X but not by much</span></p> <p><span style="color: #000000;"><img src="/files/u154082/x264pass2.png" alt="x264 pass 2" title="x264 pass 2" width="620" height="499" /></span></p> <p><span style="color: #000000;"><strong>X264 HD 5.01 Pass 2 performance</strong></span></p> <p><span style="color: #000000;">Pass two of the X264 HD 5.01 benchmark is more sensitive to core and thread counts, and we see the Haswell-E come in with a nice 46 percent performance advantage against the Devil’s Canyon chip. The Ivy Bridge-E, though, still represents well. The Haswell-E chip is “only” 22 percent faster than it. Still, this is a solid win for the Haswell-E chip. We also like how we’re seeing very similar scaling in multiple encoding tests of roughly 45 percent. With Intel saying it’s seeing 69 percent in 4K resolution content in Handbrake, we’re wondering if the Haswell-E would offer similar scaling if we just moved all of our tests up to 4K.</span></p> <p><span style="color: #333399;">Winner: Core i7-5960X</span></p> <p><strong>Click the next page for even more Haswell-E benchmarks.</strong></p> <hr /> <p>&nbsp;</p> <p><span style="color: #000000;"><img src="/files/u154082/stitch.png" alt="stitch" title="stitch" width="620" height="473" /></span></p> <p><span style="color: #000000;"><strong>Stitch.EFx 2.0 Performance&nbsp;</strong></span></p> <p><span style="color: #000000;">Again, we like to mix up our workloads to stress different tasks that aren’t always multi-threaded to take advantage of a 12-core Xeon chip. For this test, we shot about 200 images with a Canon EOS 7D using a GigaPan motorized head. That’s roughly 1.9GB in images to make our gigapixel image using Stitch.EFx 2.0. The first third of the render is single-threaded as it stitches together the images. The final third is multi-threaded as it does the blending, perspective correction, and other intensive image processing. It’s a good blend of single-threaded performance and multi-threaded, but we expected the higher clocked parts to take the lead. No surprise, the Devil’s Canyon 4.4GHz advantage puts it in front, and the Haswell-E comes in about 14 percent slower with its 1.1GHz clock disadvantage. The clock speed advantage of the 4GHz Ivy Bridge-E also pays dividends, and we see the Haswell-E losing by about 10 percent. The good news? A dual-core Pentium K running at 4.7GHz coughed up a score of 1,029 seconds (not represented on the chart) and is roughly 22 percent slower than the CPU that costs about 11 times more.&nbsp;</span></p> <p><span style="color: #333399;">Winner: Core i7-4790K</span></p> <p><span style="color: #000000;"><img src="/files/u154082/7zip.png" alt="7-zip" title="7-zip" width="620" height="477" /></span></p> <p><span style="color: #000000;"><strong>7-Zip Performance</strong></span></p> <p><span style="color: #000000;">The popular and free zip utility, 7-Zip, has a nifty built-in benchmark that tells you the theoretical file-compression performance a CPU. You can pick the workload size and the number of threads. For our test, we maxed it out at 16-threads using an 8MB workload. That gives the Haswell-E familiar advantage in performance—about 45 percent—over the Devil’s Canyon part. Against that Ivy Bridge-E part though, it’s another uncomfortably close one at 8 percent. Still, a win is a win even if we have to say that if you have a shiny Core i7-4960X CPU in your system, you’re still doing fine.</span></p> <p><span style="color: #333399;">Winner: Core i7-5960X</span></p> <p><span style="color: #000000;"><img src="/files/u154082/sandra.png" alt="sisoft sandra" title="sisoft sandra" width="620" height="421" /></span></p> <p><span style="color: #000000;"><strong>Sisoft Sandra Memory Bandwidth (GB/s)</strong></span></p> <p>Since this is the first time we’re seeing DDR4 in a desktop part, we wanted to see how it stacked up in benchmarks. But, before you get too excited, remember that we set all three systems to 2133 data rates. The Devil’s Canyon part is dual-channel and the Ivy Bridge-E and Haswell-E are both quad-channel. With the memory set at 2133, we expected Haswell-E to be on par with the Ivy Bridge-E chip, but oddly, it was slower, putting out about 40GB/s of bandwidth. It’s still more than the 27GB/s the Devil’s Canyon could hit, but we expected it to be closer to double of what the Ivy Bridge-E was producing. For what it’s worth, we did double-check that we were operating in quad-channel mode and the clock speeds of our DIMMs. It’s possible this may change as the hardware we see becomes more final. We’ll also note that even at the same clock, DDR4 does suffer a latency penalty over DDR3. That would also be missing the point of DDR4, though. The new memory should give us larger modules and hit higher frequencies far easier, too, which will nullify that latency issue. Still, the winner is Ivy Bridge-E.</p> <p><span style="color: #333399;">Winner: Core i7-4960X</span></p> <p><span style="color: #000000;"><img src="/files/u154082/3dmarkgpu.png" alt="3d mark" title="3d mark" width="620" height="457" /></span></p> <p><span style="color: #000000;"><strong>3DMark Firestrike Overall Performance</strong></span></p> <p><span style="color: #000000;">Even though 3DMark Firestrike is primarily a graphics benchmark, not having a 3DMark Firestrike score is like not having coffee in the morning. Basically, it’s a tie between all three chips, and 3DMark Firestrike is working exactly as you expect it to: as a GPU benchmark.</span></p> <p><span style="color: #333399;">Winner: Tie</span></p> <p><span style="color: #000000;"><img src="/files/u154082/3dmarkphysics.png" alt="3d mark physics" title="3d mark physics" width="620" height="477" /></span></p> <p><span style="color: #000000;"><strong>3DMark Firestrike Physics Performance</strong></span></p> <p><span style="color: #000000;">3DMark does factor in the CPU performance for its physics tests. It’s certainly not weighted for multi-core counts as other tests are, but we see the Haswell-E with a decent 29 percent bump over the Devil’s Canyon chip. But, breathing down the neck of the Haswell-E is the Ivy Bridge-E chip. To us, that’s damned near a tie. Overall, the Haswell-E wins, but in gaming tasks—at stock clocks—paying for an 8-core monster is unnecessary except for those running multi-GPU setups.</span></p> <p><span style="color: #333399;">Winner: Core i7-5960X</span></p> <p><span style="color: #000000;"><img src="/files/u154082/valveparticle.png" alt="valve particle" title="valve particle" width="620" height="451" /></span></p> <p><span style="color: #000000;"><strong>Valve Particle Benchmark Performance</strong></span></p> <p><span style="color: #000000;">Valve’s Particle test was originally developed to show off quad-core performance to the world. It uses the company’s own physics magic, so it should give some indication of how well a chip will run. We’ve long suspected the test is cache and RAM latency happy. That seems to be backed by the numbers because despite the 1.1GHz advantage the Devil’s Canyon chip has, the Haswell-E is in front to the tune of 15 percent. The Ivy Bridge-E chip though, with its large cache, lower latency DDR3, and assloads of memory bandwidth actually comes out on top by about 3 percent. We’ll again note the Ivy Bridge-E part has a 700MHz advantage, so this is a very nice showing for the Haswell-E part.&nbsp;</span></p> <p><span style="color: #333399;">Winner: Core i7-4960X</span></p> <p><span style="color: #000000;"><img src="/files/u154082/dirtlow.png" alt="dirt showdown low" title="dirt showdown low" width="620" height="438" /></span></p> <p><span style="color: #000000;"><strong>Dirt Showdown low-resolution performance</strong></span></p> <p><span style="color: #000000;">For our gaming tests, we decided to run the games at 1366x768 resolution and at very low settings to take the graphics card out of the equation. In one way, you imagine this as what it would look like if you had infinitely powerful graphics cards in your system. As most games are not multi-threaded and are perfectly fine with a quad-core with Hyper-Threading, we fully expected the parts with the highest clock speeds to win all of our low-resolution, low-quality tests. No surprise, the Devil’s Canyon part at 4.4GHz private schools the 3.3GHz Haswell-E chip. And, no surprise, the 4GHz Ivy Bridge-E also eats the Haswell-E’s lunch and drinks its milk, too.</span></p> <p><span style="color: #333399;">Winner: Core i7-4790K</span></p> <p><span style="color: #000000;"><img src="/files/u154082/dirtultra.png" alt="dirt showdown ultra performance" title="dirt showdown ultra performance" width="620" height="475" /></span></p> <p><span style="color: #000000;"><strong>Dirt Showdown 1080p, ultra performance</strong></span></p> <p><span style="color: #000000;">To make sure we put everything in the right context, we also ran the Dirt Showdown at 1920x1080 resolution at Ultra settings. This puts most of the load on the single GeForce GTX 780 we used for our tests. Interestingly, we saw the Haswell-E with a slight edge over the Devil’s Canyon and Ivy Bridge-E parts. We’re not sure, but we don’t think it’s a very significant difference, but it’s still technically a win for Haswell-E.</span></p> <p><span style="color: #333399;">Winner: Core i7-5960X</span></p> <p><span style="color: #000000;"><img src="/files/u154082/hitmanlow.png" alt="hitman low" title="hitman low" width="620" height="502" /></span></p> <p><span style="color: #000000;"><strong>Hitman: Absolution, low quality, low performance&nbsp;</strong></span></p> <p><span style="color: #000000;">We did the same with Hitman: Absolution, running it at low resolution and its lowest settings. The Haswell-E came in about 12 percent slower the Devil’s Canyon part and 13 percent slower than the Ivy Bridge-E.&nbsp;</span></p> <p><span style="color: #333399;">Winner: Core i7-4960X</span></p> <p><span style="color: #000000;"><img src="/files/u154082/hitmanultra.png" alt="hitman ultra" title="hitman ultra" width="620" height="479" /></span></p> <p><span style="color: #000000;"><strong>Hitman: Absolution, 1080p, ultra quality</strong></span></p> <p><span style="color: #000000;">Again, we tick the settings to an actual resolution and quality at which people actually play. Once we do that, the gap closes slightly, with the Haswell-E trailing the Devil’s Canyon by about 8 percent and the Ivy Bridge-E by 9 percent. Still, these are all very playable frame rates and few could tell the difference.&nbsp;</span></p> <p><span style="color: #333399;">Winner: Core i7-4960X</span></p> <p><span style="color: #000000;"><img src="/files/u154082/tombraider.png" alt="tomb raider low" title="tomb raider low" width="620" height="465" /></span></p> <p><span style="color: #000000;"><strong>Tomb Raider, low quality, low resolution.</strong></span></p> <p><span style="color: #000000;">We did the same low quality, low resolution trick with Tomb Raider and while need to see 500 frames per second, it’s pretty much a wash here.&nbsp;</span></p> <p><span style="color: #333399;">Winner: Tie</span></p> <p><span style="color: #000000;"><img src="/files/u154082/tomraiderulti.png" alt="tomb raider ultra" title="tomb raider ultra" width="620" height="472" /></span></p> <p><span style="color: #000000;"><strong>Tomb Raider, 1080p, Ultimate</strong></span></p> <p><span style="color: #000000;">At normal resolutions and settings we were a little surprised, as the Haswell-E actually had a 15 percent advantage over the Devil’s Canyon CPU. We’re not exactly sure why, as the only real advantage we can see is memory bandwidth and large caches on the Haswell-E part. We seriously doubt it’s due to the number of CPU cores. The Haswell-E also has a very, very slight lead against the Ivy Bridge-E part, too. That’s not bad considering the clock penalty it’s running at.</span></p> <p><span style="color: #333399;">Winner: Core i7-5960X</span></p> <p><span style="color: #000000;"><img src="/files/u154082/metrolastlight.png" alt="metro last light low" title="metro last light low" width="620" height="503" /></span></p> <p><span style="color: #000000;"><strong>Metro Last Light, low resolution, low quality</strong></span></p> <p><span style="color: #000000;">In Metro Last light, at low settings it’s a wash between all of them.</span></p> <p><span style="color: #333399;">Winner: Tie</span></p> <p><span style="color: #000000;"><img src="/files/u154082/metroveryhigh.png" alt="metro last light high" title="metro last light high" width="620" height="502" /></span></p> <p><span style="color: #000000;"><strong>Metro Last Light, 1080p, Very High quality</strong></span></p> <p><span style="color: #000000;">Metro at high-quality settings mirrors that of Hitman: Absolution, and we think favors the parts with higher clock speeds. We should also note that none of the chips with the $500 graphics card could run Metro at 1080p at high-quality settings. That is, of course, you consider 30 to 40 fps to be “smooth.” We don’t. Interestingly, the Core i7-4690X was the overall winner.</span></p> <p><span style="color: #333399;">Winner: Core i7-4960X</span></p> <p><strong>Conclusion:</strong> If you skipped to the very last page to read the conclusion, you’re in the wrong place. You need to go back to page 4 to read our conclusions and what you should buy. And no, we didn’t do this to generate just one more click either though that would be very clever of us wouldn’t it?</p> http://www.maximumpc.com/haswell-e_review_2014#comments benchmarks cpu haswell e intel ivy bridge e maximum pc processor Review Specs News Reviews Features Fri, 29 Aug 2014 16:00:40 +0000 Gordon Mah Ung 28431 at http://www.maximumpc.com Broken Age Review http://www.maximumpc.com/broken_age_review_2014 <!--paging_filter--><h3>Two stories, tons of creativity, yummy ice cream, no grog</h3> <p>That’s fair advice for the half of you who will start out Broken Age in a miserable funk instead of a monster-filled fairy tale. At least, that’s how we felt when we initially began our trip through Tim Schafer’s imaginative title—the first half of a two-part, point-and-click adventure from the industry veteran whose previous credits stand well on their own within the genre: Day of the Tentacle, The Secret of Monkey Island, Full Throttle, et cetera.</p> <p>The game splits the two protagonists’ (seemingly) separate story lines right from the start. We started our journey with the boy, Shay, but found the initial ramp-up to his adventure a bit too convincing.</p> <p style="text-align: center;"><a class="thickbox" href="/files/u152332/2_small_26.jpg"><img src="/files/u152332/2_small_25.jpg" alt="It’s no Mystery Science Theater movie warning, that’s for sure." title="Broken Age" width="620" height="388" /></a></p> <p style="text-align: center;"><strong>It’s no Mystery Science Theater movie warning, that’s for sure.</strong></p> <p>Without spoiling too much of the plot, Shay is trapped on a spaceship that goes above and beyond to protect him from the harshness of growing up. Shay could not be any more apathetic to the idea of daily life with his “mother,” a benevolent, computerized AI of sorts, who washes him, feeds him his daily cereal, and sends him on “adventures” that end in hugs, piles of ice cream, and, most likely, a bout of depression.</p> <p>The other protagonist of this half-game, Vella, presents a more compelling story line. In this case, you’re playing the classic damsel in distress. Rather than being eaten by a giant monster as part of her town’s sacrificial ritual to avoid destruction, she decides to go on a one-woman crusade to slay said monster herself.</p> <p>While Vella’s story line is a bit more action-packed—or at least, feels more so as a result of its classic slay-the-dragon-like premise—we actually found ourselves more proud of our experience in Shay’s adventure. Our favorite moment involved trying to find a way to “kill” our character, for lack of a better way to say it, in order to see if his daily monotony could be averted somehow. Spoiler: It can.</p> <p>That’s the most challenging example of the game’s puzzles that we could come up with, as Broken Age feels perfectly balanced between “breeze on by” and “consult game FAQs” for its overall difficulty. You get just enough quirky items to keep you thinking about what goes where without feeling overwhelmed with options—this isn’t a 20-item-inventory, combine-every-gizmo kind of adventure title.</p> <p>While Broken Age features no hint system, which might frustrate those looking for an extra boost or two in some head-scratching moments, you do have the option to switch between the two separate”story lines at a moment’s notice. Think Day of the Tentacle, only, your actions in the two stories don’t affect each other—a somewhat curious oversight that we hope developer Double Fine Productions changes up in the game’s second half.</p> <p>There’s no real point to spending much time talking about the game’s graphics, as you’ll fall in love with the beautiful visuals the moment you start adventuring. Kudos to Broken Age’s original orchestration as well—it’s the bread keeping the delicious presentation together. Sharp writing, endless wit, and excellent characterization (with similarly awesome voice talent) all work in tandem to deliver a welcome arrival to a genre whose blockbuster titles are not always at the forefront of gamers’ minds.</p> <p>You won’t forget Broken Age; in fact, we think you’ll be clamoring for quite a while to see how chapter one’s big cliffhanger ends up. More, Tim Schafer! More!</p> <p><strong>$25,</strong> <a href="http://www.brokenagegame.com/">www.brokenagegame.com</a><strong><a href="http://www.brokenagegame.com/">,</a> ESRB: n/a</strong></p> http://www.maximumpc.com/broken_age_review_2014#comments Broken Age maximum pc May issues 2014 Software Software Reviews Wed, 20 Aug 2014 14:57:20 +0000 David Murphy 28383 at http://www.maximumpc.com OCZ Vertex 460 240GB Review http://www.maximumpc.com/ocz_vertex_460_240gb_review <!--paging_filter--><h3>Rumors of its death were greatly exaggerated</h3> <p>That last time we heard from OCZ was back before the end of 2013, when the company was in the grips of bankruptcy and nobody was sure what its future held. Fast forward to March 2014, and things are looking rather good for the formerly beleaguered company, much to everyone’s surprise. Rather than simply dissolve and fade away like we had feared, the company has been acquired by storage behemoth Toshiba, and is now operating as an independent subsidiary.</p> <p style="text-align: center;"><a class="thickbox" href="/files/u152332/vertex460_lrg_small_0.jpg"><img src="/files/u152332/vertex460_lrg_small.jpg" alt="OCZ’s new drive has a more subdued, corporate look to it, thanks to a takeover by “the man.”" title="OCZ Vertex 460 240GB" width="620" height="449" /></a></p> <p style="text-align: center;"><strong>OCZ’s new drive has a more subdued, corporate look to it, thanks to a takeover by “the man.”</strong></p> <p>The best news is OCZ’s NAND-acquisition troubles are seemingly a thing of the past, as Toshiba is one of the world’s largest manufacturers of NAND. So, it is no surprise that the first drive we’re seeing from the new venture is essentially a reborn Vector drive, only with Toshiba NAND flash. Dubbed the Vertex 460, this “new” drive blends the company’s proprietary Barefoot 3 controller found on its high-end Vector drives with Toshiba’s 19nm MLC NAND flash, so it’s ditching the Micron NAND it used previously. The result is basically a slight watering-down of its Vector 150 drive in order to make it more affordable and consumer-friendly. It also needed to bring its Barefoot 3 controller over to its mainstream line of Vertex-branded drives, so this drive accomplishes that feat, as well.</p> <p>In many ways, the Vertex 460 is very similar to the company’s recent Vector 150 drive, the only difference being the Vector has a five-year warranty and has a higher overall endurance rating to reflect its use of binned NAND flash. The Vertex 460 is no slouch, though, and is rated to handle up to 20GB of NAND writes per day for three years. The drive also utilizes over-provisioning, so 12 percent of the drive is reserved for NAND management by the Barefoot 3 controller. Though you lose some capacity, you gain longer endurance and better performance, so it’s a worthwhile trade-off. The Vertex 460 also offers hardware encryption support, which is very uncommon for a mainstream drive, and though we’d never use it, it’s nice to have options. Otherwise, its specs are par for the course in that it’s a 7mm drive and is available in 120GB, 240GB, and 480GB flavors. It’s also bundled with a 3.5-inch bay adapter as well as a copy of Acronis True Image, which is appreciated.</p> <p>When we strapped the Vertex to our test bench, we saw results that were consistently impressive. In every test, the Vertex 460 was very close to the fastest drives in its class, and in all scenarios it’s very close to saturating the SATA bus, so it’s not really possible for it to be any faster. It had no problem handling small queue depths of four commands in ATTO, and held its own with a 32 queue depth in Iometer, too. It was a minute slower than the Samsung 840 EVO in our Sony Vegas test, which writes a 20GB uncompressed AVI file to the drive, but also much faster than the Crucial M500 in the same test. Overall, there were no weak points whatsoever in its performance, but it is not faster than the Samsung 840 EVO, and its OCZ Toolbox software utility is extremely rudimentary compared to the Samsung app. Though the Vertex 460 is an overall very solid drive, it doesn’t exceed our expectations in any particular category. In other words, it’s a great SSD, but not quite Kick Ass.</p> <p><strong>$190,</strong> <a href="http://ocz.com/">www.ocz.com</a></p> http://www.maximumpc.com/ocz_vertex_460_240gb_review#comments Hard Drive Hardware HDD May issues 2014 OCZ Vertex 460 240GB Review solid state drive ssd Reviews Wed, 20 Aug 2014 14:16:12 +0000 Josh Norem 28382 at http://www.maximumpc.com Nvidia Shield Tablet Review http://www.maximumpc.com/nvidia_shield_tablet_review_2014 <!--paging_filter--><h3>Updated: Now with video review!&nbsp;</h3> <p>Despite its problems, we actually liked <a title="Nvidia Shield review" href="http://www.maximumpc.com/nvidia_shield_review_2013" target="_blank">Nvidia’s original Shield Android gaming handheld</a>. Our biggest issue with it was that it was bulky and heavy. With rumors swirling around about a Shield 2, we were hoping to see a slimmer, lighter design. So consider us initially disappointed when we learned that the next iteration of Shield would just be yet another Android tablet. Yawn, right? The fact of the matter is that the Shield Tablet may be playing in an oversaturated market, but it’s still great at what it sets out to be.</p> <p><iframe src="//www.youtube.com/embed/dGigsxi9-K4" width="620" height="349" frameborder="0"></iframe></p> <p style="text-align: center;"><strong>We've updated our review to include the video review above.</strong></p> <p>At eight inches, the Shield Tablet features a gorgeous 1900x1200 display, which shares the same resolution as Google’s flagship <a title="nexus 7 review" href="http://www.maximumpc.com/google_nexus_7_review_2013" target="_blank">Nexus 7</a> tablet. At 13.1 ounces, the Shield Tablet is about three ounces heavier than the Nexus 7 but still a lot lighter than the original’s 1 lb. 4.7 ounces.&nbsp;</p> <p>Part of the weight increase with the Shield Tablet over the Nexus 7 is due to the extra inch that you’re getting from the screen, but also because the Shield Tablet is passively cooled and has an extra thermal shield built inside to dissipate heat. It’s a little heavier than we like, but isn’t likely to cause any wrist problems. On the back of the Shield is an anti-slip surface and a 5MP camera, and on the front of the tablet is a front-facing 5MP camera and two front-facing speakers. While the speakers are not going to blow away dedicated Bluetooth speakers, they sound excellent for a tablet. In addition to the speakers, the Shield Tablet has a 3.5mm headphone jack up at the top. Other ports include Micro USB, Mini HDMI out, and a MicroSD card slot capable of taking up to 128GB cards. Buttons on the Shield include a volume rocker and a power button, which we found to be a little small and shallow for our liking.</p> <p style="text-align: center;"><img src="/files/u154082/shield_tablet_exploded_view_black_bckgr.jpg" alt="Nvidia Shield Tablet guts" title="Nvidia Shield Tablet guts" width="620" height="349" /></p> <p style="text-align: center;"><strong>The guts of the Nvidia Shield Tablet.</strong></p> <p>All of this is running on the latest version of Android KitKat (4.4). Nvidia says that it will update the tablet to Android L within a few weeks of Google’s official release. If Nvidia’s original Shield is any indication of how well the company keeps up with OS updates, you should be able to expect to get the latest version of Android after a couple of weeks, if not a months, after release. Regardless, the Shield Tablet is running a pretty stock version of Android to begin with, the main difference being that Nvidia has pre-loaded the tablet with its Shield Hub, which is a 10-foot UI used to purchase, download, and launch games.</p> <p>Arguably, the real star of the tablet is Nvidia’s new Tegra K1 mobile superchip. The 2.2GHz quad-core A15 SOC features Nvidia’s Kepler GPU architecture and 192 CUDA cores along with 2GB of low-power DDR3. K1 supports many of the graphical features commonplace in GeForce graphics cards, including tesselation, HDR lighting, Global illumination, subsurface scattering, and more.</p> <p>In our performance benchmarks, the K1 killed it. Up until now, the original Shield’s actively cooled Tegra 4 is arguably one of the most, if not <em>the</em> most, powerful Android SOC on the market, but the K1 slaughters it across the board. In Antutu and GeekBench benchmark, we saw modest gains of 12 percent to 23 percent in Shield vs. Shield Tablet action. But in Passmark and GFX Bench’s Trex test, we saw nearly a 50 percent spread, and in 3DMark’s mobile Icestorm Unlimited test, we saw an astounding 90 percent advantage for the Shield Tablet. This is incredible when you consider that the tablet has no fans and a two-watt TDP. Compared to the second-gen Nexus 7, the Shield Tablet benchmarks anywhere from 77 percent to 250 percent faster. This SOC is smoking fast.</p> <p>In terms of battery life, Nvidia claims you’ll get 10 hours watching/surfing the web and about five hours from gaming with its 19.75 Wh battery. This is up 3.75 Wh up from Google’s Nexus 7 equivalent, and from our experiential tests, we found those figures to be fairly accurate if not a best-case scenario. It will pretty much last you all day, but you'll still want to let it sip juice every night.</p> <p style="text-align: center;"><img src="/files/u154082/shield_tablet_shield_controller_war_thunder.jpg" alt="Shield Tablet review" title="Shield Tablet review" width="620" height="343" /></p> <p style="text-align: center;"><strong>The new wireless controller uses Wi-Fi Direct instead of Bluetooth for lower latency.</strong></p> <p>Of course, if you’re going to game with it, you’re going to need Nvidia’s new wireless Shield Controller. Sold separately for $60, the 11.2-ounce Shield Controller maintains the same button layout as the original Shield controller, but feels a lot lighter and is more comfortable to hold. While most Android game controllers operate over Bluetooth, Nvidia opted to go with Wi-Fi Direct, stating that it offers 2x faster response time and more bandwidth. The extra bandwidth allows you to plug a 3.5mm headphone into the controller and also allows you to link up to four controllers to the device, which is an appreciated feature when you hook up the tablet to your HDTV via the Shield Tablet’s <a title="shield console mode" href="http://www.maximumpc.com/nvidia_sweetens_shield_console_android_442_kitkat_price_drop_199_through_april" target="_blank">Console Mode</a>. Other unique features of the controller include capacitive-touch buttons for Android’s home, back, and play buttons. There’s also a big green Nvidia button that launches Shield Hub. The controller also has a small, triangle-shaped clickable touch pad which allows you to navigate your tablet from afar. One quibble with it is that we wish the trackpad was more square, to at least mimic the dimensions of the tablet; the triangle shape was a little awkward to interface with. Another problem that we initially had with the controller was that the + volume button stopped working after a while. We contacted Nvidia about this and the company sent us a new unit, which remedied the issue. One noticeable feature missing from the controller is rumble support. Nvidia said this was omitted on the original Shield to keep the weight down; its omission is a little more glaring this time around, however, since there's no screen attached to the device.</p> <p>The controller isn’t the only accessory that you’ll need to purchase separately if you want to tap into the full Shield Tablet experience. To effectively game with the tablet, you’ll need the Shield Tablet cover, which also acts as a stand. Like most tablets, a magnet in the cover shuts off the Shield Tablet when closed, but otherwise setting up the cover and getting it to act as a stand is initially pretty confusing. The cover currently only comes in black, and while we’re generally not big on marketing aesthetics, it would be nice to have an Nvidia green option to give the whole look a little more pop. We actually think the cover should just be thrown in gratis, especially considering that the cheapest 16GB model costs $300. On the upside though, you do get Nvidia’s new passive DirectStylus 2 that stows away nicely in the body of the Shield Tablet. Nvidia has pre-installed note-writing software and its own Nvidia Dabbler painting program. The nice thing about Dabbler is that it leverages the K1’s GPU acceleration so that you can virtually paint and blend colors in real time. There’s also a realistic mode where the “paint” slowly drips down the virtual canvas like it would in real life.&nbsp;</p> <p style="text-align: center;"><img src="/files/u154082/shield_tablet_shield_controller_trine2_0.jpg" alt="Shield tablet review" title="Shield tablet review" width="620" height="404" /></p> <p style="text-align: center;"><strong>The Shield Controller is a lot lighter and less blocky than the original Shield Portable.</strong></p> <p>But that’s probably not why you’re interested in the Shield Tablet. This device is first and foremost a gaming tablet and even comes with a free Android copy of Trine 2. Trine 2 was originally a PC game and it’s made a great transition to the Shield Tablet. While the game was never known to be a polygon pusher, it looks just as good as it ever did on its x86 debut.&nbsp;</p> <p>With gaming as the primary driver for Shield Tablet, you may wonder why Nvidia didn’t bundle its new controller. The company likely learned from Microsoft’s mistake with Kinect and the Xbox One: Gamers don’t like to spend money and getting the price as low as possible was likely on Nvidia’s mind. Of course, not everyone may even want a controller, with the general lack of support for them in games. Nvidia says there are now around 400 Android titles that support its controller, but that’s only a small percentage of Android games and the straight truth is that the overwhelming majority of these games are garbage.&nbsp;</p> <p>Nvidia is making a push for Android gaming, however. The company worked with Valve to port over Half Life 2 and Portal to the Shield and they look surprisingly fantastic and are easily the two prettiest games on Android at the moment. Whether Android will ever become a legitimate platform for hardcore gaming is anyone’s guess, but at least the Shield Tablet will net you a great front seat if the time ever arises.</p> <p>Luckily, you won’t have to rely solely on the Google Play store to get your gaming fix. Emulators run just as well here as they did on the original Shield and this iteration of Shield is also compatible with Gamestream, which is Nvidia’s streaming technology that allows you to stream games from your PC to your Shield. Gamestream, in theory, lets you play your controller-enabled PC games on a Shield.</p> <p>At this point, Nvidia says Gamestream supports more than 100 games such as Batman: Arkham Origins and Titanfall from EA’s Origin and Valve’s Steam service. The problem, though, is that there are hundreds more games on Steam and Origin that support controllers—but not the Shield Tablet’s controller. For example, Final Fantasy VII, a game that we couldn’t get to work with the original Shield, still isn't supported even though it works with an Xbox controller on the PC. When Gamestream does work, however, it’s relatively lag-free and kind of wonderful. The one caveat here is that you’ll have to get a 5GHz dual-band router to effectively get it working.&nbsp;</p> <p style="text-align: center;"><iframe src="//www.youtube.com/embed/rh7fWdQT2eE" width="620" height="349" frameborder="0"></iframe></p> <p style="text-align: center;"><strong>Nvidia Shield Video demo.</strong></p> <p>Would we buy the Shield Tablet if we owned the original Shield (now renamed the Shield Portable)? Probably not. If we were looking for a new tablet and top-notch gaming performance was on the checklist, the Shield Tablet is easily the top contender today. We’d take it over the second-gen Nexus 7 in a heartbeat. While we understand why Nvidia decided to separate the cover and controller to keep the prices down and avoid the Kinect factor, we think a bundled package with a small price break as an alternative would have been nice. All things considered though, consider us surprised. The Shield Tablet is pretty dang cool.&nbsp;</p> <p><strong>$300</strong></p> <p><em><strong>Update:</strong> The original article incorrectly labled the Shield Portable benchmarks with the Nexus 7 figures. The issue has been resolved and both benchmark charts are listed below.&nbsp;</em></p> http://www.maximumpc.com/nvidia_shield_tablet_review_2014#comments android Google Hardware KitKat maximum pc nvidia portable Review shield tablet wireless controller News Reviews Tablets Mon, 18 Aug 2014 21:36:57 +0000 Jimmy Thang 28263 at http://www.maximumpc.com Xidax M6 Mining Rig Review http://www.maximumpc.com/xidax_m6_mining_rig_review_2014 <!--paging_filter--><h3>A gaming rig that pays for itself</h3> <p>Exotic car paint, multiple GPUs, and custom-built chassis’ be damned, boutique PC builder <a title="xidax" href="http://www.maximumpc.com/tags/Xidax" target="_blank">Xidax</a> thinks it has the sexiest sales pitch on the planet with its <strong>M6 Mining Rig</strong>: It pays for itself! Now, we can’t say this PC is basically “free” because it ain’t that, but Xidax says by using the box’s spare GPU cycles to mine for crypto-currency, this baby would be paid off in about four months. To be honest, it’s not something we’ve ever considered, as we’ve seen gaming rigs, and we’ve seen coining rigs, but never in the same box. It seems like a solid idea though, as the system can game during the day, then mine at night to help cover its cost.</p> <p style="text-align: center;"><a class="thickbox" href="/files/u152332/xidax_guts13979_small_0.jpg"><img src="/files/u152332/xidax_guts13979_small.jpg" alt="The Xidax M6 Mining Rig comes set up with everything you need to start mining crypto-currancy almost right out of the box." title="Xidax M6 Mining Rig" width="620" height="676" /></a></p> <p style="text-align: center;"><strong>The Xidax M6 Mining Rig comes set up with everything you need to start mining crypto-currancy almost right out of the box.</strong></p> <p>The system’s specs include a 3.4GHz Core i5-4670K with 16GB of RAM, a Corsair RM 850 PSU, closed-loop liquid cooler, 250GB Samsung 840 EVO SSD, 1TB WD Black, and a pair of Sapphire Radeon R9 290X cards. In application performance, it’s pretty pedestrian with its stock-clocked Core i5-4670K. Why not something more badass? Xidax says it weighed hardware choices carefully because the pricier the hardware, the longer it takes to pay off with crypto-coins. The Radeons are a wise choice, as they offer about twice the performance of Nvidia’s fastest GPUs in mining applications. Gaming is also quite excellent (obviously, for a two-card system), and its mining performance is impressive at 1.7 to 1.8 Kilohashes per second. (Hashes of the kilo/mega/giga variety are the units of measurement for mining productivity.)</p> <p>Xidax ships the PC ready to start mining operations almost right out of the box, which is normally a daunting task. It also includes a Concierge (or should we say coincierge) service that has a Xidax rep remotely connect to the rig and do a final tune on the box for maximum mining performance. On this particular machine, it came ready to mine for Doge Coins and was forecast to make about $21.60 a day, or $670 a month, on a 24/7 schedule—including electricity costs.</p> <p>What’s the catch? There are a few. First, it’s loud when mining. In fact, it’s so loud that you won’t be able to stand being in the same room with it. Second, you can’t do anything with it while it’s mining because all GPU resources are pegged to the max. Third, crypto-currency can be volatile. Bitcoin saw its value see-saw from $130 to $1,242 and then back to $455 and $900 in just four months. It could all go kaput in a few months, or who knows—the government might even step in and ruin the fun.</p> <p>Considering its performance outside of mining, the M6 Mining Rig is pricey at $3,000. However, the price includes a lifetime warranty on parts and service except for the GPUs. Those carry a five-year warranty, which is still surprisingly good, considering that board vendors are already making noises that they don’t want to eat the cost of dead boards killed by mining. Xidax says it will cover them, though. And—again—it pays for itself, right?</p> <p>That’s ultimately the appeal of the M6 Gaming Rig, but it has to be carefully considered by potential buyers. After all, anything that sounds too good to be true usually is, but then again, it is a powerful gaming PC that could theoretically pay for itself in a few months. And even if the market blew up, at least you’d still have a formidable gaming PC rather than just standing there with your RAM sticks in one hand. And if it works out, whoa baby, you just got a PC for free! –</p> <p><strong>$3,000,</strong> <a href="http://www.xidax.com/">www.xidax.com</a></p> <p><img src="/files/u154082/xidax_benchmarks.png" alt="xidax benchmarks" title="xidax benchmarks" width="620" height="277" /></p> http://www.maximumpc.com/xidax_m6_mining_rig_review_2014#comments april issues 2014 bitcoin dogecoin Hardware maximum pc Review xidax m6 mining computer Reviews Systems Wed, 06 Aug 2014 16:42:51 +0000 Gordon Mah Ung 28234 at http://www.maximumpc.com Intel 730 Series SSD 480GB Review http://www.maximumpc.com/intel_730_series_ssd_480gb_review <!--paging_filter--><h3>An overclocked enterprise SSD, priced accordingly</h3> <p><a title="intel" href="http://www.maximumpc.com/tags/Intel_0" target="_blank">Intel</a> has largely been absent from the high-end SSD market for many years, which has been a real head-scratcher, considering the original X-25M’s dominance back in 2009. That all changes this month with the release of its all-new <strong>730 series SSD</strong>. It springs from the loins of its data center SSDs, which use validated NAND and Intel’s enterprise-level controller technology. To emphasize this heritage, Intel isn’t bragging about the drive’s overall speed, but instead notes the drive is rated to handle up to 70GB of writes per day, which is higher than any other SSD on the market by a huge margin. It features capacitors to protect data being written in case of a power outage, which is an unusual but not unprecedented feature on a consumer SSD. Intel also backs the drive with a five-year warranty.</p> <p style="text-align: center;"><a class="thickbox" href="/files/u152332/ww_13_18_small_0.jpg"><img src="/files/u152332/ww_13_18_small.jpg" alt="Intel’s new flagship SSD is validated for a whopping 70GB of writes per day." title="Intel 730 Series SSD 480GB" width="620" height="437" /></a></p> <p style="text-align: center;"><strong>Intel’s new flagship SSD is validated for a whopping 70GB of writes per day.</strong></p> <p>To create the 730 Series, Intel has basically taken the NAND flash and controller from its data center–oriented S3700 SSD and bumped up the clock and interface speeds. If you recall the “SSD overclocking” demo Intel held at Pax last year, this is the result, though Intel decided against letting consumers overclock the drive. Instead, it did the overclocking at the factory so that the drives could be validated at those speeds. To drive home the point that this is an SSD made for enthusiasts, Intel has even adorned it with a sweet-looking Skulltrail badge.</p> <p>The drive is a 7mm unit, so it will fit inside an ultrabook, but is available only in 240GB and 480GB capacities. It’s odd that it’s not available in 750GB or higher capacities, but our guess is Intel is afraid of the sky-high sticker price that such a drive would require; the two capacities it’s offering are priced very&nbsp; high at $250 and $490, respectively. The drive features Intel’s 20nm MLC NAND and its own third-generation controller. It’s ditched SandForce, along with all the other SSD makers in the business. One interesting note is that since this is an enterprise drive, it essentially doesn’t have a “low-power state,” so it’s not intended for mobile usage. Also, it consumes 5W under load, which is double the consumption of even a 7,200rpm mobile hard drive.</p> <p>When we strapped the 730 Series drive to our test bench, we saw results that were a bit slower overall than we expected. It topped the charts in AS SSD, which measures read and write speeds of incompressible data, but the Intel drive was only a smidge faster than most, and not by enough to make it stand out, as they are all very fast. It was a bit slower than average in straight-line sequential read speeds, topping out at 468MB/s for reads and 491MB/s for writes. While this is still plenty fast, it’s a bit short of the 550MB/s Intel claims the drive is capable of, which is totally saturating the SATA 6Gb/s interface.</p> <p>It was also oddly slow in the ATTO benchmark, which has a queue depth of four and is a “best case scenario” for most drives. It scored just 373MB/s for 64KB-read speeds, compared to 524MB/s for the Samsung 840 Pro. We ran the test several times to verify, so it’s not an aberration. It placed mid-pack in PCMark Vantage, but was slower than its competition in our real-<br />world Sony Vegas test, where we write a 20GB uncompressed AVI file to the drive.</p> <p>Overall, this drive is a bit of a conundrum. We have no doubt it’s reliable, as Intel has always been strong in that regard and this drive is full of safety-oriented features. But is it more reliable than a Samsung 840 Pro for the average consumer? We doubt it, and therefore the drive’s extra-high price tag doesn’t make much sense. If Intel realizes it’s no longer the only game in town and adjusts the price a bit, it’ll be a much more competitive drive, but as it stands, we must give it a so-so verdict of 8.</p> <p><strong>$490,</strong> <a href="http://www.intel.sg/content/www/xa/en/homepage.html">www.intel.com</a></p> http://www.maximumpc.com/intel_730_series_ssd_480gb_review#comments Hardware Intel 730 Series SSD 480GB maximum pc May issues 2014 solid state drive Reviews SSD Wed, 06 Aug 2014 16:36:43 +0000 Josh Norem 28289 at http://www.maximumpc.com Gigabyte Radeon R9 290X OC Review http://www.maximumpc.com/gigabyte_radeon_r9_290x_oc_review <!--paging_filter--><h3>As good as it gets, if you can find one to buy</h3> <p>Aftermarket Radeon R9 290X GPUs are beginning to make the rounds, and this month we had a WindForce-cooled behemoth from <a title="gigabyte" href="http://www.maximumpc.com/tags/Gigabyte" target="_blank">Gigabyte</a> strutting its stuff in the lab. Unlike last month’s <a title="sapphire tri x r9 290x" href="http://www.maximumpc.com/sapphire_tri-x_radeon_r9_290x_review" target="_blank">Sapphire Tri-X R9 290X</a>, this board features a custom PCB in addition to the custom cooler, whereas the Sapphire slapped a huge cooler onto the reference design circuit board. Theoretically, this could allow for higher overclocks on the Gigabyte due to better-quality components, but more on that later.</p> <p style="text-align: center;"><a class="thickbox" href="/files/u152332/windforce14052_small_0.jpg"><img src="/files/u152332/windforce14052_small.jpg" alt="Unlike the reference design, Gigabyte’s R9 290X is cool, quiet, and overclockable." title="Gigabyte Radeon R9 290X OC" width="620" height="476" /></a></p> <p style="text-align: center;"><strong>Unlike the reference design, Gigabyte’s R9 290X is cool, quiet, and overclockable.</strong></p> <p>This is the overclocked version of the card, so it clocks up to 1,040MHz under load, which is a mere 40MHz over stock. These boards always have conservative overclocks out of the box, though, and that is by no means the final clock speed for this card. We’ve covered its WindForce cooler in past reviews, so we won’t go into all the details, but it’s a three-fan cooler that only takes up two PCIe slots and uses six heat pipes with inclined heatsinks to better dissipate the warm. It’s good for 450W of heat dispersal, according to Gigabyte, and since the R9 290X is roughly a 300W card (AMD has never given a TDP for this particular model for some reason), the WindForce cooler should be more than up to the job.</p> <p>Like all Radeon R9 290X boards, this sucker is big and long, measuring 11.5 inches. Gigabyte recommends you use at least a 600W power supply with it, and it sports two dual-link DVI ports for 2560x1600 gaming, as well as HDMI 1.4 and DisplayPort 1.2a if you want to run 4K. The card comes bundled with a free set of headphones. It used to include a free copy of Battlefield 4, but the company told us it was no longer offering the game bundle because it had run out of coupons. The MSRP of the board is $620, but some stores had it for $599 while others marked it up to $700.</p> <p>Once we had this Windy Bad Boy in the lab, we were very curious to compare it to the Sapphire Tri-X R9 290X we tested last month. Since both cards feature enormous aftermarket coolers, have the exact same specs and clocks, and are roughly the same price, we weren’t surprised to find that they performed identically for the most part.</p> <p>If you look at the benchmark chart, in every test the two cards are almost exactly the same—the only exception being Metro, but since that’s a PhysX game, AMD cards can get a bit wonky sometimes. In every other test, the two cards are within a few frames-per-second difference, making them interchangeable. Both cards also run in the mid–70 C zone under load, which is 20 C cooler than the reference design. We were able to overclock both cards to just a smidge over 1,100MHz, as well.</p> <p>“Okay,” you are saying to yourself. “I’m ready to buy!” Well, that’s where we run into a small problem. Gigabyte’s MSRP for this card is $620—the same as the Sapphire Tri-X card—but at press time, the cheapest we could find it for was $700 on Newegg. We can’t ding Gigabyte for Newegg’s pricing, but it’s a real shame these R9 290X cards are so damned expensive.</p> <p><strong>$620,</strong> <a href="http://www.gigabyte.us/">www.gigabyte.us</a></p> http://www.maximumpc.com/gigabyte_radeon_r9_290x_oc_review#comments Air Cooling amd april issues 2014 Gigabyte Radeon R9 290X OC gpu graphics card Hardware maximum pc Review Reviews Tue, 05 Aug 2014 19:52:42 +0000 Josh Norem 28227 at http://www.maximumpc.com NZXT H440 Review http://www.maximumpc.com/nzxt_h440_review <!--paging_filter--><h3>Remarkably clean, and limited, too</h3> <p>We love the fact that <a title="nzxt" href="http://www.maximumpc.com/tags/nzxt" target="_blank">NZXT</a> bills this semi-silent-themed case as a “hassle-free experience.” We wonder if the company was using the same case that we were, because we encountered quite a bit of hassle building a standard configuration into this smaller-than-usual chassis.</p> <p>For starters, the case itself ships with no printed manual—at least, ours didn’t. We only hope that’s an oversight with our early review unit instead of a standard feature of the chassis itself, because there are definitely some features of the <a title="h440" href="http://www.maximumpc.com/nzxt_h440_case_ditches_optical_drive_bays_cleaner_look" target="_blank">H440</a> that warrant a bit of instruction, especially for neophyte builders.</p> <p style="text-align: center;"><a class="thickbox" href="/files/u152332/h440_blk_main_24x32in_small_0.jpg"><img src="/files/u152332/h440_blk_main_24x32in_small.jpg" alt="The H440 is the first case we’ve tested that doesn’t have 5.25-inch drive bays. " title="NZXT H440" width="620" height="578" /></a></p> <p style="text-align: center;"><strong>The H440 is the first case we’ve tested that doesn’t have 5.25-inch drive bays. </strong></p> <p>Case in point: There are absolutely zero 5.25-inch bays to be found on the H440, which is a good thing to know before you start attempting to pry off the H440’s front (Dremel in hand). We know, we know, the optical drive is dead, long live the optical drive—but is it too soon? To be honest, there’s an upstart contingent here at Maximum PC who think it’s a plus, while some cranky old farts think it’s a minus. Additionally, installing the power supply might evoke a bout of head-scratching at first, as there’s seemingly no way to just stuff it into the chassis thanks to how it’s been compartmentalized on the case’s bottom. This does build on the case’s motto of “remarkably clean,” though, by hiding your messy PSU cabling.</p> <p>This leads us into one of our major gripes with this chassis: There’s a lot of screwing. We pretty much pulled out the thumbscrews in the case’s side, which are supposedly designed to not do that. Beyond that, you have to unscrew a panel to slide the power supply in, you have to unscrew the standard PCI slot covers for any devices you want to install, and—most frustratingly—you have to first unscrew the case’s steel drive trays (up to six total) just for the privilege of being able to screw in your hard drive. Clean, yes. Toolless, no.</p> <p>The case feels a bit small on the inside, but it adequately supported our standard test setup (including an Nvidia GTX 480 video card) without any cramming or wedging. We like how the case’s three rubberized cable-routing holes fit perfectly with a standard video card setup—when using the top-most PCI Express x16 slot on our ATX motherboard, our video card didn’t block any of the much-needed routing holes.</p> <p>That said, cable routing is a bit of a challenge in the H440. There’s already not that much room between the rear of the motherboard tray and the case’s side panel. Amplifying the claustrophobia is a layer of soundproofing foam adhered to the side panel. We love that NZXT cares so much about our ears, but it makes for a less-than-pleasant smashing of cables against the case’s side (especially since there’s only one provided hole for power-supply cables to route through otherwise). Cable-management options feel more constrained by this case than others we’ve tested.</p> <p>The foam surrounding the case’s insides has quite a bit of work in store for it, too. No fewer than four of NZXT’s next-gen case fans grace the inside of the chassis: three 12cm fans on the front and one 14cm fan on the back. When we fired up the system with no components inside it, the soundproof-themed case was a bit audible. A full system only adds to the din, and while we appreciate NZXT’s efforts toward keeping the volume dial at a three instead of an eleven, it seems to be a bit of a lost cause.</p> <p>NZXT seems to think this case is perfect for liquid cooling. For some all-in-one setups, sure; for customized loops, you’re going to be in for something of a tubing nightmare. Best of luck!</p> <p><strong>$120,</strong> <a href="http://www.nzxt.com/">www.nzxt.com</a></p> http://www.maximumpc.com/nzxt_h440_review#comments april issues 2014 Hardware maximum pc Review Cases Reviews Tue, 05 Aug 2014 19:46:55 +0000 David Murphy 28236 at http://www.maximumpc.com Cooler Master Nepton 280L Review http://www.maximumpc.com/cooler_master_nepton_280l_review <!--paging_filter--><h3>Not quite god, but still Herculean</h3> <p>In the world of CPUs, closed-loop liquid coolers (CLCs) seem to be standard-issue for enthusiasts these days. They give you higher overclocking headroom than even the most expensive and beefy air coolers, and they can operate more quietly. However, we haven’t seen many with radiators as large as 280mm—just the <a title="kraken x60" href="http://www.maximumpc.com/nzxt_kraken_x60_review_2013" target="_blank">NZXT Kraken X60</a> and the <a title="Corsair h110 review" href="http://www.maximumpc.com/corsair_h110_review" target="_blank">Corsair H110</a> come to mind—so we were eager to run the <strong>Cooler Master Nepton 280L</strong> through its paces.</p> <p style="text-align: center;"><a class="thickbox" href="/files/u152332/coolermaster14036_small_0.jpg"><img src="/files/u152332/coolermaster14036_small.jpg" alt="The Nepton features a massive 280mm radiator." title="Cooler Master Nepton 280L" width="620" height="559" /></a></p> <p style="text-align: center;"><strong>The Nepton features a massive 280mm radiator.</strong></p> <p>Many hardware vendors have chosen to license their CLC designs from Asetek, whose patents go back quite a way. With the 280L, however, Cooler Master decided to roll its own with a custom pump. It’s definitely larger than usual. The tubes coming out of it are sleeved with a material called FEP, which is similar to Teflon and designed to slow the rate of evaporation inside the loop. That’s an important factor for a cooler that’s not designed to be refilled. Cooler Master is also using its own JetFlo fans, designed for high static pressure. This feature is needed to penetrate into the fins of the radiator, and the 140mm version of the JetFlo is making its debut here (the radiator can also fit 120mm fans).</p> <p>Pump installation is pretty straightforward. First, we screwed in a small bracket to each side of the cold plate. Then, since our LGA 2011 motherboard has an integrated CPU backplate, we just attached four bundled screws to that, set the cold plate on top the CPU, and added four fasteners to fix the cold plate’s brackets to the four screws in the backplate. The fasteners only take a flat-bladed screwdriver, oddly, but they went in smoothly. The radiator screws also come in two sets of eight, differing only a couple of millimeters in length, so it took a minute to separate each type. It would have been better had they been clearly differentiated.</p> <p>The pump, plugged into our board’s secondary CPU fan header, operated at a steady 6,300rpm, which is unusually high. We checked with Cooler Master, and the company agreed. We used a Zalman Fanmate to manually tune it down to 5,000rpm, at which point the pump noise didn’t stand out. Despite a loss of 1,300rpm, temps only went up about 1 C during our load test, indicating that the additional speed offered minimal improvement anyway. We then plugged the pump into a chassis fan header without the Fanmate, and it leveled off at 4,500rpm.</p> <p>Of course, there are caveats. A large percentage of cases will not accommodate a 280mm radiator; either the dimensions are too small or the fan mounts are not sized for it. This is not the radiator’s fault, though, so we can’t really deduct points for it. It’s just something that you have to be aware of. Also, the thick FEP tubes are not especially flexible. The radiator screws have unusually open heads, requiring an uncommonly large bit to avoid stripping. Lastly, the pump is too loud without some fiddling.</p> <p>These are fairly minor issues that all have workarounds, though. Considering the Nepton’s top-tier cooling performance, reasonably low noise levels, and ease of installation, its quirks don’t stick out in the end. Its load temperatures were notably lower than anything else we’ve tested and may allow you to squeeze another couple-hundred MHz out of an overclock. The Nepton is an indisputable upgrade from Cooler Master’s older Seidon series.</p> <p><strong>$125 (street),</strong> <a href="http://us.coolermaster.com/">www.coolermaster-usa.com</a></p> http://www.maximumpc.com/cooler_master_nepton_280l_review#comments Air Cooling april issues 2014 clc closed loop cooler Cooler Master Nepton 280L cpu Hardware maximum pc water cooling Reviews Tue, 05 Aug 2014 19:35:45 +0000 Tom McNamara 28218 at http://www.maximumpc.com Seagate 1TB Hybrid vs. WD Black2 Dual Drive http://www.maximumpc.com/seagate_1tb_hybrid_vs_wd_black2_dual_drive_2014 <!--paging_filter--><h3>Seagate 1TB Hybrid vs. WD Black2 Dual Drive</h3> <p>Every mobile user who is limited to just one storage bay wants the best of both worlds: SSD speeds with HDD capacities. Both Seagate and WD have a one-drive solution to this problem, with Seagate offering a hybrid 1TB hard drive with an SSD cache for SSD-esque performance, and WD offering a no-compromise 2.5-inch drive with both an SSD and an HDD. These drives are arch rivals, so it’s time to settle the score.</p> <h4>ROUND 1: Specs and Package</h4> <p>The WD Black2 Dual Drive is two separate drives, with a 120GB SSD riding shotgun alongside a two-platter 1TB 5,400rpm hard drive. Both drives share a single SATA 6Gb/s interface and split the bandwidth of the channel between them, with the SSD rated to deliver 350MB/s read speeds and 140MB/s write speeds. The drive comes with a SATA-to-USB adapter and includes a five-year warranty. The Seagate SSHD uses a simpler design and features a 1TB 5,400rpm hard drive with an 8GB sliver of NAND flash attached to it, along with software that helps move frequently accessed data from the platters to the NAND memory for faster retrieval. It includes a three-year warranty and is otherwise a somewhat typical drive aimed at the consumer market, not hardcore speed freaks. Both drives include free cloning software, but since the WD includes two physical drives, a USB adapter, and a longer warranty, it gets the nod.</p> <p style="text-align: center;"><a class="thickbox" href="/files/u152332/wd_endeavor_quarter_left_higres_smal_0.jpg"><img src="/files/u152332/wd_endeavor_quarter_left_higres_smal.jpg" alt="WD’s Black2 Dual Drive is two individual drives in one enclosure, and it has the price tag to prove it. " title="WD Black2" width="620" height="620" /></a></p> <p style="text-align: center;"><strong>WD’s Black2 Dual Drive is two individual drives in one enclosure, and it has the price tag to prove it. </strong></p> <p><strong>Winner: WD Black2</strong></p> <h4>ROUND 2: Durability</h4> <p>This category is somewhat of a toss-up, as the WD Black2’s overall reliability is degraded somewhat by the fact that it has a spinning volume attached to it, giving it the same robustness of the Seagate SSHD. There’s also the issue of the WD Black using the slightly antiquated JMicron controller. We don’t have any reliability data on that controller in particular, but we are always more concerned about the SSD controller you-know-whating the bed than the memory, which is rated to last for decades, even under heavy write scenarios. Both drives also use two-platter designs, so neither one is more or less prone to damage than the other. In the end, we’ll have to go with the Seagate SSHD as being more durable, simply because you only have to worry about one drive working instead of two.&nbsp;</p> <p><strong>Winner: Seagate SSHD</strong></p> <h4>ROUND 3: Performance</h4> <p>Seagate is very clear about the performance of its hybrid drives, stating that they “boot and perform like an SSD,” but it never says they’re faster. It also claims the drive is “up to five times faster than a hard drive,” which seems like a bit of a stretch. It’s difficult to actually benchmark a caching drive because it won’t show on standard sequential read tests, and it gets killed by SSDs in access time tests. That said, we did see boot and PCMark Vantage scores improve significantly over time. Our boot time dropped by more than half, going from 2:27 to 1:07 after several boots, and our PCMark Vantage score shot up from 6,000 to 19,000. Still, these times are much slower than what we got with the WD SSD, which booted in 45 seconds (the system had three dozen programs installed), and hit 33,000 in PCMark Vantage.</p> <p><strong>Winner: WD Black2</strong></p> <h4>ROUND 4: Cloning Package</h4> <p>Both drives include free software to help you clone your old drive and, in an odd twist, both companies use Acronis software to get ’er done. Seagate’s software is called DiscWizard, and works on OSes as old as Windows 98 and Mac OS 10.x. WD throws in a copy of Acronis True Image, though it only works with WD drives attached via the included USB-to-SATA adapter. We tested both software packages and found them to be nearly identical, as both let us clone our existing drive and boot from it after one pass, which can be tricky at times. Therefore, we call the software package a tie since they both perform well and use Acronis. However, WD’s $300 bundle includes a USB-to-SATA adapter that makes the cloning process totally painless. Seagate makes you forage for a cable on your own, which tips the scales in WD’s favor.</p> <p><strong>Winner: WD Black2</strong></p> <h4>ROUND 5: Ease of Use</h4> <p>This round has a crystal-clear winner, and that’s the Seagate SSHD. That’s because the Seagate drive is dead-simple to use and behaves exactly like a hard drive at all times. You can plug it into any PC, Mac, or Linux machine and it is recognized with no hassle. The WD drive, on the other hand, only works on Windows PCs because it requires special software to “unlock” the 1TB hard drive partition. For us, that’s obviously not a problem, but we know it’s enraged some Linux aficionados. Also, the WD drive only has a 120GB SSD. So, if you are moving to it from an HDD, you will likely have to reinstall your OS and programs, then move all your data to the HDD portion of the drive. The Seagate drive is big enough that you would just need to clone your old drive to it.</p> <p><strong>Winner: Seagate SSHD</strong></p> <p style="text-align: center;"><strong><a class="thickbox" href="/files/u152332/laptop-sshd-1tb-dynamic-with-label-hi-res-5x7_small_0.jpg"><img src="/files/u152332/laptop-sshd-1tb-dynamic-with-label-hi-res-5x7_small.jpg" alt="Seagate’s hybrid drive offers HDD simplicity and capacity, along with SSD-like speed for frequently requested data. " title="Seagate SSHD" width="620" height="639" /><br /></a></strong></p> <p style="text-align: center;"><strong>Seagate’s hybrid drive offers HDD simplicity and capacity, along with SSD-like speed for frequently requested data. </strong></p> <h3 style="text-align: left;">And the Winner Is…</h3> <p style="text-align: left;">This verdict is actually quite simple. If you’re a mainstream user, the Seagate SSHD is clearly the superior option, as it is fast enough, has more than enough capacity for most notebook tasks, and costs about one-third of the WD Black2. But this is Maximum PC, so we don’t mind paying more for a superior product, and that’s the <strong>WD Black2 Dual Drive</strong>. It delivers both speed and capacity and is a better high-performance package, plain and simple.</p> <p style="text-align: left;"><span style="font-style: italic;">Note: This article originally appeared in the April 2014 issue of the magazine.</span></p> http://www.maximumpc.com/seagate_1tb_hybrid_vs_wd_black2_dual_drive_2014#comments Hard Drive Hardware HDD Review Seagate 1TB Hybrid ssd WD Black2 Backup Drives Hard Drives Reviews SSD Features Thu, 31 Jul 2014 19:27:45 +0000 Josh Norem 28103 at http://www.maximumpc.com MSI Radeon R9 270 Gaming OC Review http://www.maximumpc.com/msi_radeon_r9_270_gaming_oc_review <!--paging_filter--><h3>No surprises here, just a solid 1080p card</h3> <p><a title="msi" href="http://www.maximumpc.com/tags/msi" target="_blank">MSI</a> is offering two flavors of its midrange Radeon R9 270 GPU, formerly known as the <a title="7870 GHz" href="http://www.maximumpc.com/tags/radeon_hd_7870_ghz_edition" target="_blank">Radeon HD 7870 GHz edition</a>. There is a standard model and one with an “X” after its name. The difference between the two is the X model has slightly higher core and boost clocks, but otherwise the two cards are the same and are both based on AMD’s Pitcairn GCN core, which is a 28nm part that debuted in 2013.</p> <p style="text-align: center;"><a class="thickbox" href="/files/u152332/r9_270x_gaming_2gd5v303_3d1_small_0.jpg"><img src="/files/u152332/r9_270x_gaming_2gd5v303_3d1_small.jpg" alt="Don’t bother with the R9 270X—the non-X version shown here is just fine. " title="MSI Radeon R9 270 Gaming OC" width="620" height="487" /></a></p> <p style="text-align: center;"><strong>Don’t bother with the R9 270X—the non-X version shown here is just fine. </strong></p> <p>The card in front of you is the MSI R9 270 Gaming model, which is a stock R9 270 with a mild overclock, hence the word “Gaming” in its moniker. It has an MSRP of $180, while the X version is roughly $20 more, though street prices are higher due to the mining craze and short supply. For those who are prone to guffawing at a card that is merely rebadged and price-dropped, this is par for the course and actually good news for gamers. That’s because both Nvidia and AMD refine their manufacturing processes over time, so by the time a GPU gets a rebadge, it’s often able to run at higher clocks with better efficiency for a much lower price. The bottom line is that this card once had a $350 price tag and now costs less than $200, so there’s very little to complain about.</p> <p>To rehash the specs, this is a card with a base clock of 900MHz and a boost clock of 975MHz, which is 50MHz higher than the reference board. It has 2GB of GDDR5 memory that runs at 5.6GHz, and 1,280 stream processors. Since this is not new silicon, the card does not offer support for TrueAudio, but as it’s a Graphics Core Next (GCN) card, it does support AMD’s new Mantle API (at press time, BF4 was not optimized for Mantle with the R9 270, but AMD said it’s “being investigated”). As a midrange GPU, the R9 270 has a low-ish TDP of 150w, and therefore requires only a single six-pin PCIe connector for power—an advantage over the 270X, which requires two six-pin connectors. Interestingly, the R9 270 doesn’t have a direct competitor from Nvidia since it costs just a bit over $200, so it sits right in between the $250 GTX 760 and the $150 GTX 650 Ti (the Ti Boost is out of stock everywhere, but costs around $175). The GTX 660 is about the same price, but that card is ancient, so we compared it to the more-expensive GTX 760.</p> <p>Overall, we had a pleasant testing experience with the MSI R9 270 card. It was quiet and cool—never getting hotter than <br />60 C—and was totally stable. It ran the grueling new Star Swarm demo over a weekend with nary a hiccup, and we were also able to overclock it to 1,140MHz boost clock, which netted a 10 percent bump in performance. Basically, we found its performance exactly in line with its price, in that it was a bit slower than the more-expensive GTX 760 in all the games we test aside from Tomb Raider, which is an AMD game.</p> <p>In the end, there’s nothing wrong with the MSI R9 270 Gaming OC and we have no problem recommending it. However, we’d still go with the GTX 760 just because it is quite a bit faster in many games, and only costs $30 more. If Mantle support is important to you, though, feel free to pull the trigger.</p> <p><strong>$220 (street),</strong> <a href="http://www.msi.com/index.php">www.msi.com</a></p> <p><span style="font-style: italic;">Note: This review was originally featured in the April 2014 issue of the&nbsp;</span><a style="font-style: italic;" title="maximum pc mag" href="https://w1.buysub.com/pubs/IM/MAX/MAX-subscribe.jsp?cds_page_id=63027&amp;cds_mag_code=MAX&amp;id=1366314265949&amp;lsid=31081444255021801&amp;vid=1&amp;cds_response_key=IHTH31ANN" target="_blank">magazine</a><span style="font-style: italic;">.</span></p> http://www.maximumpc.com/msi_radeon_r9_270_gaming_oc_review#comments april issues 2014 graphics card Hardware maximum pc msi radeon r9 270 oc Review videocard Reviews Videocards Wed, 30 Jul 2014 22:39:42 +0000 Josh Norem 28096 at http://www.maximumpc.com D-Link DGL-5500 Review http://www.maximumpc.com/d-link_dgl-5500_review <!--paging_filter--><h3>A router built specifically for gamers</h3> <p>When it comes to PC parts and accessories, all roads eventually lead to gamers. Intel and AMD both sell unlocked processors so gamers can more easily overclock their rigs for a few extra frames per second; pro gamer Johnathan “Fatal1ty” Wendel has endorsed everything from motherboards to power supplies; there’s gaming RAM; and of course, a whole assortment of accessories designed to give you an edge when smoking your friends on the virtual battlefield. Up until now, one of the few items missing from the list was an 802.11ac wireless router.</p> <p style="text-align: center;"><a class="thickbox" href="/files/u152332/dgl-5500_front_small_0.jpg"><img src="/files/u152332/dgl-5500_front_small.jpg" alt="The new Mac Pro stole its design from this router—true story. " title="D-Link DGL-5500" width="583" height="1200" /></a></p> <p style="text-align: center;"><strong>The new Mac Pro stole its design from this router—true story. </strong></p> <p style="text-align: center;"><a class="thickbox" href="/files/u152332/dgl-5500_back_small_0.jpg"><img src="/files/u152332/dgl-5500_back_small.jpg" title="D-Link DGL-5500" width="584" height="1200" /></a></p> <p>D-Link gets credit for tying up that loose end with the DGL-5500, a dual-band AC1300 wireless router built specifically for gamers. What makes the DGL-5500 different from all the other 802.11ac models, including D-Link’s own DIR-868L (reviewed in our February issue), is the inclusion of Qualcomm’s StreamBoost technology.</p> <p>Whereas the majority of modern routers rely on simple quality of service (QoS) rules to prioritize network packets, StreamBoost examines what applications are running and how much actual bandwidth each one needs. It also manages latency because a laggy gamer is a dead gamer. The question is, does it work as advertised?</p> <p>For the most part, StreamBoost lives up to the hype. We consistently saw lower pings in online games when connected to the DGL-5500 versus our zero-point router, the Asus RT-AC66U. External factors beyond our control also affect ping, so it’s hard to offer an apples-to-apples comparison, but to give one example, our ping averaged around 42ms in Battlefield 4 when using Asus’s router. When switching to D-Link’s model and turning on StreamBoost, our pings hovered around 19ms. After firing up Netflix on a second PC and initiating file downloads on two other systems, the ping stayed around 22–24ms—that’s impressive.</p> <p>In our evaluation of D-Link’s DIR-868L, we said the fugly web-based interface could use a major overhaul, and that’s what we got with the DGL-5500. It’s much better looking than before and far less complicated to navigate, though it’s also painfully slow when switching between menus. The UI is also heavily biased toward StreamBoost—if you disable the feature, you lose access to the My Network map, which provides a graphical view of all active devices and how much bandwidth each one is consuming.</p> <p>The DGL-5500 outpaced our zero point router in 802.11n mode on the 2.4GHz band in our three indoor tests. It also did better at picking out uncluttered channels on its own—we use inSSIDer ($20, www.inssider.com) to identify the best channel(s) for testing. However, the RT-AC66U boasts better range and faster transfers in 802.11ac mode on the 5GHz band. It’s worth pointing out the DGL-5500 lacks beamforming, which concentrates the wireless signal at connected devices for longer range and better speeds.</p> <p>There are other shortcomings, as well—you can’t configure Guest networks, the single USB 2.0 port doesn’t support printer sharing, and the combined speed of both channels is capped at AC1300 rather than AC1750 as it is with D-Link’s DIR-868L. While StreamBoost is a step forward, the router is a step backward in other areas. Note to D-Link: Gamers care about this stuff, too.</p> <p><strong>$140 [street],</strong> <a href="http://www.d-link.com/">www.d-link.com</a></p> http://www.maximumpc.com/d-link_dgl-5500_review#comments ac wireless april issues 2014 Gaming Hardware hd media router 2000 Review Reviews Wed, 30 Jul 2014 22:22:18 +0000 Paul Lilly 28097 at http://www.maximumpc.com AVADirect Mini Cube Gaming PC Review http://www.maximumpc.com/avadirect_mini_cube_gaming_pc_review_2014 <!--paging_filter--><h3>Just call it ‘The Fridge’</h3> <p>Naming a PC isn’t an easy task. It’s hard enough when you’re talking about your personal PC (Betsy, Svetlana, or Jabba work well), but when you’re a company selling a new model, Marketing 101 says the name should imbue magic and convince consumers to pony up.</p> <p style="text-align: center;"><a class="thickbox" href="/files/u152332/ava_13708_small_0.jpg"><img src="/files/u152332/ava_13708_small.jpg" alt="Though capable and reasonably priced, this medium form factor is eclipsed by smaller, faster, and cheaper machines." title="AVADirect Mini Cube Gaming PC" width="620" height="582" /></a></p> <p style="text-align: center;"><strong>Though capable and reasonably priced, this medium form factor is eclipsed by smaller, faster, and cheaper machines.</strong></p> <p>We’re guessing AVADirect didn’t take that class, as its new custom mini-cube gaming PC is apparently named Mini Cube Gaming PC. The truth is, AVADirect probably doesn’t give a damn about the name because frankly, who cares? Maybe “5S” or “S IV” works on some people, but on a custom PC where you pick out the parts yourself, it’s probably far less pressing.</p> <p>Around the office, we’ve taken to calling this handsome SFF machine “The Fridge,” not necessarily because of its size, but because of its Frigidaire-like aesthetic. Sure, it would have been cool if the optical drive shared the same brushed-aluminum surface, but it still matches the black accents elsewhere on the case. While there’s no question that this is a small form factor rig, compared to the micro-towers we’ve seen lately, it’s pretty big. It’s more than double the width of the Falcon Northwest Tiki, and while slightly shorter than the CyberPower Hadron we reviewed in February, it’s about three inches wider than that machine.</p> <p>That size increase gives it more capability. While most micro-towers use SFX or 1U PSUs, The Fridge uses a standard 760W Seasonic ATX PSU. Inside, you’ll also find a liquid-cooled Core i7-4770K overclocked to 4.2GHz, 16GB of Kingston DDR3/1600, two Kingston 120GB HyperX SSDs in RAID 0, a 2TB WD HDD, an MSI Z87 Mini-ITX board, and an Asus GeForce GTX 780 card.</p> <p>Against our zero-point system, the AVADirect represents well in the non-heavily multithreaded tasks but, not surprisingly, it gets left behind in all other tests by the ZP’s six-core Core i7-3930K part clicking along at 3.8GHz. That includes gaming tests, but not by the margin you would expect from the zero-point’s GeForce GTX 690.</p> <p>The more important question is how The Fridge compares with the SFF/micro-tower crowd. Not too shabby. The bad mutha of the group continues to be Falcon Northwest’s Tiki, with its Haswell part overclocked to 4.7GHz and a GeForce Titan. Indeed, the Tiki still stands as the fastest micro-tower we’ve ever tested, and the fact that it’s held onto that title well into the new year demonstrates how aggressively Falcon went for broke with this model. Of course, that aggression comes at a price, with the Tiki hitting the $4,400 mark. At $2,583, AVADirect can pull the old, “You can buy our system, play all of your games, and still have enough money to buy two of the upcoming cheap 4K panels” routine.</p> <p>Normally, that routine would sway us, because like most folks, we can see sacrificing a little performance for a new monitor, keyboard, mouse, and new suit and shoes, too. But then there’s CyberPower PC’s Hadron Hydro 300, which costs $300 less than the AVADirect. It almost mirrors the parts in the AVADirect except for the HDD. The Hadron also packs custom liquid-cooling for its CPU and GPU, which, while the chassis gets a tad warm, helps the rig run extremely quietly and gives it a slight performance edge. The AVADirect box is louder and under heavy loads emits a low-frequency large-fan buzz.</p> <p>That leaves the AVADirect in a tough spot. It’s slower than the Tiki and more expensive than the Hadron. Yes, it’s got an off-the-shelf PSU, but we’re not sure that’s worth the sacrifice in size. Yes, it’s a striking-looking case with its brushed-steel/aluminum finish, but maybe the sun is just finally starting to set on the medium form factor.</p> <p><strong>$2,584,</strong> <a href="http://www.avadirect.com/">www.avadirect.com</a></p> <p><em>Note: This article was originally featured in our March issue of the magazine.</em></p> http://www.maximumpc.com/avadirect_mini_cube_gaming_pc_review_2014#comments AVADirect Mini Cube Hardware March issues 2014 maximum pc Reviews Systems Thu, 24 Jul 2014 22:11:59 +0000 Gordon Mah Ung 28059 at http://www.maximumpc.com Sapphire Tri-X Radeon R9 290X Review http://www.maximumpc.com/sapphire_tri-x_radeon_r9_290x_review <!--paging_filter--><h3>A real gem of a GPU</h3> <p>For those who haven’t kept up with current events: Late last year AMD launched its all-new Hawaii GPUs, starting with its flagship Radeon R9 290X that featured a blower-type cooler designed by AMD. In testing, it ran hotter than any GPU we’ve ever tested, hitting 94 C at full load, which is about 20 C higher than normal. AMD assured everyone this was no problemo, and that the board was designed to run those temps until the meerkats came home. It was stable at 94 C, but the GPU throttled performance at those temps. The stock fan was also a bit loud at max revs, so though the card offered kick-ass performance, it was clearly being held back by the reference cooler.</p> <p style="text-align: center;"><a class="thickbox" href="/files/u152332/sapphire_13650_small_0.jpg"><img src="/files/u152332/sapphire_13650_small.jpg" alt="The Tri-X throws off AMD’s meh cooler." title="Sapphire Tri-X Radeon R9 290X" width="620" height="413" /></a></p> <p style="text-align: center;"><strong>The Tri-X throws off AMD’s meh cooler.</strong></p> <p>Therefore, we all eagerly awaited the arrival of cards with aftermarket coolers, and this month we received the first aftermarket Radeon R9 290X—the massive triple-fan Tri-X model from Sapphire; and we must say, all of our Radeon prayers have been answered by this card.</p> <p>Not only does it run totally cool and quiet at all times, but because it runs so chilly it has plenty of room to overclock, making it a card that addresses every single one of our complaints about the reference design from AMD. There is one caveat: price. The Sapphire card is $50 more expensive than the reference card at $600, but you are obviously getting quite a bit of additional horsepower for your ducats.</p> <p>When we first fired it up, we were amazed to see it hit 1,040MHz under load, and stay there throughout testing. Even more surprising were the temps we were seeing. Since the reference card hits 94 C all day long, this is obviously a really hot GPU, but the Sapphire Tri-X cooler was holding it down at a chilly 75 C. The card was whisper-quiet too, which was also a pleasant surprise given the noise level of the reference cooler. We were also able to overclock it to 1,113MHz, which is a turnaround in that we could not overclock the reference board at all since it throttles at stock settings.</p> <p><strong>$600,</strong> <a href="http://www.sapphiretech.com/landing.aspx?lid=1">www.sapphiretech.com</a></p> <p><span style="font-style: italic;">Note: This review was originally featured in the March 2014 issue of the&nbsp;</span><a style="font-style: italic;" title="maximum pc mag" href="https://w1.buysub.com/pubs/IM/MAX/MAX-subscribe.jsp?cds_page_id=63027&amp;cds_mag_code=MAX&amp;id=1366314265949&amp;lsid=31081444255021801&amp;vid=1&amp;cds_response_key=IHTH31ANN" target="_blank">magazine</a><span style="font-style: italic;">.</span></p> http://www.maximumpc.com/sapphire_tri-x_radeon_r9_290x_review#comments Air Cooling amd gpu graphics card Hardware March issues 2014 maximun pc Review Sapphire Tri-X Radeon R9 290X Reviews Thu, 24 Jul 2014 22:09:13 +0000 Josh Norem 28024 at http://www.maximumpc.com