Jump to content

Fiery

Administrators
  • Posts

    12286
  • Joined

  • Last visited

  • Days Won

    541

Everything posted by Fiery

  1. We do have references to 4D Systems LCDs, but they are actually not supported. We'll fix that discrepancy to clear things up.
  2. The readings look fine to me. I'm not sure why one core is colder than another one that's very close to it. It's probably due to inaccuracies in Intel's DTS (Digital Thermal Sensor) solution. DTS was not designed to allow temperature monitoring, but rather to prevent the CPU from overheating. So it doesn't have to be 100% precise, as long as it can detect the situation when the overall CPU state is considered "too hot for normal operation".
  3. It is usually caused by one of the sensor modules taking too long to update the values. Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Sensor Profiling 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. Thanks, Fiery
  4. The latest AIDA64 beta applies the -20 Celsius offset on the CPU Diode temperature reading for Ryzen 1600X, 1700X and 1800X processors. We merely follow AMD's recommendation on how to handle the Tctl based temperature readings. You can override that offset if you want, in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Correction. On that page you can also override the "CPU" temperature reading as well, BTW. As for the "CPU" temperature reading, that one comes from the motherboard sensor chip. The reading coming from that source depends on how BIOS configures the sensor chip at bootup. Gigabyte never requested us to implement an offset for that reading, so we show the raw value as it comes from the sensor chip.
  5. Thank you, but Asus Crosshair VI Hero is already supported in AIDA64 v5.90. What do you find incorrect about it?
  6. Yes, it's correct.
  7. Thank you for your feedback
  8. The reference list is part of AIDA64, it's not downloaded or updated from the internet. You can already have the up-to-date reference list, including Ryzen 7 1800X and Kaby Lake i7-7700K results if you use the latest AIDA64 beta available at: https://www.aida64.com/downloads/latesta64xebeta We've also added a Broadwell-E i7-6850K result and an Apollo Lake reference set of scores as well.
  9. Yes, it should still work. Just create that key if it doesn't exist, and put your values under there.
  10. Please upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps. Thanks, Fiery
  11. Please upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps.
  12. Thank you. We've implemented support for Norton Security v22 in the latest AIDA64 Extreme beta update available at: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works
  13. Try to update everything in Play Store, and also install any available Android platform updates for your tablet. If it still doesn't work, then I'm afraid it's a platform limitation that prevents our app from using the standard Google services. In which case we cannot fix it from our end Regards, Fiery
  14. No, it's not possible right now. You need to pick the images for each state individually, but then when you're done with one gauge, you can duplicate it on your LCD/SensorPanel layout to avoid having to go through that process again.
  15. If you can send us a sample, we'd be happy to do that
  16. Do you have an AMD processor? If yes, then please note that AMD processors do not support throttling activity detection/measurement.
  17. Thank you for your understanding and cooperation about this issue. I forgot to mention that you should ask Amazon for a refund ASAP, but you already did, so all is cool
  18. Yes, Amazon was selling pirate license keys via a fraudulent seller. We've already notified them about this issue, and they already removed the seller from their site. Our Sales Team will contact you about possible resolutions to resolve this issue. Regards, Fiery
  19. Thank you for your idea. We currently have no plans to implement a 3D benchmark. We already have the GPGPU Benchmark module that offers various tests to benchmark the compute capabilities of any modern GPUs.
  20. In case Asus finally implements the industry standard synchronization mutexes that AIDA64 and roughly a dozen other monitoring software already use for years, then we can add the missing temperatures. We've been pestering Asus about that issue for years, without luck so far though.....
  21. Thank you for letting us know about the resolution. I've checked, and both our Win7 64-bit test systems had the TdrDelay value set to 30 seconds. So that explains everything We'll display a warning message when the value is set below 8 seconds in the Registry, and offer a quick fix.
  22. You're right, it wouldn't need a http session. However, it would still require hammering the storage device with a new write operation every second or so. In the age of flash memory based devices, it's one of the worst solutions. Foobar needs to put that information into shared memory, it's a way better solution.
  23. WATER_IN and WATER_OUT temperature cannot be monitored, since they would require EC (Embedded Controller) bank switching, which is a dangerous thing to do on Asus motherboards. Switching the EC bank could cause system instability or even lockup. WATER_FLOW fan header is monitored, but it will only appear in AIDA64 if you have a fan or pump connected to it.
  24. Thank you. I'll let you know in this topic once we have a new beta update with NVMe RAID support.
  25. R That solution would imply that we need to start a HTTP client session for the URL you've quoted. That's what I meant about quite complicated and overkill. If you open a new HTTP session once a second, that uses a lot of system resources.
×
×
  • Create New...