Jump to content
AIDA64 Discussion Forum
Hurricane28

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

Recommended Posts

2 hours ago, tomy100 said:

Thank you very much for your answer.

Does the latest beta version of AIDA64 improve behavior?

Is Asus really looking for a solution? This problem seems to have been known for a long time and no bios have tried to solve this problem.

Does not Asus seek to hide the problem, and therefore never solve it?

Make sure to always use the latest AIDA64 beta build on Asus ROG products -- although in this particular case it wouldn't help much I'm afraid.  As a temporary workaround you can try disabling EC (Embedded Controller) support in AIDA64 / main menu / File / Preferences / Stability, but that may still not get things 100% stable.

We've discussed the issues and came up with a possible solution with Asus' engineers.  So yes, they are absolutely committed now to fix the collision issue.

Share this post


Link to post
Share on other sites

Thank you for your help. Unfortunately the problem remains the same.

Out of curiosity I tried with another software (HWInfo), when I opened the latter he warned me against the use of the EC.
I nevertheless accepted the risks.

I did not experience any crash with HWInfo, either in fan speed or in the display of my ROG Front base.

Could it be that a solution (given by Asus?) Could be integrated in HWinfo but not in AIDA64?

Thank you in advance for your answer.

Share this post


Link to post
Share on other sites
On ‎2018‎. ‎01‎. ‎05‎. at 9:15 AM, tomy100 said:

Thank you for your help. Unfortunately the problem remains the same.

Out of curiosity I tried with another software (HWInfo), when I opened the latter he warned me against the use of the EC.
I nevertheless accepted the risks.

I did not experience any crash with HWInfo, either in fan speed or in the display of my ROG Front base.

Could it be that a solution (given by Asus?) Could be integrated in HWinfo but not in AIDA64?

Thank you in advance for your answer.

No, it's not the same thing.  The EC warning is due to EC bank switching, which is indeed a dangerous thing to perform when AI Suite is installed.

Share this post


Link to post
Share on other sites

Thank you for your reply.

How do you explain the difference in behavior between AIDA64 and HWinfo?

AIDA64 + ROG Front Base = Placing the display + fans to 100% after a few minutes
HWinfo + ROG Front Base = No crash despite 3 days when the PC remained on?

Share this post


Link to post
Share on other sites
On ‎2018‎. ‎01‎. ‎09‎. at 5:01 PM, tomy100 said:

Thank you for your reply.

How do you explain the difference in behavior between AIDA64 and HWinfo?

AIDA64 + ROG Front Base = Placing the display + fans to 100% after a few minutes
HWinfo + ROG Front Base = No crash despite 3 days when the PC remained on?

I have no idea.  HWiNFO is not our software, so we don't have deep understanding on the way it handles your system.

Share this post


Link to post
Share on other sites

Good to hear there is some progress about this issue.

I understand that the problem occurs when more software programs access the EC sensor and therefore become erratic. hardwareinfo64 found an solution but as for Aida64 there is none as of today. I tried launching Aida64 last week with the latest beta and it gave me errors and my fans also spin up to the max without ramping down.

 

The EC event ID in Windows is a different thing though which is not related to this as its an Microsoft issue i've been told. There is more about this in the overclock.net ROG thread.

Share this post


Link to post
Share on other sites

Thnx for the update but i already read that. I am an member of overclock.net too.

Elmor said this before and its been like 6 months and still no fix.. I doubt they fix it but i stay positive.

 

Share this post


Link to post
Share on other sites

Hi guys,

I have a new Asus ROG x470 board and i uses Aida64 the latest version and within 15 minutes i have the fan issue again..

Why is this still not fixed after all these months is my question? I really want to use your program but i can't even run cash benchmark because of this fan issue...

Plz contact Elmor ( Jon)  From asus ROG in order to solve this.

Thank you.

Share this post


Link to post
Share on other sites
On ‎2018‎. ‎04‎. ‎29‎. at 9:14 AM, Hurricane28 said:

Hi guys,

I have a new Asus ROG x470 board and i uses Aida64 the latest version and within 15 minutes i have the fan issue again..

Why is this still not fixed after all these months is my question? I really want to use your program but i can't even run cash benchmark because of this fan issue...

