Jump to content
AIDA64 Discussion Forum
tistou77

Bugs with probes reading (Asus Rampage VI Extreme)

Recommended Posts

Hello

With Rampage VI Extreme and System Stability Test, I have bugs with probes reading during the tests
As on the Screen, the temperature 1 indicated 201°C, but it is 24°C in reality
For VRM, I had the same thing, minimum temperature 1°C (
not visible on this screen)

Aida64.thumb.PNG.36e13bfe97064490f38f3ae24f51ea3d.PNG

 

And also, when I run the tests, Aida seems to be "blocked" after a few seconds and after 20 seconds to 1mn, it's good, the temperatures and voltages "vary" and the "Elapsed Time" goes

Thanks

Share this post


Link to post
Share on other sites

The invalid temperature readings are usually caused by another monitoring tool colliding with AIDA64 about EC (Embedded Controller) register readout.  In your case the most likely candidate for such software is Asus' own monitoring application AI Suite.  Currently there's no 100% reliable way to fix it up.  So if you'd like to avoid such collisions, make sure to uninstall AI Suite, including its background services.

As for the half a minute freezing after you start a stress test session: it's caused by Windows kernel which can get quite slow and bumpy when an application tries to allocate a huge chunk of system memory.  And that's exactly what the memory subtest of AIDA64 System Stability Test initiates right after you press the Start button.  As soon as all the system memory is allocated by the AIDA64 stress test, Windows should return back to normal responsivity.  The duration of the "bumpy" phase depends on the amount of system RAM you have installed.

Share this post


Link to post
Share on other sites

Ok for the "bumpy" phase after the start of tests
I never had this "problem" with the X99 (same amount of ram)

For the probes problem, I have never used and therefore installed AI Suite or other Asus software
During the test, only System Stability Test is open (no software in the background)

Thanks

Share this post


Link to post
Share on other sites
On ‎2018‎. ‎01‎. ‎08‎. at 10:22 PM, tistou77 said:

Ok for the "bumpy" phase after the start of tests
I never had this "problem" with the X99 (same amount of ram)

For the probes problem, I have never used and therefore installed AI Suite or other Asus software
During the test, only System Stability Test is open (no software in the background)

Thanks

The difference (between your X99 and X299 systems) might be the Windows 10 build.  In Windows 10 the higher the build number is, the slower some of the kernel calls get.  So allocating the same amount of RAM in Windows 10 Fall Creators Update could well be slower than what it used to be with Windows 10 Creators Update or Anniversary Update.

As for the EC register readout issues: do you have EC bank switching enabled in AIDA64 / main menu / File / Preferences / Stability?

Share this post


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

The difference (between your X99 and X299 systems) might be the Windows 10 build.  In Windows 10 the higher the build number is, the slower some of the kernel calls get.  So allocating the same amount of RAM in Windows 10 Fall Creators Update could well be slower than what it used to be with Windows 10 Creators Update or Anniversary Update.

As for the EC register readout issues: do you have EC bank switching enabled in AIDA64 / main menu / File / Preferences / Stability?

Ok for the version of Windows 10, I did not know
Yes I enable
EC bank switching

Thanks

Share this post


Link to post
Share on other sites
4 hours ago, tistou77 said:

Ok for the version of Windows 10, I did not know
Yes I enable
EC bank switching

Thanks

I guess then either the BIOS itself interferes sometimes with the EC register readout activity of AIDA64, or the EC sometimes becomes slightly unstable in providing the right register values.  Old older motherboards we've seen EC communication issues when the system is under heavy load -- but no glitches when the computer is idle.

Share this post


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

I guess then either the BIOS itself interferes sometimes with the EC register readout activity of AIDA64, or the EC sometimes becomes slightly unstable in providing the right register values.  Old older motherboards we've seen EC communication issues when the system is under heavy load -- but no glitches when the computer is idle.

But with other monitoring software I do not have this problem
This is related to Aida64's stress test and its monitoring ?

Share this post


Link to post
Share on other sites
13 hours ago, tistou77 said:

But with other monitoring software I do not have this problem
This is related to Aida64's stress test and its monitoring ?

I'd try to run another monitoring software and AIDA64 stress test in the same time, and see if the heavy stress makes the other software experience EC register readout glitches.  If yes, then it's a hardware issue, and not an AIDA64 related issue.

Share this post


Link to post
Share on other sites
1 hour ago, Fiery said:

I'd try to run another monitoring software and AIDA64 stress test in the same time, and see if the heavy stress makes the other software experience EC register readout glitches.  If yes, then it's a hardware issue, and not an AIDA64 related issue.

I had tested with SIV launched at the same time as the stress test of Aida64 (more information on consumptions, etc ...) and no weird temperature/voltage with SIV ;)

Share this post


Link to post
Share on other sites
On ‎08‎/‎01‎/‎2018 at 5:35 PM, tistou77 said:

And also, when I run the tests, Aida seems to be "blocked" after a few seconds and after 20 seconds to 1mn, it's good, the temperatures and voltages "vary" and the "Elapsed Time" goes

Thanks

Hello

For information, tested with SIV, HWInfo, etc... and no "bumpy phase" after start the test
Only the Aida64 benchmark window (and monitoring) freeze, the other programs do not have this "bumpy phase" with the Aida64 benchmark launched

Share this post


Link to post
Share on other sites
26 minutes ago, tistou77 said:

Hello

For information, tested with SIV, HWInfo, etc... and no "bumpy phase" after start the test
Only the Aida64 benchmark window (and monitoring) freeze, the other programs do not have this "bumpy phase" with the Aida64 benchmark launched

Please note that when an AIDA64 benchmark is launched, AIDA64 monitoring threads are put to sleep in order to avoid them interfering with the benchmark threads.  Otherwise the benchmark results would be lower.

