Jump to content
AIDA64 Discussion Forum
facboy

fixed: Asus Maximus X Hero not all sensors detected

Recommended Posts

hi,

i have a Maximus X Hero (Z370) and not all the sensors appear to be detected by AIDA64.  This is the ISA sensor dump, do you need others?

------[ Versions ]------

Program Version : AIDA64 Extreme v5.92.4370 Beta
BenchDLL Version: 4.3.759-x64
Windows Version : Microsoft Windows 10 Pro 10.0.16299.19 (64-bit)

------[ Motherboard Info ]------

Motherboard ID      : 63-0100-000001-00101111-090216-Chipset$0AAAA000_BIOS DATE: 10/11/17 22:18:29 VER: 05.0000C
Motherboard Model   : Asus ROG Maximus X Hero
Motherboard Chipset : Intel Union Point Z370, Intel Coffee Lake-S

DMI MB Manufacturer : ASUSTeK COMPUTER INC.
DMI MB Product      : ROG MAXIMUS X HERO
DMI MB Version      : Rev 1.xx
DMI MB Serial       : 170808594502414
DMI SYS Manufacturer: System manufacturer
DMI SYS Product     : System Product Name
DMI SYS Version     : System Version
DMI SYS Serial      : System Serial Number
DMI BIOS Version    : 0505

ITE SuperIO Port           = 00h
ITE SuperIO HWMonitor Port = 0000h     (    0000h /     0000h)
ITE SuperIO HWMonitor MMIO = 00000000h (00000000h / 00000000h)
ITE SuperIO Device ID      = 0000h     (    0000h /     0000h)
ITE SuperIO Version        = 00h       (      00h /       00h)

Winbond SuperIO Port              = 2Eh
Winbond SuperIO HWMonitor Port/60 = 0290h (0290h / 0000h)
Winbond SuperIO HWMonitor Port/64 = 0A00h (0A00h / 0000h)
Winbond SuperIO Device ID         = D121h (D121h / 0000h)
Winbond Sensor ID A3/5C/reg$58    = FF / FF / FF

Fintek SuperIO Port           = 00h
Fintek SuperIO HWMonitor Port = 0000h (0000h / 0000h)
Fintek SuperIO Device ID      = 0000h (0000h / 0000h)

SMSC SuperIO Port           = 00h
SMSC SuperIO HWMonitor Port = 0000h (0000h / 0000h)
SMSC SuperIO Device ID      = 0000h (0000h / 0000h)

ASpeed SuperIO Port = 00h

------[ NCT6791 ISA Sensor Device at 0A00 ]------

0000  32 7D D3 D2  7E 12 00 D3  C3 7F 54 92  7F 4B 93 00
0010  1A 1B 80 2C  11 11 00 2A  00 1A 1A 1A  1A 1A 1A 00
0020  1A 02 99 99  99 99 FF 99  00 00 00 00  00 00 FF 1F
0030  FF 1F FF 1F  FF 1F FF 1F  FF 1F 00 00  00 00 00 00
0040  00 00 00 00  00 00 00 00  00 00 00 00  99 99 99 99
0050  FF 99 1D 40  00 00 00 00  00 00 00 00  00 00 00 00
0060  00 00 00 FF  FF FF FF FF  FF FF FF FF  FF FF FF 00
0070  00 1A 00 FE  00 1D 1B 00  FF FF FF FF  FF FF FF FF
0080  FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF
0090  FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF
00A0  FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF
00B0  FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF
00C0  FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF
00D0  FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF
00E0  FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF
00F0  FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF

     10    11    12    13    1B    20    52    71    73    75
T:   26    27   128    44    26    26    29    26   254    29
T:   26    27   128    44    26    26    32    26   254    32
T:   26    27   128    44    26    26    29    26   254    29
T:   26    27   128    44    28    26    29    28   255    29
T:   26    27   128    44    28    26    28    28   255    28
T:   26    27   128    44    28    26    28    28   255    28
T:   26    27   128    44    27    26    28    27   254    28
T:   26    27   128    44    27    26    28    27   254    28
T:   26    27   128    44    26    26    28    26   254    28
T:   26    27   128    44    27    26    28    27   255    28

   0000 0001 0002 0003 0004 0005 0006 0007 0008 0009 000A 000B 000C 000D 000E 000F
