Jump to content
AIDA64 Discussion Forum
Hurricane28

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

Recommended Posts

Hi all,

This is the second thread i make about this issue as it appears that my previous thread is forgotten or something.. 

I would like to get some help with problems i am having with the latest build of Aida64 extreme edition regarding my sensor problems which is caused by Aida64. 

I would like to know why this is happening and maybe get some feedback on this matter in order to understand why this is happening in order to fix this issues. 

I tried running the program with EC support enabled and disabled but both get the same results unfortunately. 

 

As you can see in the pictures below temps are not as they should be and in in read write program under kolom 6 row 00 you can see that its reading from register 43 which doesn't even exist.. This is the fan controlling which causes my fans to ramp up to 100% and stay there until i restart or sometimes reset my system. 

This only happens when i try to run Aida64, with or without EC sensor support. 

 

thank you. 

 

 

weird readings.JPG

EC sensor with monitoring.png

Share this post


Link to post
Share on other sites

I apologize for the late response (in your other topic).  Let's continue investigating this issue here.

If you disabled EC support already, then I don't think merely reading a SIO (Super I/O) register like at index 43h could cause such issues.  You can try dumping all SIO registers (all 256 of them) by issuing an ISA Sensor Dump, and see if any of those register readouts make the fan spin up to 100%. Right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. If you make such a dump, then please also 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.

The dump may help us understand more about your system, and may provide us tips on where to look next.  I really thought disabling EC support would cure the issues you're having on your system.


Thanks,
Fiery

Share this post


Link to post
Share on other sites

Hi, 

No problem, i am sure you meant well but it seems a little busy. 

The thing is that i am no engineer and to be honest, i have no idea what i am looking at in read write utility. I know what i know from someone called The Stilt ( you probably know him)  and he told me this. 

It seems that there is a big problem with this IT8655E Controller but not all errors are directly caused by it.. Its very complicated and it seems that even Elmor (Jon)  that is an r&d Engineer over at Asus, doesn't quite understand what is going on here. He told me that they are working on a fix for this in a firmware or BIOS but i haven't heard from him for 5 days now so i thought i will do my own investigation in what is going on with this thing. Anyway, here is the TXT file you were asking for. 

I really hope you can provide me some more information about this and can explain little more in what is going on regarding this issue. 

Thank you, much obliged. 

 

isasensordump.txt

Share this post


Link to post
Share on other sites

Thank you.  You own the infamous Crosshair VI Hero :)  That explains a lot.  On this motherboard, as The Stilt correctly stated, even Asus has issues when it comes to 3rd party software polling the motherboard sensor registers.  AIDA64 follows Jon's (who works for Asus) guidelines on how to handle the IT8655E sensor chip of Crosshair VI Hero.  If it still doesn't work 100% reliably, it's not really our fault.  We've already tweaked around it a lot, but in case Asus has further ideas on how to make it better, we can put more efforts into this.  However, we haven't heard from Jon since July, so we assumed that all issues are gone now around Crosshair VI Hero.

Share this post


Link to post
Share on other sites

Hi, 

Yes it does doesn't it... I mean, i like this board but its full of errors and sensors that doesn't even correctly work to begin with.. I mean, how is it possible that these issues originate from the 990 FX chipset era while i had similar problems and still continue to this day... This baffles me to be honest. 

Can you plz point to me how to handle this erratic sensor according to Jon's guidelines? He is very busy at the moment "fixing" this hardware problem, which is IMO not possible because its an design flaw in the sensor itself, but who knows. 

They just need to fix this ASAP as this is no cheapo board but an premium board with cheapo sensors with lots of problems... IMO they should replace this sensor for something more reliable and error free but i don't think they will to be honest. 

 

Thank you for your answer, 

Regards, 

Richard.

Share this post


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

Hi, 

Yes it does doesn't it... I mean, i like this board but its full of errors and sensors that doesn't even correctly work to begin with.. I mean, how is it possible that these issues originate from the 990 FX chipset era while i had similar problems and still continue to this day... This baffles me to be honest. 

Can you plz point to me how to handle this erratic sensor according to Jon's guidelines? He is very busy at the moment "fixing" this hardware problem, which is IMO not possible because its an design flaw in the sensor itself, but who knows. 

They just need to fix this ASAP as this is no cheapo board but an premium board with cheapo sensors with lots of problems... IMO they should replace this sensor for something more reliable and error free but i don't think they will to be honest. 

 

Thank you for your answer, 