Share this post


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

Please note that when an AIDA64 benchmark is launched, AIDA64 monitoring threads are put to sleep in order to avoid them interfering with the benchmark threads.  Otherwise the benchmark results would be lower.

Aa ok, thanks ;)

Share this post


Link to post
Share on other sites

Hello

It is also normal that during the stress test, the weather, monitoring, etc ... freeze very regularly (the time can jump 20 seconds) ?
What is annoying is that we do not know if it is Aida64 that "freezes" or if it is because of the OC (no worries with other stress test and Aida64 in the background, for monitoring)

For the "bump" at the start of the benchmark, maybe it would be better to be like this
Launch of the benchmark (Start) => allocated memory => start of the benchmark (
begin time elapsed)

Instead the benchmark starts (time elapsed), freeze (while memory is allocated) and the benchmark continues

Thanks

Share this post


Link to post
Share on other sites
On ‎2018‎. ‎03‎. ‎11‎. at 6:47 PM, tistou77 said:

Hello

It is also normal that during the stress test, the weather, monitoring, etc ... freeze very regularly (the time can jump 20 seconds) ?
What is annoying is that we do not know if it is Aida64 that "freezes" or if it is because of the OC (no worries with other stress test and Aida64 in the background, for monitoring)

For the "bump" at the start of the benchmark, maybe it would be better to be like this
Launch of the benchmark (Start) => allocated memory => start of the benchmark (
begin time elapsed)

Instead the benchmark starts (time elapsed), freeze (while memory is allocated) and the benchmark continues

Thanks

I'm confused.  Are you talking about benchmarking or stress testing? :)

Share this post


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

I'm confused.  Are you talking about benchmarking or stress testing? :)

The stress test (System Stability Test) not the benchmark :)
There is a gap between reading Computer/Sensor and the infromations with System Stability Test

The System Stability Test window "freezes" very often (noticed with the Elapsed Time that can "jump" by several seconds), and reading temperatures, voltages is not "synchronized" with the monitoring of the sensor part of Aida64 (Computer/Sensor) several tens of seconds difference

The problem comes from System Stability Stress app, because if I use another stress test and only use the
System Stability Test for reading probes for example, the window "freezes" very often (it's ok with the Computer/Sensor window)

Thanks

Share this post


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

The stress test (System Stability Test) not the benchmark :)
There is a gap between reading Computer/Sensor and the infromations with System Stability Test

The System Stability Test window "freezes" very often (noticed with the Elapsed Time that can "jump" by several seconds), and reading temperatures, voltages is not "synchronized" with the monitoring of the sensor part of Aida64 (Computer/Sensor) several tens of seconds difference

The problem comes from System Stability Stress app, because if I use another stress test and only use the
System Stability Test for reading probes for example, the window "freezes" very often (it's ok with the Computer/Sensor window)

Thanks

Have you tried it with the latest AIDA64 beta as well?

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

I'm just asking because we've recently applied a workaround to mitigate the issue you've described.

Share this post


Link to post
Share on other sites
2 minutes ago, tistou77 said:

Yes, I've tried it yesterday ;)

It's cool then :) Please let me know what subtests do you have enabled in the System Stability Test when the "jumping" occurs.  If you have the memory stress test enabled, please check it without it, and let me know if it makes a difference.  If it does,  let me know how much system RAM do you have installed, and whether you're running the latest Windows 10 stable build (of 16299) or an Insider Preview build.

Share this post


Link to post
Share on other sites

So I use CPU, FPU, Cache and Memory
I will test without "Memory" to see
I am using the latest version of Windows 10 16299
Besides, I think that the amount of memory tested is too important (98%) whereas all the other stress tests, uses ~ 90%

Share this post


Link to post
Share on other sites
3 minutes ago, tistou77 said:

So I use CPU, FPU, Cache and Memory
I will test without "Memory" to see
I am using the latest version of Windows 10 16299
Besides, I think that the amount of memory tested is too important (98%) whereas all the other stress tests, uses ~ 90%

How much system RAM you've got? 32GB? 64GB?  A lot rides on that, since it takes quite some time for Win10 to allocate big chunks of RAM.  Windows, going from WinXP through Win7 through Win8 to Win10 tends to get slower and slower when it comes to allocating huge memory blocks.  But, you may have a point there: we may need to add a new option in the System Stability Test Preferences to let you lower the default 95% memory allocation to 90% or 80%.

Share this post


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

How much system RAM you've got? 32GB? 64GB?  A lot rides on that, since it takes quite some time for Win10 to allocate big chunks of RAM.  Windows, going from WinXP through Win7 through Win8 to Win10 tends to get slower and slower when it comes to allocating huge memory blocks.  But, you may have a point there: we may need to add a new option in the System Stability Test Preferences to let you lower the default 95% memory allocation to 90% or 80%.

I have 32 GB and there is only 500 MB left available when I test with Aida64
It will be a good idea this new option

I do not know how the stress test allocates the memory, but for example with Ram Test, this stress test takes 3 to 4 seconds to allocate 90% of ram and no freeze
Same with HCI Memtest


EDIT: After I know that with RamTest the allocation of memory is faster when the Cache is also tested
For Memory + Cache: ~ 4 sec to allocate memory
Memory: ~ 12sec to allocate memory
And no freeze in both cases

Share this post


Link to post
Share on other sites

I tested with only CPU, FPU and Cache
There is just a little "lapse of time" at the beginning of the test, but the Elapsed Time always jumps (jumps from 5 to 10 seconds each time)

Share this post


Link to post
Share on other sites
16 minutes ago, tistou77 said:

If you need other tests ;)

An idea of when will be available the "new option" for memory allocation ?

We'll work on it soon.  First we need to roll out a new stable update to AIDA64 ;) 

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