V:  4E   7E   D4   D3   7E   12   00   D3   C3   7F   54   92   7F   4B   93   00   [ VID = 1.27283 V ]
V:  4E   7E   D4   D3   7E   12   00   D3   C3   7F   54   92   7F   4B   93   00   [ VID = 1.24060 V ]
V:  4E   7E   D4   D3   7E   12   00   D3   C3   7F   54   92   7F   4B   93   00   [ VID = 1.29883 V ]
V:  30   7E   D4   D3   7E   12   00   D3   C3   7F   54   92   7F   4B   93   00   [ VID = 1.32886 V ]
V:  30   7E   D4   D3   7E   12   00   D3   C3   7F   54   92   7F   4B   93   00   [ VID = 0.99890 V ]
V:  30   7E   D4   D3   7E   12   00   D3   C3   7F   54   92   7F   4B   93   00   [ VID = 1.34814 V ]
V:  30   7E   D4   D3   7E   12   00   D3   C3   7F   54   92   7F   4B   93   00   [ VID = 1.29773 V ]
V:  37   7E   D4   D3   7E   12   00   D3   C3   7F   54   92   7F   4B   93   00   [ VID = 1.23706 V ]
V:  37   7E   D4   D3   7E   12   00   D3   C3   7F   54   93   7F   4B   93   00   [ VID = 0.88184 V ]
V:  2F   7E   D4   D2   7E   12   00   D3   C3   7F   54   93   7F   4B   93   00   [ VID = 0.75378 V ]

------[ ACPI Temperatures & Fans ]------

