Jump to content
AIDA64 Discussion Forum
Hurricane28

Weird sensor reports and fan controlling issues (Asus Crosshair VI Hero)

Recommended Posts

On ‎6‎/‎22‎/‎2018 at 11:01 AM, aTsgR said:

I see, thanks for this! hopefully ASUS gets its act together soon... as this is kind of unacceptable (for all boards involved).

They're working on it, but progress is slow due to many occuring issues.  They wouldn't want to release something half-baked.  So once the non-beta BIOSes supporting the new ACPI-WMI interface is out, they will be great :) 

Share this post


Link to post
Share on other sites

I Agree with him man, this is unacceptable.. The weird thing is is that only the ROG boards are affected as far as i know.. Gigabyte and MSI have no problems whatsoever.. 

They released an BIOS with the implementation but its still not fixed.. I hope they release new BIOS soon with the implementation.

Share this post


Link to post
Share on other sites
On 7/7/2018 at 5:06 PM, Hurricane28 said:

I Agree with him man, this is unacceptable.. The weird thing is is that only the ROG boards are affected as far as i know.. Gigabyte and MSI have no problems whatsoever.. 

They released an BIOS with the implementation but its still not fixed.. I hope they release new BIOS soon with the implementation.

Did the BIOS update and latest AIDA64 beta fix your problem completely? I'm asking because I still get fan issue even with latest BIOS on C6H and latest AIDA64. I turned off EC support and is using WMI to read sensor data. Does this mean that I may have other programs that is causing the trouble?

Share this post


Link to post
Share on other sites
On 6/26/2018 at 6:35 PM, Fiery said:

They're working on it, but progress is slow due to many occuring issues.  They wouldn't want to release something half-baked.  So once the non-beta BIOSes supporting the new ACPI-WMI interface is out, they will be great :) 

Hi Fiery,

 

I was trialing the C6H new BIOS 6201 and latest AIDA 64 Beta version.

The fan issue seems to be better, but I got some weird issue.

After some CPU-heavy tasks, the CPU temperature reading is off, it now drops very slowly from 65 to 59 in about 5 minutes. 

On the other hand, HWInfo64 actually have a correct reading, please see attachment.

I can't explain it, as HWInfo and AIDA64 should both be reading off the ASUS WMI sensor by now.

 

2018-07-15 17_47_19-Microsoft Edge.png

2018-07-15 17_58_05-AIDA64 Extreme.png

Edited by EpicEric6
uploading another example.

Share this post


Link to post
Share on other sites

It happened again.

It seems that only CPU temp is affacted.

CPU  Diode and other sensors are working fine.

However, all fan speeds seems to depend on CPU temp, so that in the image below, fan won't spin up.

1297483413_2018-07-1600_05_14-OSD.png.78b7f070e3b5f94d8089d9589b47f60d.png

To me it seems like prolonged pooling to fan speed can still cause the issue, no matter accessing via EC or WMI.

 

 

Share this post


Link to post
Share on other sites
On ‎7‎/‎15‎/‎2018 at 9:51 AM, EpicEric6 said:

Hi Fiery,

 

I was trialing the C6H new BIOS 6201 and latest AIDA 64 Beta version.

The fan issue seems to be better, but I got some weird issue.

After some CPU-heavy tasks, the CPU temperature reading is off, it now drops very slowly from 65 to 59 in about 5 minutes. 

On the other hand, HWInfo64 actually have a correct reading, please see attachment.

I can't explain it, as HWInfo and AIDA64 should both be reading off the ASUS WMI sensor by now.

Maybe you're comparing the wrong readings against each other?  There are multiple thermal readings for the CPU, so it's not always easy to match them with another software's own readings...

Share this post


Link to post
Share on other sites
13 minutes ago, Fiery said:

Maybe you're comparing the wrong readings against each other?  There are multiple thermal readings for the CPU, so it's not always easy to match them with another software's own readings...

I can assure you that the CPU(TDie) on HWInfo and CPU on AIDA64 is the same reading. 

They can be perfectly synced for a few hours until the AIDA64 reading stopped changing.

That's also when the fan start to play up (Similar to original method that cause IT8665E to hang)

 

If I have to guess, HWInfo is reading directly from CPU while the AIDA value still queue the motherboard? Although this reading ultimately come from the CPU.

Share this post


Link to post
Share on other sites
6 minutes ago, EpicEric6 said:

I can assure you that the CPU(TDie) on HWInfo and CPU on AIDA64 is the same reading. 

They can be perfectly synced for a few hours until the AIDA64 reading stopped changing.

That's also when the fan start to play up (Similar to original method that cause IT8665E to hang)

 

If I have to guess, HWInfo is reading directly from CPU while the AIDA value still queue the motherboard? Although this reading ultimately come from the CPU.

The "CPU" temperature reading in AIDA64 comes from the Asus WMI interface, just like the "CPU Socket" reading.  The "CPU Diode" reading however comes directly from the CPU, without the need to go through the Asus WMI interface.  The "CPU Diode" reading is also independent from the motherboard model.

