<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: How do I validate cpu stability in Mobile and Desktop Processors</title>
    <link>https://community.intel.com/t5/Mobile-and-Desktop-Processors/How-do-I-validate-cpu-stability/m-p/617325#M34779</link>
    <description>&lt;P&gt;Oh thanks for the reply but I have finally solved this problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It all started 2 months ago with this new cpu on a new ASUS board and I could never solve the issue. When it came up on my new MSI mobo with the same cpu, I feared the worst but I have managed to iron it out this morning by adjusting my cache ratio and boosting VCCSA, which is something that made no difference on the ASUS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So the end result is that for all other stress/bench tests, including XTU, IBT, AIDA and Folding there is no problem running a modest 4.7Ghz OC with 2400 ram but for the Fire Strike test I have to dial the ram down 1333 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I drop down to 4.6Ghz for my daily build so it's all good now. I am now confident of pushing this cpu further when I submerge it in the coming weeks &lt;/P&gt;</description>
    <pubDate>Fri, 31 Oct 2014 16:55:13 GMT</pubDate>
    <dc:creator>PWalk3</dc:creator>
    <dc:date>2014-10-31T16:55:13Z</dc:date>
    <item>
      <title>How do I validate cpu stability</title>
      <link>https://community.intel.com/t5/Mobile-and-Desktop-Processors/How-do-I-validate-cpu-stability/m-p/617323#M34777</link>
      <description>&lt;P&gt;I am not sure if my recently new i7-4790k is faulty or not.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have run a series of stress/benchmarks and mostly they come back fine. Including Intel Burn Test.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, every now and then XTU complains that my system may be unstable when I open it, even though I am running stock (no overclock). Also, Futuremark Firestrike test has always rejected my test results since I have had this cpu due to claimed cheating, which they say if I am not cheating means I have an unstable rtc on my cpu. I am not cheating.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If this cpu is faulty, I will need to rma it soon before I can't but I just do not know how to confirm what Futuremark claim and if I simply rma for the supplier to confirm the chip is fine, I will be charged for the process :S&lt;/P&gt;</description>
      <pubDate>Thu, 30 Oct 2014 11:15:43 GMT</pubDate>
      <guid>https://community.intel.com/t5/Mobile-and-Desktop-Processors/How-do-I-validate-cpu-stability/m-p/617323#M34777</guid>
      <dc:creator>PWalk3</dc:creator>
      <dc:date>2014-10-30T11:15:43Z</dc:date>
    </item>
    <item>
      <title>Re: How do I validate cpu stability</title>
      <link>https://community.intel.com/t5/Mobile-and-Desktop-Processors/How-do-I-validate-cpu-stability/m-p/617324#M34778</link>
      <description>&lt;P&gt;Hello Tuxxy_Thang, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It is possible that your motherboard manufacturer has programmed in some DEFAULT BIOS settings that are essentially overclocking your CPU.&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;Please share a screenshot of the All Controls screen (under the Manual Tuning section) from XTU&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards.&lt;/P&gt;</description>
      <pubDate>Fri, 31 Oct 2014 14:27:38 GMT</pubDate>
      <guid>https://community.intel.com/t5/Mobile-and-Desktop-Processors/How-do-I-validate-cpu-stability/m-p/617324#M34778</guid>
      <dc:creator>Silvia_L_Intel1</dc:creator>
      <dc:date>2014-10-31T14:27:38Z</dc:date>
    </item>
    <item>
      <title>Re: How do I validate cpu stability</title>
      <link>https://community.intel.com/t5/Mobile-and-Desktop-Processors/How-do-I-validate-cpu-stability/m-p/617325#M34779</link>
      <description>&lt;P&gt;Oh thanks for the reply but I have finally solved this problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It all started 2 months ago with this new cpu on a new ASUS board and I could never solve the issue. When it came up on my new MSI mobo with the same cpu, I feared the worst but I have managed to iron it out this morning by adjusting my cache ratio and boosting VCCSA, which is something that made no difference on the ASUS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So the end result is that for all other stress/bench tests, including XTU, IBT, AIDA and Folding there is no problem running a modest 4.7Ghz OC with 2400 ram but for the Fire Strike test I have to dial the ram down 1333 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I drop down to 4.6Ghz for my daily build so it's all good now. I am now confident of pushing this cpu further when I submerge it in the coming weeks &lt;/P&gt;</description>
      <pubDate>Fri, 31 Oct 2014 16:55:13 GMT</pubDate>
      <guid>https://community.intel.com/t5/Mobile-and-Desktop-Processors/How-do-I-validate-cpu-stability/m-p/617325#M34779</guid>
      <dc:creator>PWalk3</dc:creator>
      <dc:date>2014-10-31T16:55:13Z</dc:date>
    </item>
  </channel>
</rss>