_TZ_.THM0._TMP             : 
_TZ_.THM1._TMP             : 
_TZ_.THR0._TMP             : 
_TZ_.THR1._TMP             : 
_TZ_.TZ00._TMP             : 
_TZ_.TZ01._TMP             : 
_TZ_.RTMP                  : 
_TZ_.RFAN                  : 
_TZ_.RFAN(0)               : 
_TZ_.RFAN(1)               : 
_SB_.ATKD._HID             : 
_SB_.ATKD.TMPR             : 
_SB_.PCI0.LPC0.EC0_.CCTV   : 
_SB_.PCI0.LPC0.EC0_.LRPM   : 
_SB_.PCI0.LPC0.EC0_.HRPM   : 
_SB_.PCI0.SBRG.EC0_.ECPU   : 
_SB_.PCI0.SBRG.EC0_.TACH(0): 
_SB_.PCI0.SBRG.EC0_.TACH(1): 
_SB_.PCI0.SBRG.EC0_.TAH0   : 
_SB_.PCI0.SBRG.EC0_.TAH1   : 
_SB_.PCI0.SBRG.EC0_.ST00   : 
_SB_.PCI0.SBRG.EC0_.SC01   : 
_SB_.PCI0.SBRG.EC0_.SC02   : 
_SB_.PCI0.SBRG.EC0_.SC03   : 
_SB_.PCI0.SBRG.EC0_.SC04   : 
_SB_.PCI0.SBRG.EC0_.SC05   : 
_SB_.PCI0.SBRG.EC0_.SC06   : 
_SB_.PCI0.SBRG.EC0_.TH0R   : 
_SB_.PCI0.SBRG.EC0_.TH1R   : 
_SB_.PCI0.SBRG.EC0_.F0TS   : 
_SB_.PCI0.SBRG.EC0_.F1TS   : 
_SB_.PCI0.PIB_.EC0_.TCRT   : 
_SB_.PCI0.SBRG.EC0_.CTPM   : 
_SB_.PCI0.SBRG.EC__.CPUT   : 
_SB_.PCI0.SBRG.EC__.SYST   : 
_SB_.PCI0.LPC_.EC0_.CTMP   : 
_SB_.PCI0.LPCB.EC0_.CTMP   : 
_SB_.PCI0.LPC_.EC0_.TMP1   : 
_SB_.PCI0.LPC_.EC0_.TMP2   : 
_SB_.PCI0.LPC_.EC0_.TMPI   : 
_SB_.PCI0.LPC_.EC0_.TMPV   : 
_SB_.PCI0.LPCB.EC0_.A1TP   : 
_SB_.PCI0.LPCB.EC0_.A2TP   : 
_SB_.PCI0.LPCB.EC0_.FAN0   : 
_SB_.PCI0.LPCB.EC__.TS1R   : 
_SB_.PCI0.LPCB.EC__.TS2R   : 
_SB_.PCI0.LPCB.EC__.TS3R   : 
_SB_.PCI0.LPCB.EC__.F1FL   : 
_SB_.PCI0.LPCB.EC__.F1FH   : 
_SB_.PCI0.LPCB.EC__.F2FL   : 
_SB_.PCI0.LPCB.EC__.F2FH   : 
_SB_.PCI0.LPC_.H8EC.RTMP   : 
_SB_.PCI0.LPC_.H8EC.LTMP   : 
_SB_.PCI0.LPC_.H8EC.MTMP   : 
_SB_.PCI0.LPC_.H8EC.GTMP   : 
_SB_.PCI0.LPCB.H8EC.CTMP   : 
_SB_.PCI0.LPCB.H8EC.DTMP   : 
_SB_.PCI0.LPCB.H8EC.GTMP   : 
_SB_.PCI0.LPCB.H8EC.ITMP   : 
_SB_.PCI0.LPCB.H8EC.MTMP   : 
_SB_.PCI0.LPCB.H8EC.STMP   : 
_SB_.PCI0.LPCB.H8EC.PFAN   : 
_SB_.PCI0.LPCB.EC0_.OTPC   : 
_SB_.PCI0.LPCB.EC0_.VGAT   : 
_SB_.PCI0.LPCB.EC0_.CHPT   : 
_SB_.PCI0.LPCB.EC0_.CPUT   : 
_SB_.PCI0.LPCB.EC0_.SYST   : 
_SB_.PCI0.LPCB.EC0_.DTS1   : 
_SB_.PCI0.LPCB.EC0_.DTS2   : 
_SB_.PCI0.LPCB.EC0_.DIMM   : 
_SB_.PCI0.LPCB.EC0_.FANH   : 
_SB_.PCI0.LPCB.EC0_.FANL   : 
_SB_.PCI0.LPCB.EC0_.CUTP   : 
_SB_.PCI0.LPCB.EC0_.PHTP   : 
_SB_.PCI0.LPCB.EC0_.DIMT   : 
_SB_.PCI0.LPCB.EC0_.INLE   : 
_SB_.PCI0.LPCB.EC0_.PANT   : 
_SB_.PCI0.LPCB.EC0_.F0RM   : 
_SB_.PCI0.LPCB.EC0_.F0DT   : 
_SB_.PCI0.LPCB.EC0_.F1RM   : 
_SB_.PCI0.LPCB.EC0_.F1DT   : 
_SB_.PCI0.SBRG.EC0_.CUTP   : 
_SB_.PCI0.SBRG.EC0_.PHTP   : 
_SB_.PCI0.SBRG.EC0_.DIMT   : 
_SB_.PCI0.SBRG.EC0_.INLE   : 
_SB_.PCI0.SBRG.EC0_.PANT   : 
_SB_.PCI0.SBRG.EC0_.F0RM   : 
_SB_.PCI0.SBRG.EC0_.F0DT   : 
_SB_.PCI0.SBRG.EC0_.F1RM   : 
_SB_.PCI0.SBRG.EC0_.F1DT   : 
_SB_.SAMB.TMPC             : 
_SB_.SAMB.TMPH             : 
_SB_.STR0._TMP             : 
_SB_.STR1._TMP             : 
_SB_.STR2._TMP             : 
_SB_.STR3._TMP             : 
_SB_.STR4._TMP             : 
_SB_.STR5._TMP             : 
_SB_.STR6._TMP             : 
_SB_.STR7._TMP             : 
CPUT                       : 
GPUT                       : 
SYST                       : 
FANT                       : 
BATT                       : 

 