Plz contact Elmor ( Jon)  From asus ROG in order to solve this.

Thank you.

The issue will be fixed when the new sensor solution will be implemented in both X370 and X470 chipset based Asus motherboards.  Jon is still working on it AFAIK.

Share this post


Link to post
Share on other sites

I see,

I really hope this is going to be fixed soon as i really need and want to use Aida64 again which i can't now.

But the question remains, why do i only have problems with Aida64 and not with other programs.

Share this post


Link to post
Share on other sites

New Beta-BIOS 6201 released:

• AGESA 1.0.0.2c
• Fixes fan calibration wrongly detecting 90+% min duty
• Fixes APM settings (restore power on AC loss)
• Adds an ACPI-WMI interface for sensor readings. It's the first release and may still have bugs. For example there's an issue where some temperatures and VRM current will read 0 at the moment. Latest HWInfo64 Beta will pick this up, not sure about others. This is the SIO sensor fix you've been waiting for. It will only be working fully when all software are using it.
 

Now waiting for an AIDA64-Update…

Share this post


Link to post
Share on other sites
On ‎5‎/‎29‎/‎2018 at 6:30 PM, Grainger said:

New Beta-BIOS 6201 released:

• AGESA 1.0.0.2c
• Fixes fan calibration wrongly detecting 90+% min duty
• Fixes APM settings (restore power on AC loss)
• Adds an ACPI-WMI interface for sensor readings. It's the first release and may still have bugs. For example there's an issue where some temperatures and VRM current will read 0 at the moment. Latest HWInfo64 Beta will pick this up, not sure about others. This is the SIO sensor fix you've been waiting for. It will only be working fully when all software are using it.
 

Now waiting for an AIDA64-Update…

We're already working on it ;) The new WMI interface will be implemented in other AM4 and TR4 Asus motherboards as well, so hopefully soon all such motherboard owners will have a stable monitoring solution.

  • Like 1

Share this post


Link to post
Share on other sites
21 hours ago, Fiery said:

We're already working on it ;) The new WMI interface will be implemented in other AM4 and TR4 Asus motherboards as well, so hopefully soon all such motherboard owners will have a stable monitoring solution.

I'm glad to hear that. ;)

Share this post


Link to post
Share on other sites
On ‎5‎/‎31‎/‎2018 at 4:06 PM, Grainger said:

I'm glad to hear that. ;)

Here's the first AIDA64 beta that supports the new Asus WMI sensor interface:

https://www.aida64.com/downloads/latesta64xebeta

You can enable/disable Asus WMI sensor support in AIDA64 / main menu / File / Preferences / Stability.  It is enabled by default.

It requires a BIOS interface, so it will only work in case the motherboard BIOS supports Asus WMI.  If it doesn't, and you flash a new BIOS that does support it, AIDA64 will automatically switch to using the WMI interface right away.

The current implementation supports Asus Crosshair VI Hero, Crosshair VII Hero and Zenith Extreme motherboards.  Other motherboards are partly or fully supported by the current implementation.  When a certain motherboard is not fully supported, make sure to right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first.  That dump will enable us to fine-tune the Asus WMI implementation and adjust it to support new motherboards.

We've tested the current implementation with the following motherboard + BIOS combinations with success:

- Crosshair VI Hero / 6201
- Crosshair VII Hero / 0702

Everyone: please let us know how it works on your motherboards ;) 

Share this post


Link to post
Share on other sites

Thx.

Received 5.97.4640 Beta with the Auto-Update.

Asus WMI Sensor is enabled by default.

All seems to be fine, only the sensor reading from my Corsair H110i AiO-Pump displays 0 rpm in the sensorpanel. But after assigning the sensor new to the AiO its running too.

 

PS: should Asus ATKEX Sensor (Asus ROG) enabled too?

Share this post


Link to post
Share on other sites
9 hours ago, Grainger said:

Thx.

Received 5.97.4640 Beta with the Auto-Update.

Asus WMI Sensor is enabled by default.

All seems to be fine, only the sensor reading from my Corsair H110i AiO-Pump displays 0 rpm in the sensorpanel. But after assigning the sensor new to the AiO its running too.

