We'll sum up the weaknesses for both boards together, as they are essentially the same. Automated overclocking routines seem to be an increasing trend among the board-makers, but sadly Intel's "Auto-Tune" software failed horribly. With our i7 870 sat at stock and BIOS defaults, we started the Auto-Tune and chose the 1st option of overclocking within Intel’s safe range. The program quickly ran into problems such as application crashes and BSOD’s. Auto-Tune’s pre-programmed routines start IDCC and reinitialize the Auto-Tune option when Windows loads, so unfortunately this problem persisted as it failed to advance past the point it kept failing at. The only solution was to stop Auto-Tune starting at the Windows UAC prompt and then uninstall and reinstall the software.

Memory overclocking was disappointing. While the 2:6 and 2:8 memory ratios were satisfactory, the 2:10 ran into problems and refused to boot any higher than 175 BCLK from a power cycle which equated to 875 MHz or DDR3-1750. This was despite trying up to 1.35v VTT and loosening timings to 9-9-9-27 and slacking off tRFC and tFAW. The only way to get both boards to POST past 175 BCLK was to use or high-end Corsair 2200 MHz modules - and that too was only possible by ramping BCLK slowly so that the board did not need a full power cycle when exiting BIOS.

Unfortuantely, we ran into problems whilst stress testing at memory freqeuncies above 1800MHz, the board shut-down when running Hyper-Pi. We tried all manner of changes to circumvent this problem, finding that using VTT voltage above 1.42V resulted in the board shutting down whilst loading Windows. It would be logical for us to put this down to some kind of over-current protection - we're used to seeing more overhead from motherboards that are given an 'Extreme' moniker. It's clear this is an area that Intel need to work on in the future.

Four months after the launch of Intel's 32nm Clarkdale CPUs and after a number of supported BIOS releases, we didn't expect to run into a bug such as the PCI-E x16 slot running at 1x speed with an i5 670. This was another disappointing discovery that affects the lowly 9500GT in terms of benchmark results, meaning that better and faster cards are likely the be affected even more.

S3 resume was ok on both boards until around abut 170-175 BCLK where the board would resume Windows, but fail-back to restore the session from the hard drive like a hibernation.  Again, this is an area where Intel are not quite competitve with the rest.

The list of what we would like to see improved or added to Intel’s “Extreme” series is quite lengthy. The BIOS could be better laid out, with more options to tweak but even just the simple things like ‘Auto’ settings for memory timings. The IDCC software could also be improved, with Auto-Tune needing a large overhaul. Memory overclocking should be a strong focus, with the minimum requirement of having all the dividers working as expected, at least to the same level as other vendors.

Stepping back from the specifics, the board layout, while understandable for Intel’s standard desktop range, should have been redesigned to allow larger aftermarket heatsinks to be used and a full board of good quality solid capacitors isn’t much to ask as it's become standard for products in this price range.

If you forget that these boards are part of Intel’s “Extreme” series and just look upon them as basic P55 ATX and M-ATX boards, they’re much easier to recommend. As with all of Intel’s boards, they have a lot of ‘little things’ that just work and you find yourself overlooking some of the finer details unless you stop to think. The disappointing fact is that Intel is marketing these under their “Extreme” series and they just don’t do enough to satisfy their ‘extreme’ price tags.

System Benchmarks
Comments Locked

26 Comments

View All Comments

  • Richard Pawley - Wednesday, April 7, 2010 - link

    Thanks PR3ACH3R, this is good feedback. We will look into this and update the review once we've carried out some more tests.

    Regards,
    Richard
  • PR3ACH3R - Thursday, April 8, 2010 - link

    Look Here for a report on the biggest DPC Issue of our time,
    one that is silenced by the manufacturer, & probably an excellent article subject for Anandtech.

    http://www.avsforum.com/avs-vb/showthread.php?p=18...
  • Googer - Thursday, April 8, 2010 - link

    With out PS2 die hard Clicky Keyboard Lovers like myself will be forced to boycott intel motherboards and support manufacturers like Gigabyte and ASUS. Intel, do all of us a favor and preserve the PS2 port, USB converter solutions just don't work very well.
  • ClagMaster - Saturday, April 10, 2010 - link

    I too have issues with this latest generation of Intel Motherboards of not providing support for legacy devices.

    Lack of floopy and PS/2 support is not an issue because these devices are truly obsolete. Most new mice and keyboards available for the last six years with USB.

    Lack of IDE support for Optical Drives is a significant issue for many users because they have high performance IDE Optical Drives they paid over $100 that they still want to use. And they are very much aware there is no significant benefit buying a SATA drive for much less.

    The DP55KG is too much money for the features and performance at ($210). I would have bought the lower cost DP55WG ($140) except that it does not have IDE support for my optical drives. So the candidate worth buying for the money is the GIGABYTE GA-P55A-UD3P ($140)
  • iamkyle - Monday, April 19, 2010 - link

    ...at least Intel programs its own BIOS program, unlike every other mobo manufacturer that has it programmed in Taiwan, then poorly translates it.

    Nowhere in an Intel BIOS will you find things like "It the system power is be reset it will cause the malfunction!!!"
  • Redphil - Sunday, November 28, 2010 - link

    I am using the DP55KG for a while in combination with a Pentium G6950 (Clarkdale).
    I changed my Graphic Card and discovered that I have the PCIe x1-Bug that was described in the review. I have the newest BIOS and tried a bunch of things, but wasn't able to solve the problem. Even contacted Intel via Support-Chat, but they were no help.

    Have anyone here a solution for this annoying bug (besides changing Mainboard/CPU, of course)?

Log in

Don't have an account? Sign up now