Share this post


Link to post
Share on other sites

Thanks for the update, still missing two temperatures (W_IN and W_OUT), Temperature #1 should be called T_SENSOR and Fan #4 should be called W_PUMP+.

not sure if other fan/temp readings are missing as i don't have them physically connected.

Share this post


Link to post
Share on other sites
On ‎2017‎. ‎10‎. ‎19‎. at 8:40 PM, facboy said:

Thanks for the update, still missing two temperatures (W_IN and W_OUT), Temperature #1 should be called T_SENSOR and Fan #4 should be called W_PUMP+.

not sure if other fan/temp readings are missing as i don't have them physically connected.

Thank you for your feedback. Measuring W_IN and W_OUT would require EC (Embedded Controller) bank switching, which is a dangerous procedure to perform on Asus motherboards.  EC bank switching may collide with Asus' own AI Suite software package or its underlying service components, or the BIOS itself, and could cause system lockup or other stability issues.

T_Sensor is a generic label, meaning Temperature Sensor, that's why AIDA64 also uses a generic label for it.  It's correct that way.

On your motherboard Fan #4 will be renamed to "Water Pump" fan in the next AIDA64 beta update due in a few days from now.

Share this post


Link to post
Share on other sites

oh, that's a shame.  hwinfo reads it (but does warn about instability first).  is it possible to have this EC reading enabled as an 'advanced' option, ie at user's own risk?  i'd rather not install the ASUS software as it tends to be v buggy (and unstable, ironically).

Share this post


Link to post
Share on other sites
22 hours ago, facboy said:

oh, that's a shame.  hwinfo reads it (but does warn about instability first).  is it possible to have this EC reading enabled as an 'advanced' option, ie at user's own risk?  i'd rather not install the ASUS software as it tends to be v buggy (and unstable, ironically).

We may enable that in the near future, but only via a Stability option as you've suggested.

Share this post


Link to post
Share on other sites

not really an AIDA64 problem, but are these errors in the Windows Event Viewer due to the BIOS, or is it some other  piece of software I have on the system?

: 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.

 

Share this post


Link to post
Share on other sites
On ‎2017‎. ‎10‎. ‎31‎. at 7:59 PM, facboy said:

not really an AIDA64 problem, but are these errors in the Windows Event Viewer due to the BIOS, or is it some other  piece of software I have on the system?


: 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.

 

It should be due to the BIOS accessing EC registers.

Share this post


Link to post
Share on other sites

We've implemented Asus EC bank switching in the latest AIDA64 beta build:

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

You need to enable both Embedded Controller (EC) support and Embedded Controller (EC) bank switching in AIDA64 / main menu / File / Preferences / Stability.  That will unlock a few additional sensor readings on your motherboard.  Make sure to not have Asus AI Suite or any of its background services installed on your system.  If you have any of those left around, a collision may occur while AIDA64 tries to perform EC bank switching, and it may just cause a system lockup or sudden system restart.

Share this post


Link to post
Share on other sites
On 11/23/2017 at 11:10 AM, Fiery said:

We've implemented Asus EC bank switching in the latest AIDA64 beta build:

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

You need to enable both Embedded Controller (EC) support and Embedded Controller (EC) bank switching in AIDA64 / main menu / File / Preferences / Stability.  That will unlock a few additional sensor readings on your motherboard.  Make sure to not have Asus AI Suite or any of its background services installed on your system.  If you have any of those left around, a collision may occur while AIDA64 tries to perform EC bank switching, and it may just cause a system lockup or sudden system restart.

This is great news, I am assuming this is the same for the ASUS Maximus X Formula, I have one on the way.  

I am assuming that if I don't install ASUS AI Suite, then I am good to go?  The Maximus X Formula has the OLED screen that is enabled and controlled via "Live Dash" Software, have you had any issues with this software and the EC support listed above?