PS: should Asus ATKEX Sensor (Asus ROG) enabled too?

Thank you for your feedback.  No, ATKEX is a different interface, so that setting does not have any affect on Asus WMI.

Share this post


Link to post
Share on other sites
On 6/3/2018 at 9:31 PM, Fiery said:

Here's the first AIDA64 beta that supports the new Asus WMI sensor interface:

https://www.aida64.com/downloads/latesta64xebeta

You can enable/disable Asus WMI sensor support in AIDA64 / main menu / File / Preferences / Stability.  It is enabled by default.

It requires a BIOS interface, so it will only work in case the motherboard BIOS supports Asus WMI.  If it doesn't, and you flash a new BIOS that does support it, AIDA64 will automatically switch to using the WMI interface right away.

The current implementation supports Asus Crosshair VI Hero, Crosshair VII Hero and Zenith Extreme motherboards.  Other motherboards are partly or fully supported by the current implementation.  When a certain motherboard is not fully supported, make sure to right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first.  That dump will enable us to fine-tune the Asus WMI implementation and adjust it to support new motherboards.

We've tested the current implementation with the following motherboard + BIOS combinations with success:

- Crosshair VI Hero / 6201
- Crosshair VII Hero / 0702

Everyone: please let us know how it works on your motherboards ;) 

Great news! Hopefully its really working this time. What is this new 0702 BIOS? I don't see any or is that a new one we don't have yet?

 

Thnx.

Share this post


Link to post
Share on other sites
6 hours ago, Hurricane28 said:

Great news! Hopefully its really working this time. What is this new 0702 BIOS? I don't see any or is that a new one we don't have yet?

 

Thnx.

It's a non-public BIOS update ... right now.  It should be out there soon.

Share this post


Link to post
Share on other sites

C6H and BIOS 6201:

With BIOS 6201 and with AIDA64 5.97.4640 Beta there are no more fan issues since 1 week.

I tested the system for many hours under realistic conditions (encoding more than 10 blurays with handbrake).

Share this post


Link to post
Share on other sites
17 hours ago, Grainger said:

C6H and BIOS 6201:

With BIOS 6201 and with AIDA64 5.97.4640 Beta there are no more fan issues since 1 week.

I tested the system for many hours under realistic conditions (encoding more than 10 blurays with handbrake).

Sounds great, thank you!

Share this post


Link to post
Share on other sites

On the Zenith extreme using bios 1003 (latest official one) it does not work -- after a while it ramps the fans and sound like my computer is going to take off.

 

any hits Fiery? or the new WMI interface is not there for Zenith yet?

Share this post


Link to post
Share on other sites
12 hours ago, aTsgR said:

On the Zenith extreme using bios 1003 (latest official one) it does not work -- after a while it ramps the fans and sound like my computer is going to take off.

any hits Fiery? or the new WMI interface is not there for Zenith yet?