Regards, 

Richard.

Previous Asus motherboards may have had issues about EC sensors, but now you can disable handling EC sensors in AIDA64.  So if that fix (well... more like a silly workaround) doesn't help about Crosshair VI Hero, then it's an unrelated issue to the old 990FX era issues ;)

As for Jon's guidelines: on Asus AM4 motherboards we read sensor registers using an unconventional method (MMIO) as opposed to how it works on all other motherboards where we use classic port I/O.  We also disable SMBus before reading the sensor registers, and re-enable it when we're done.  We're not keen on doing that, but that's what Jon suggested to fix the hardware collision issues.  Based on our email correspondance with Jon, those two fixes should be adequate to make AIDA64 sensor polling stable on Crosshair VI Hero and other Asus AM4 motherboards.

Share this post


Link to post
Share on other sites

Hi, 

 

I am having the same exact issues as on my 990 FX Sabertooth board which is also an Asus board.. I mean, this problem is known for a long time now and people are still reporting issues with these erratic sensors... 

I determined that its not Aida64 nor hardwareinfo64's fault but rather the lack of support from Asus side i am afraid.. 

Anyhow, you can understand that i am pretty mad about this, not about the programs but rather towards Asus because they should have fixed this by now.. 

But i digress, 

The problem is that whenever i try to read from this EC sensor by enabling it in Aida64 or hardwareinfo64, i get stability issues and huge latency issues and i am presented with this error message in Event viewer: "The embedded controller (EC) returned data when none was requested. The BIOS might be trying to access the EC without synchronizing with the operating system. This data will be ignored. No further action is necessary; however, you should check with your computer manufacturer for an upgraded BIOS".

The fix that Jon provides is not a fix but a workaround which has nothing to do with fixing the problem at hand.. Its the same as an engine light or Oil temp LED in your car lights up and you simply smash the LED instead of doing something on the engine or fill the oil or whatever.. 

The thing is that they bought and faulty EC sensor from the wrong supplier and we end up with an motherboard which cannot be monitored because if we do, we get errors like this.. 

If i disabled this EC sensor i cannot monitor my vrm's, Temp_1,PCIe etc. Basically the crucial parts which i would like to monitor which is also the reason i bought this board.

Just to be clear, i should disable EC support and SMbus like in the screenshot?

 

Thank you for your support! Much obliged by it. 

Regards,

Richard. 

Aida64 sensors.png

Share this post


Link to post
Share on other sites

Interesting, after some testing i discovered that when i use Aida64 in the background, i crash during stress testing.. When i disable Aida64 i no longer get crashes. 

Regardless the setting i use with Aida64, i keep crashing in Realbench, Cinebench R15 and IBT AVX. I don't get this problem with hardwareinfo64 tho.

Share this post


Link to post
Share on other sites

You don't need to disable SMBus support, since that particular module shouldn't cause any issues on your motherboard.  As for crashes, that can still be because of a collision between your motherboard performing various tasks around the sensor chip and EC.  Hard to tell where the issue might be exactly, but without further assistance from Asus (Jon), we cannot tweak the current sensor access solution any further :(

BTW, the crashes might also indicate generic stability issues, like due to excessive overclocking, memory configuration issue, etc.

Share this post


Link to post
Share on other sites

Hi, 

alright but i am not using Aida64 anymore since i get sensor corruption and stability issues even when i am not even enabling this EC sensor.. I understand what you are saying, Elmor (Jon) told us over at overclock.net that he is working with 3rt party software developers, you haven't hear from him yet? 

The Freezes and instability only occurs when i use Aida64 i am afraid, when i don't use Aida64 i am stable as a rock. I crashed yesterday at the same clocks i am running now but today i am stable as a rock after i reset the motherboard and pulled the battery out and i don't use Aida64 anymore. As soon as i open Aida64 i get crash because of sensor corruption or something, idk. 

I will ask Jon to contact you because this should be on Asus priority number 1 imo as this affects a lof of users.. 

Thank you for your feed back. 

 

Share this post


Link to post
Share on other sites
On ‎2017‎. ‎10‎. ‎13‎. at 6:45 PM, Hurricane28 said:

Hi, 

alright but i am not using Aida64 anymore since i get sensor corruption and stability issues even when i am not even enabling this EC sensor.. I understand what you are saying, Elmor (Jon) told us over at overclock.net that he is working with 3rt party software developers, you haven't hear from him yet? 

Not recently, no...

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


×