Thank you, 

-Jsunn

 

Share this post


Link to post
Share on other sites
14 hours ago, Jsunn said:

This is great news, I am assuming this is the same for the ASUS Maximus X Formula, I have one on the way.  

I am assuming that if I don't install ASUS AI Suite, then I am good to go?  The Maximus X Formula has the OLED screen that is enabled and controlled via "Live Dash" Software, have you had any issues with this software and the EC support listed above?

Thank you, 

-Jsunn

Yes, it should work with any Asus ROG motherboard.  We haven't tested the OLED screen yet.  You need to check if Live Dash requires any AI Suite components that may collide with the EC layer of AIDA64.

Share this post


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

Yes, it should work with any Asus ROG motherboard.  We haven't tested the OLED screen yet.  You need to check if Live Dash requires any AI Suite components that may collide with the EC layer of AIDA64.

Thank you for the reply.  The Live Dash software does not require AI Suite to be installed... at least I don't think so.  I will report back in a few days. 

-J

Share this post


Link to post
Share on other sites

I am afraid I am running into similar issues on the Asus Z370 Maximums X Code.  No VRM temp, chassis fan speeds, motherboard temp sensor, temp probe, and probably something else I am forgetting about.  AIDA extreme build 5.95.4522.  Code BIOS 1003.  Switched on both EC Support check boxes, but no change.  SMBus ACPI access also on.  No AI Suite - ever.

Share this post


Link to post
Share on other sites
On ‎2018‎. ‎01‎. ‎07‎. at 1:49 PM, XTAC said:

I am afraid I am running into similar issues on the Asus Z370 Maximums X Code.  No VRM temp, chassis fan speeds, motherboard temp sensor, temp probe, and probably something else I am forgetting about.  AIDA extreme build 5.95.4522.  Code BIOS 1003.  Switched on both EC Support check boxes, but no change.  SMBus ACPI access also on.  No AI Suite - ever.

Please upgrade to the latest beta version of AIDA64 Extreme available at:

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

Make sure to have both EC stability options enabled.

Share this post


Link to post
Share on other sites

So I had a chance to test the EC Switching with the latest version of LiveDash on my Maximus X Formula. 

I have 2 thermal sensors connected to the W_In and W_OUT headers on the motherboard. I do not have Asus AI Suite installed. 

Before I installed the latest version of LiveDash (v1.01.08) the two temperature readings seemed correct and acted normally when using the Aida64 sensor panel. 

After I installed LiveDash, I would get momentary spikes in temperature readings only on those two sensors. The spikes would shoot up to 200+ degrees. 

 

My guess is that Live Dash might be using the same type of connections that AI Suite uses. 

 

So far, I haven’t had and crashes or freezes, only the momentary spike in temp. 

 

Is there anything I can provide you to help out? 

J

Share this post


Link to post
Share on other sites
On ‎2018‎. ‎01‎. ‎20‎. at 6:12 PM, Jsunn said:

So I had a chance to test the EC Switching with the latest version of LiveDash on my Maximus X Formula. 

I have 2 thermal sensors connected to the W_In and W_OUT headers on the motherboard. I do not have Asus AI Suite installed. 

Before I installed the latest version of LiveDash (v1.01.08) the two temperature readings seemed correct and acted normally when using the Aida64 sensor panel. 

After I installed LiveDash, I would get momentary spikes in temperature readings only on those two sensors. The spikes would shoot up to 200+ degrees. 

 

My guess is that Live Dash might be using the same type of connections that AI Suite uses. 

 

So far, I haven’t had and crashes or freezes, only the momentary spike in temp. 

 

Is there anything I can provide you to help out? 

J

Yes, those spikes are because LiveDash also fiddles around the EC, and switches EC banks back and forth.  There's no real solution to that issue I'm afraid.  The only "solution" is to disable EC bank switching in AIDA64, that way you won't see any temperature spikes in LiveDash.

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 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  
    • 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.
×
×
  • Create New...