<?xml version="1.0" encoding="utf-8" ?>
<?xml-stylesheet type="text/xsl" href="RSS_xslt_style.asp" version="1.0" ?>
<rss version="2.0" xmlns:WebWizForums="https://syndication.webwiz.net/rss_namespace/">
 <channel>
  <title>ASRock Forums : Asrock X99 WS SYSTIN temp &gt;100C</title>
  <link>https://forum.asrock.com/</link>
  <description><![CDATA[This is an XML content feed of; ASRock Forums : Intel Motherboards : Asrock X99 WS SYSTIN temp &gt;100C]]></description>
  <copyright>Copyright (c) 2006-2013 Web Wiz Forums - All Rights Reserved.</copyright>
  <pubDate>Sun, 07 Jun 2026 13:14:10 +0000</pubDate>
  <lastBuildDate>Fri, 05 Aug 2016 04:26:50 +0000</lastBuildDate>
  <docs>http://blogs.law.harvard.edu/tech/rss</docs>
  <generator>Web Wiz Forums 12.04</generator>
  <ttl>360</ttl>
  <WebWizForums:feedURL>https://forum.asrock.com/RSS_post_feed.asp?TID=3170</WebWizForums:feedURL>
  <image>
   <title><![CDATA[ASRock Forums]]></title>
   <url>https://forum.asrock.com/forum_images/web_wiz_forums_black.png</url>
   <link>https://forum.asrock.com/</link>
  </image>
  <item>
   <title><![CDATA[Asrock X99 WS SYSTIN temp &gt;100C : So things have cooled off there....]]></title>
   <link>https://forum.asrock.com/forum_posts.asp?TID=3170&amp;PID=15587&amp;title=asrock-x99-ws-systin-temp-100c#15587</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://forum.asrock.com/member_profile.asp?PF=423">wardog</a><br /><strong>Subject:</strong> 3170<br /><strong>Posted:</strong> 05 Aug 2016 at 4:26am<br /><br />So things have cooled off there. Good to hear.<br><br>Maybe not NZXTs prog alone but all running at the same time. All competing for the same data.<br>]]>
   </description>
   <pubDate>Fri, 05 Aug 2016 04:26:50 +0000</pubDate>
   <guid isPermaLink="true">https://forum.asrock.com/forum_posts.asp?TID=3170&amp;PID=15587&amp;title=asrock-x99-ws-systin-temp-100c#15587</guid>
  </item> 
  <item>
   <title><![CDATA[Asrock X99 WS SYSTIN temp &gt;100C : UpdateI disabled NZXT CAM while...]]></title>
   <link>https://forum.asrock.com/forum_posts.asp?TID=3170&amp;PID=15564&amp;title=asrock-x99-ws-systin-temp-100c#15564</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://forum.asrock.com/member_profile.asp?PF=1673">Airbus480</a><br /><strong>Subject:</strong> 3170<br /><strong>Posted:</strong> 04 Aug 2016 at 1:07pm<br /><br />Update<br>I disabled NZXT CAM while HWMonitor and Speccy are running and I have not encountered the 100 C ever since temp so maybe NZXT CAM is the culprit.]]>
   </description>
   <pubDate>Thu, 04 Aug 2016 13:07:00 +0000</pubDate>
   <guid isPermaLink="true">https://forum.asrock.com/forum_posts.asp?TID=3170&amp;PID=15564&amp;title=asrock-x99-ws-systin-temp-100c#15564</guid>
  </item> 
  <item>
   <title><![CDATA[Asrock X99 WS SYSTIN temp &gt;100C : There are many instances where...]]></title>
   <link>https://forum.asrock.com/forum_posts.asp?TID=3170&amp;PID=15513&amp;title=asrock-x99-ws-systin-temp-100c#15513</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://forum.asrock.com/member_profile.asp?PF=423">wardog</a><br /><strong>Subject:</strong> 3170<br /><strong>Posted:</strong> 03 Aug 2016 at 1:39am<br /><br />There are many instances where multiple programs tapping the SMBus for temp data will return very incorrect dubious results.<br><br>Try disabling all but one monitoring program, shut down or reboot, and reply back if this continues.<br><br><br>If your MB has the ASRock AXTU installed, when it's the only monitoring program, do you see this issue?<br><span style="font-size:10px"><br /><br />Edited by wardog - 03 Aug 2016 at 1:40am</span>]]>
   </description>
   <pubDate>Wed, 03 Aug 2016 01:39:38 +0000</pubDate>
   <guid isPermaLink="true">https://forum.asrock.com/forum_posts.asp?TID=3170&amp;PID=15513&amp;title=asrock-x99-ws-systin-temp-100c#15513</guid>
  </item> 
  <item>
   <title><![CDATA[Asrock X99 WS SYSTIN temp &gt;100C : I have this mobo for over a year...]]></title>
   <link>https://forum.asrock.com/forum_posts.asp?TID=3170&amp;PID=15512&amp;title=asrock-x99-ws-systin-temp-100c#15512</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://forum.asrock.com/member_profile.asp?PF=1673">Airbus480</a><br /><strong>Subject:</strong> 3170<br /><strong>Posted:</strong> 03 Aug 2016 at 12:31am<br /><br />I have this mobo for over a year now and using HWMonitor to mainly see the temps of my CPU <br><br>While I am using HWMonitor I suddenly saw my mobo temp or SYSTIN temp goes more than 100C of course I panicked and force shutdown my computer to see if something smells and open up my case but I didn't see any melted components or the smell of burn so I powered up again and went into UEFI and saw mobo temps are normal nearing ~40C<br>So I rebooted and use the computer for a few hours and then after that suddenly I saw again in HWmonitor SYSTIN temp goes above 100C with a maximum of 126C, Speccy also reports this temp<br>I panicked again but a little less so what I did to test something: put the computer to sleep for a few seconds then wake it up again and the mobo temps are now back to normal ~37 C <br>Is this a bug? I never encountered this problem before, it started when I updated my UEFI from 3.10 to 3.20. <br>I have to note also I started using NZXT CAM (same time as UEFI update) while using HWMonitor and Speccy at the same time.<br>I am sure if this is beyond 100C I should've smelled something burning and the mobo shutsdown <img src="https://forum.asrock.com/smileys/smiley5.gif" border="0" alt="C&#111;nfused" title="C&#111;nfused" /><br><br>SYSTIN<br><img src="http://i.imgur.com/T5OTZpE.png" height="106" width="527" border="0" /><br>I am using 5820k Win 7 x64<br><span style="font-size:10px"><br /><br />Edited by Airbus480 - 03 Aug 2016 at 12:51am</span>]]>
   </description>
   <pubDate>Wed, 03 Aug 2016 00:31:25 +0000</pubDate>
   <guid isPermaLink="true">https://forum.asrock.com/forum_posts.asp?TID=3170&amp;PID=15512&amp;title=asrock-x99-ws-systin-temp-100c#15512</guid>
  </item> 
 </channel>
</rss>