ASRock Forums : X399 Fatal1ty temperature sensors wrong, stays on https://forum.asrock.com/ Copyright (c) 2006-2013 Web Wiz Forums - All Rights Reserved. Sun, 17 May 2026 02:33:21 +0000 Fri, 24 Nov 2017 03:05:30 +0000 http://blogs.law.harvard.edu/tech/rss Web Wiz Forums 12.04 360 https://forum.asrock.com/RSS_post_feed.asp?TID=6609 <![CDATA[ASRock Forums]]> https://forum.asrock.com/forum_images/web_wiz_forums_black.png https://forum.asrock.com/ <![CDATA[X399 Fatal1ty temperature sensors wrong, stays on : I got the replacement and all...]]> https://forum.asrock.com/forum_posts.asp?TID=6609&PID=39811&title=x399-fatal1ty-temperature-sensors-wrong-stays-on#39811 Author: Sydius
Subject: 6609
Posted: 24 Nov 2017 at 3:05am

I got the replacement and all is well now. :)

I noticed, looking back at the screenshots, that the fans were running at 2^16-1 etc., so I'm pretty sure the UEFI was just completely borked (and yes, I updated it and that didn't fix it).

NewEgg was kind enough to cross-ship me a replacement.
]]> Fri, 24 Nov 2017 03:05:30 +0000 https://forum.asrock.com/forum_posts.asp?TID=6609&PID=39811&title=x399-fatal1ty-temperature-sensors-wrong-stays-on#39811 <![CDATA[X399 Fatal1ty temperature sensors wrong, stays on : Obviously something very wrong...]]> https://forum.asrock.com/forum_posts.asp?TID=6609&PID=39598&title=x399-fatal1ty-temperature-sensors-wrong-stays-on#39598 Author: ssateneth
Subject: 6609
Posted: 21 Nov 2017 at 9:17am

Obviously something very wrong with the UEFI (Tried updating it?), or the sensor chip(s).  Probably should have tried RMAing directly through asrock (Most product boxes ask you RMA through manufacturer and not retailer)]]> Tue, 21 Nov 2017 09:17:07 +0000 https://forum.asrock.com/forum_posts.asp?TID=6609&PID=39598&title=x399-fatal1ty-temperature-sensors-wrong-stays-on#39598 <![CDATA[X399 Fatal1ty temperature sensors wrong, stays on : I think you did the right thing,...]]> https://forum.asrock.com/forum_posts.asp?TID=6609&PID=39439&title=x399-fatal1ty-temperature-sensors-wrong-stays-on#39439 Author: MisterJ
Subject: 6609
Posted: 18 Nov 2017 at 8:44am

I think you did the right thing, Sydius.  Something is bad on your board, but I have never seen anything like it.  Please let us hear how it turns out.  BTW, F12 will copy a screenshot to a plugged FAT formatted USB stick.  Enjoy, John.
]]> Sat, 18 Nov 2017 08:44:44 +0000 https://forum.asrock.com/forum_posts.asp?TID=6609&PID=39439&title=x399-fatal1ty-temperature-sensors-wrong-stays-on#39439 <![CDATA[X399 Fatal1ty temperature sensors wrong, stays on : I went ahead and issued an RMA...]]> https://forum.asrock.com/forum_posts.asp?TID=6609&PID=39363&title=x399-fatal1ty-temperature-sensors-wrong-stays-on#39363 Author: Sydius
Subject: 6609
Posted: 16 Nov 2017 at 10:29am

I went ahead and issued an RMA with NewEgg, but I would still love to hear anybody's opinion about this out of curiosity. My thinking is that my CPU is probably OK because it would have seriously ruined it immediately if it was actually pumping in 4V, right? It shouldn't be able to boot to Windows and compile a bunch of software (as was my test of my new toy).]]> Thu, 16 Nov 2017 10:29:51 +0000 https://forum.asrock.com/forum_posts.asp?TID=6609&PID=39363&title=x399-fatal1ty-temperature-sensors-wrong-stays-on#39363 <![CDATA[X399 Fatal1ty temperature sensors wrong, stays on : I also notice that the 1.8V is...]]> https://forum.asrock.com/forum_posts.asp?TID=6609&PID=39355&title=x399-fatal1ty-temperature-sensors-wrong-stays-on#39355 Author: Sydius
Subject: 6609
Posted: 16 Nov 2017 at 4:39am

I also notice that the 1.8V is at over 4V. That seems scary! Have I fried my CPU?

I'm hoping the sensors are all just wrong because, like I said, Windows boots fine and nothing seems amiss otherwise. The AMD overclocking tool did show it going up to 4.1 GHz boost even though the max is supposed to be 4 GHz and I did not change any settings in UEFI and did not touch any settings in the tool. I hope that's also just a rounding error or something.
]]> Thu, 16 Nov 2017 04:39:35 +0000 https://forum.asrock.com/forum_posts.asp?TID=6609&PID=39355&title=x399-fatal1ty-temperature-sensors-wrong-stays-on#39355 <![CDATA[X399 Fatal1ty temperature sensors wrong, stays on : Here are some images:https://p...]]> https://forum.asrock.com/forum_posts.asp?TID=6609&PID=39354&title=x399-fatal1ty-temperature-sensors-wrong-stays-on#39354 Author: Sydius
Subject: 6609
Posted: 16 Nov 2017 at 4:27am

Here are some images:

https://photos.app.goo.gl/0LJLbHRlE547p3uP2

https://photos.app.goo.gl/olZqVqH9aTsJWyFA3

Looks like parts of Korean characters, not Japanese, but definitely not right...
]]> Thu, 16 Nov 2017 04:27:35 +0000 https://forum.asrock.com/forum_posts.asp?TID=6609&PID=39354&title=x399-fatal1ty-temperature-sensors-wrong-stays-on#39354 <![CDATA[X399 Fatal1ty temperature sensors wrong, stays on : Symptoms:UEFI &#034;advanced mode&#034;...]]> https://forum.asrock.com/forum_posts.asp?TID=6609&PID=39352&title=x399-fatal1ty-temperature-sensors-wrong-stays-on#39352 Author: Sydius
Subject: 6609
Posted: 16 Nov 2017 at 4:19am

Symptoms:
  • UEFI "advanced mode" CPU temperature reads as 204 C
  • UEFI "advanced mode" motherboard temperature reads as -1 C
  • UEFI "easy mode" temperature alternates between Japanese characters and the date
  • After shutdown, peripherals turn off but fans and power LED never turn off until I hold down the power button for ~5 seconds
  • The hex display on the motherboard reads "00" and the lights glow red
Windows boots fine, everything runs OK, the AMD ThreadRipper utility displays the CPU temperature as being ~34 C. No instability and no other problems that I can find.

I updated the UEFI firmware to the latest version and reset the CMOS using the button on the motherboard. Neither fixed these issues.

Do I have a bad motherboard? I assume it's the motherboard since both sensors are reporting the wrong numbers (my house is nowhere near freezing). Could it be the CPU, though? 
]]> Thu, 16 Nov 2017 04:19:45 +0000 https://forum.asrock.com/forum_posts.asp?TID=6609&PID=39352&title=x399-fatal1ty-temperature-sensors-wrong-stays-on#39352