<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>Intel Communities: Message List</title>
    <link>http://communities.intel.com/index.jspa?view=discussions</link>
    <description>Most recent forum messages</description>
    <language>en</language>
    <pubDate>Wed, 29 Aug 2012 04:31:15 GMT</pubDate>
    <generator>Jive SBS 5.0.2.0  (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2012-08-29T04:31:15Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>Re: DH77DF misdetects memory XMP profile as 1.8v, may kill CPU</title>
      <link>http://communities.intel.com/message/165542?tstart=0#165542</link>
      <description>&lt;!-- [DocumentBodyStart:ee223111-d80a-405a-9a70-da30757b69bf] --&gt;&lt;div class="jive-rendered-content"&gt;&lt;p&gt;I did some more checks, and confirmed IDU &amp;amp; BIOS fan control page are indeed correct with a multimeter.&amp;nbsp; I found a workaround that gets me back to the right voltage.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;David &amp;amp; Tolga - can you try my workaround in the 1st post to see if that gets you to a lower voltage, or if it sticks at 1.5v?&lt;/p&gt;&lt;/div&gt;&lt;!-- [DocumentBodyEnd:ee223111-d80a-405a-9a70-da30757b69bf] --&gt;</description>
      <pubDate>Wed, 29 Aug 2012 04:31:15 GMT</pubDate>
      <author>webadmin@intel.com</author>
      <guid>http://communities.intel.com/message/165542?tstart=0#165542</guid>
      <dc:date>2012-08-29T04:31:15Z</dc:date>
      <clearspace:dateToText>8 months, 4 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
      <clearspace:objectType>0</clearspace:objectType>
    </item>
    <item>
      <title>DH77DF misapplies memory voltage settings</title>
      <link>http://communities.intel.com/message/157366?tstart=0#157366</link>
      <description>&lt;!-- [DocumentBodyStart:9fe9c230-4d43-41d1-97e8-5bc74d1f31ea] --&gt;&lt;div class="jive-rendered-content"&gt;&lt;p&gt;Update 8/25/2012 - I have got down to the root of the problem, and it's not good.&amp;nbsp; I have been using this board since May, and have RMAd 4 different sets of RAM, all of which were used at their stock settings or even slower.&amp;nbsp; I suspect this is indeed due to the board over-volting the memory due to a bug in the BIOS settings that leads to incorrect memory VRM settings.&lt;/p&gt;&lt;p&gt;Here's what I now know for sure:&lt;/p&gt;&lt;p&gt;The measurements shown in Intel Desktop Utility and in system setup &amp;gt; Fan Control &amp;amp; Real-Time Monitoring &amp;gt; Memory Voltage are correct.&amp;nbsp; The measured voltages may differ from the settings, but the measurement is correct.&amp;nbsp; I confirmed this by reading the voltage off the caps adjacent to the memory slots.&amp;nbsp; If IDU reports 1.75v, I read 1.75 off that pad.&amp;nbsp; If it reads 1.53v, I can read it off the caps.&amp;nbsp; (Thanks go to erc, Daniel, David, and others in the tread for noticing this inconsistency)&lt;/p&gt;&lt;p&gt;&lt;span&gt;This sequence can cause the motherboard to supply an incorrect voltage to the memory every time.&amp;nbsp; Here's a video showing the sequence: &lt;/span&gt;&lt;a class="jive-link-external-small" href="https://skydrive.live.com/redir?resid=1AC889188B918540!569&amp;amp;authkey=!ADhaCNCCUVXtLTI" target="_blank"&gt;https://skydrive.live.com/redir?resid=1AC889188B918540!569&amp;amp;authkey=!ADhaCNCCUVXtLTI&lt;/a&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;Get the system to a clean state by resetting BIOS defaults&lt;/li&gt;&lt;li&gt;Exit, let system warm boot, and go back into BIOS.&amp;nbsp; Check voltage at Fan Control... - it will be correct (1.5 in my case) - video 0:00 to 0:30&lt;/li&gt;&lt;li&gt;You can reboot multiple times here, or go into Windows, run IDU, and it will continue returning the correct voltage.&lt;/li&gt;&lt;li&gt;Here's the problem: Now go to Performance, and change the value to Yes so you can see the memory/cpu settings.&amp;nbsp; Don't change anything.&amp;nbsp; Notice - the voltage setting will be correct here (1.5v in my case) - video 0:30 to 0:48&lt;/li&gt;&lt;li&gt;Reboot.&amp;nbsp; Go back into BIOS, and go to Fan Control...&amp;nbsp; At this point, the voltage will be wrong.&amp;nbsp; In the video attached, it shows 1.75v. - video 0:48 to 1:00&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;Now you're on track to kill the memory in a few days to a few months.&amp;nbsp; Here's how to get back to defaults. - video 1:02 to 1:50&lt;/p&gt;&lt;ul&gt;&lt;li&gt;Reset BIOS back to defaults, save settings, then TURN THE SYSTEM OFF.&amp;nbsp; If you don't turn the system off, the buggy settings WILL PERSIST.&lt;/li&gt;&lt;li&gt;Turn it back on, go into BIOS.&amp;nbsp; Confirm voltage - it will be back to the correct default. - video 1:50&lt;/li&gt;&lt;li&gt;Change your other settings back as needed for boot device, etc&lt;/li&gt;&lt;li&gt;Boot up Windows, run IDU - voltage will be correct&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;At this time, I'm not worrying about timings, etc until this voltage issue is resolved.&amp;nbsp; I'll update the thread once Intel is able to fix this firmware issue and work towards getting back to the 1600mhz my CPU and memory were designed for.&lt;/p&gt;&lt;span&gt; &lt;/span&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Original Message:&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;I have tried 3 different sets of memory trying to get to DDR3 1600mhz timings at 1.5v.&amp;nbsp; Each time, in the BIOS, Performance, Memory - it shows that its automatically choosing 1.5v, 1333 MHz, timings 9-9-9-24.&amp;nbsp; If I change from "Auto" to "XMP" profile setting, then it will show:&lt;/p&gt;&lt;p&gt;1600mhz, 1.8v, and the correct CAS/RAS timings.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;My CPU (Intel Core i5-3550) could be damaged by voltages that high, so I have not attempted these settings.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;I checked the memory's SPD data in CPU-Z, and it correctly shows the XMP profile for my Corsair XMS3 memory to be 1600mhz, 11-12-12-32, 1.5v.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;I also attempted to use Crucial Ballistix Sport (1600 9-9-9-24 1.5v), and Mushkin Blackline (1600 10-10-10-24 1.5v) modules - all led to the same incorrect 1.8v XMP profile.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Can someone confirm if this is just a display bug, or if it will actually attempt to use 1.8v in the XMP profile?&amp;nbsp; I would like to run my memory at max speed.&lt;/p&gt;&lt;/div&gt;&lt;!-- [DocumentBodyEnd:9fe9c230-4d43-41d1-97e8-5bc74d1f31ea] --&gt;</description>
      <pubDate>Tue, 29 May 2012 03:35:55 GMT</pubDate>
      <author>webadmin@intel.com</author>
      <guid>http://communities.intel.com/message/157366?tstart=0#157366</guid>
      <dc:date>2012-05-29T03:35:55Z</dc:date>
      <clearspace:dateToText>9 months, 1 day ago</clearspace:dateToText>
      <clearspace:replyCount>29</clearspace:replyCount>
      <clearspace:objectType>0</clearspace:objectType>
    </item>
    <item>
      <title>Re: DH77DF misdetects memory XMP profile as 1.8v, may kill CPU</title>
      <link>http://communities.intel.com/message/158963?tstart=0#158963</link>
      <description>&lt;!-- [DocumentBodyStart:e0b681ae-fbc4-4294-ac50-95b175bbbb9c] --&gt;&lt;div class="jive-rendered-content"&gt;&lt;p&gt;I double checked everything, and if I do full manual settings, I still cannot change the speed to 1600mhz.&amp;nbsp; The only way to get to 1600mhz is with the XMP setting, which is not safe.&amp;nbsp; There is no way to manually set both the speed and voltage to force it to 1600mhz, 1.5v that the memory was designed for and has in the XMP profile.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Does anyone know if there's another way to raise this issue with Intel?&amp;nbsp; It looks like we have 3/3 people confirming this as a bug.&lt;/p&gt;&lt;/div&gt;&lt;!-- [DocumentBodyEnd:e0b681ae-fbc4-4294-ac50-95b175bbbb9c] --&gt;</description>
      <pubDate>Thu, 14 Jun 2012 04:56:28 GMT</pubDate>
      <author>webadmin@intel.com</author>
      <guid>http://communities.intel.com/message/158963?tstart=0#158963</guid>
      <dc:date>2012-06-14T04:56:28Z</dc:date>
      <clearspace:dateToText>11 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>11</clearspace:replyCount>
      <clearspace:objectType>0</clearspace:objectType>
    </item>
  </channel>
</rss>