Zenith Extreme has no public BIOS that would support the new Asus ACPI WMI interface yet.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Similar Content

    • By Ojustaboo
      Hi
      A few odd things. I've recently added cheap water cooling to my PC.
      It might be a misunderstanding  (or reconfiguration) on my pat. 
      1) Sometimes when I start the PC and AIDA64  auto starts, it only shows the 3 white fan options as shown in the bottom of pic "Turn on PC".
      If I close AIDA64 and restart it, or reboot, it comes up with the 5 fans it should have (see bottom of pic "Restarted"), 
      2) very occasionally it starts correctly by showing the 5 fan options, but will say both the GPU Rad fan and the Temp Side Fan are 0 RPM even though they are spinning (sorry haven't got a pic for this)
      Note, Power supply fan should be 0 RPM as it's a quite PS that only starts the fan if needed
      3) With my CPU watercooler, I installed Corsairs iCUE fan control software (I presume this is needed to control the fans?).  That software shows completely different CPU temps to yours. When running your Stress Test, (all in C)
      After 40 seconds, yours says 39 , iCUE says 33.7
      After 2 mins, yours says 40  iCUE says 34.3
      After 3 mins yours says 40  iCUE says 34.8
      After 4 mins yours says 41, iCUE says 35.1
      After 6 mins yours says 41, iQUE says 35.6
      After 11 mins yours says 42 iQUE says 36.1
      Pics of the above attached.  I left it running for a while longer, but the temp stayed fluctuating  between  41/42.
      Then after I'd stopped your stress test for a couple of mins or so your s/w says 29, iQUE says 34.6
       
      Turned on PC

       
       
      Restarted PC

       
       
      AIDA64 CPU Stress test after 40 secs

       
       
       
      AIDA64 CPU Stress test after 2 mins

       
       
       
      AIDA64 CPU Stress test after 3 mins

       
       
       
      AIDA64 CPU Stress test after 4 mins

       
       
       
      AIDA64 CPU Stress test after 6 mins

       
       
       
       
      AIDA64 CPU Stress test after 11 mins

       
       
       
      Stress test stopped for a couple of mins or so

       
       
      System Spec:
      Asus Vulcan Pro ROG Headset
      Corsair Neutron GTX SSD 240GB (C drive, System)
      Samsung 500GB EVO SSD  (D drive, Games)
      SanDisk SSD Plus 480GB (E drive, Steam Library) 
      Samsung 500GB EVO SSD  (F drive , Music S/W)
      Samsung 500GB EVO SSD  (G, H, I drive,  Docs, More Programs, Email)
      Toshiba HDwe140 4TB  (External enclosure, only plugged in to do backups) 

      XFX RADEON RX480 Black Edition OC
      Utech MMO Gaming Mouse 
      Logitech G510 Keyboard
      Razer Orbweaver Chrome
      Focusrite Saffire Pro 24 Audio interface
      Dell U2713HM monitor running at 2560 x 1440
      BenQ GW2470 runing at 1920 x 1080
      Intel Core i7 3820 a2011  3600 MHz
      Asus P9X79 Socket 2011 ATX Motherboard
      32GB Corsair Vengance DDR3 RAM
      Win 10 Pro

      Corsair 750 Watt HX750i Fully Modular ATX PSU/Power Supply
      Corsair Hydro H55 on GPU
      Corsair Hydro H100 v2 on CPU
      NTZX H440 Mid ATX PC case
       
    • By Deckard
      Hello,
      I've moved this to a separate thread.
      Ive rolled back to 4900 and the sensor page is now blank, the process is stuck detecting and end task process does not work as I get "access denied" this is persistent in removal and re-install of AIDA 64 ex

      can you tell me if all check boxes ticked in the stability page for the following, which one 
      ASUS WMI
      ACPI ACCESS
      ASUS ROG

      Thanks again for the help
    • By Deckard
      Hi,
      All of the system fans are no longer appearing in the sensor page Using AIDA64 extreme 5.99.4944 Beta
      RAD 1 header
      RAD 2 Header
      Chassis fan
      I cannot remember when it happend,  just noticed another post and I checked mine. same problem
       

    • By sirlock
      Hi All, 
      Firstly I love AIDA64. It is so feature rich I can't believe I used anything else for so long! I spent 5 hours yesterday fine tuning my LCD panel display on my Android Tablet!
      I am running a Threadripper System with a ASUS ROG Zenith Extreme X399 TR4 Motherboard. 98% of the sensors are there there, there are just a few missing. For the Fans the latest AIDA Beta shows CPU and CPU OPT and CHA Fan 2. What is missing is CHA FAN 1, H_AMP_FAN, W_PUMP+ and the 3 CHA FANS on the extension board that Plugs into the EXT_FAN header.
      As I am running a TR system that runs warm it important to be able to monitor the H_AMP_FAN and W_PUMP+ connectors as that will tell me if my Liquid Cooler is operating properly. 
      Let me know if I can provide any other info or testing to help.
      Regards,
      Lachlan.
    • By Koithim
      Hey there,
      I recently upgraded my pc, i changed 3 things:
      MB: Maximus XI Extreme
      CPU: 9900k
      Cooler: Ryujin 360.
      Since then aida64 takes a very long time to start, become randomly unresponsive for random amount of time, sensor panel too. Aida64 never crash, it just become unresponsive randomly for a random time.
      I uninstalled Aida, did registry cleaning, rebooted, re-installed Aida and same thing is happening.
       
      Any help would be appreciated, thank you.
       
      Koithim
       
×