Share this post


Link to post
Share on other sites
On 7/19/2018 at 8:01 PM, Fiery said:

The "CPU" temperature reading in AIDA64 comes from the Asus WMI interface, just like the "CPU Socket" reading.  The "CPU Diode" reading however comes directly from the CPU, without the need to go through the Asus WMI interface.  The "CPU Diode" reading is also independent from the motherboard model.

Hope it helps. It's not your fault, but this is what I'm talking about. That polling current ASUS WMI interface will still cause problems. On my system I've described the behavior in my previous posts.

Please see the bold line below:

HWiNFO v5.87-3490 Beta available.

Changes:

  • Enhanced sensor monitoring on MSI MS-7B10.
  • Fixed NXZT Kraken X52/X62 support on some systems.
  • Disabled ASUS WMI support on current BIOSes due to a faulty BIOS implementation.
  • Added NVIDIA GV102 and GV104.

Share this post


Link to post
Share on other sites
8 hours ago, EpicEric6 said:

Hope it helps. It's not your fault, but this is what I'm talking about. That polling current ASUS WMI interface will still cause problems. On my system I've described the behavior in my previous posts.

Please see the bold line below:

HWiNFO v5.87-3490 Beta available.

Changes:

  • Enhanced sensor monitoring on MSI MS-7B10.
  • Fixed NXZT Kraken X52/X62 support on some systems.
  • Disabled ASUS WMI support on current BIOSes due to a faulty BIOS implementation.
  • Added NVIDIA GV102 and GV104.

There indeed are minor and major issues about the new Asus WMI interface on certain Asus motherboards.  If you want, you can disable Asus WMI sensor support in AIDA64 / main menu / File / Preferences / Stability until the BIOS side gets more mature.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

  • Similar Content

    • By btmouse
      ASUS ROG all-in-one liquid CPU cooler ,
      https://www.asus.com/Cooling/ROG-RYUO-240/

      https://www.asus.com/Cooling/ROG-RYUJIN-360/
       

    • By insp1re2600
      Hi,
      Will there be support for the ryujin 360 oled screen for hardware stats on non asus motherboards pulled from wmi?
      This would be hugely appreciated.
      Thanks
    • By Mors
      I don't see the pump speed etc. for the AIO. Is this a bug or does it need to be added ?
       
      Blah again this should be in bugs section. 
    • By Rockstonicko
      So I'm about at my wits end with this, this is such a bizarre issue. I've already submitted a ticket to Asus about this and they are "researching" why this is happening for the last 2 days but I've heard nothing back yet, so I figured I'd do the same for AIDA64 and see if there are any answers/suggestions/solutions or jokes to ease my insanity.

      AIDA64 Extreme ver. 6.10.5200 is the only hardware monitoring application I'm using as I've read multiple monitoring apps can cause the ITE IT8665E Super IO chip to bug out. (Among 1000 other things, is this thing just garbage or what?)
      I'm also using the Logitech LCD configuration in AIDA64 to display temperatures/clockspeeds/VRM current/power/etc. basically all the important information I can fit spread between 4 pages on my Logitech LCD. However, I'm not monitoring fan speeds on my LCD just in case that's causing an issue.
      After anywhere from 15 minutes to 2 hours, the fans I have connected to motherboard headers will stop spinning. After doing some experimentation and attempting to control the fans after they have stopped, I've figured out that the fan logic is randomly inverting. That is, 100% fan speed becomes 0%, and 0% becomes 100%, 66% fan speed becomes 34% fan speed etc. So after it happens, I can set the fans to 0% and they will spin back up to 100%, or to 34% and they will spin back up to 66%. So I have some form of solution, albeit not an ideal one.

      I've also noticed that once the logic reverse happens, the fan sensor values in AIDA64 either freeze at their reported value, or they just show 0 RPM depending on how it's feeling at that particular instance. If I'm not running AIDA64 this will not happen, but it's an inevitability whenever AIDA64 is running. Rebooting the PC or sleep/resume will correct the issue for another 15 minutes to 2 hours.

      Here are the only options I have enabled in the stability section of AIDA64:
      Load Kernel driver Low-Level MSR Low-Level PCI Low-Level SMBus Low-Level sensor Low-Level SMART SMBus access through ACPI GPU Sensor Support I have disabled Asus WMI sensor support because I read that can solve the issue, but it hasn't helped.

      This is also the second fresh install of Windows 10 on this machine, and it has happened during both installs. I'm on the latest 5220 BIOS, and changing all of the parameters of Q-Fan in the BIOS doesn't seem to have any effect.

      Specs:
      MB: Asus Prime X470-Pro CPU: AMD Ryzen 5 3600X RAM: 16GB G.Skill Ripjaws V 3600MHz GPU: AMD Radeon RX 5700 XT SSD's: Samsung 860 EVO 256GB + Samsung 840 Pro 128GB HDD's: Seagate Barracuda 2TB + Western Digital Blue 1TB PSU: Enermax Triathlor Eco 1000W  
×
×
  • Create New...