Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    11546

  • Joined

  • Last visited

  • Days Won

    489

 Content Type 

Everything posted by Fiery

  1. Fiery
    In case the core frequency of the individual CPU cores fluctuate, then AIDA64 already has got per-core frequency monitoring items for OSD Panel, SensorPanel, etc.
  2. Fiery
    That information merely means that the installed Windows edition supports that feature or not. If you remove the service, the Windows 7 Ultimate edition that you've got installed still supports it as a feature.
  3. Fiery
    Try to switch to SensorPanel, where you can specify the measurement unit for the network download/upload rate items as Mbps to convert the readings automatically to Megabits per second. With SensorPanel you can also use MB/s as network download/upload rate measurement unit to convert the values to MegaBytes per second.
  4. Fiery
    We don't have a preferred method. Anything could work, as long as the bootable Windows platform includes WoW64.
  5. Fiery
    I've sent you the download link in private message. Regards, Fiery
  6. Fiery
    Is phantom throttle different to "classic" throttling of Intel processors, dating back to Pentium II ?
  7. Fiery
    Thank you for your feedback. The workaround should work with RS4 Insider Preview Build 16353 as well
  8. Fiery
    Maybe the issue is due to the two 2TB Toshiba drives are reveresed in the "NOT OK" case? Without the drive serial number it's hard to tell which one is which. However, since the issue affects the disk activity sensor items as well, it would be logical if it was simply an ordering issue of physical drives -- as opposed to an issue of logical drives association with physical drives. I'm not sure however how and why those two 2TB drives change places in the order of physical drives. Other than hot-plugging causing Windows to rescan and possibly reorder physical drives, I don't have any other tips
  9. Fiery
    Here's the new AIDA64 beta that implements the previous workaround for Win10 Insider Preview Build 16278 as well: https://www.aida64.com/downloads/latesta64xebeta This time we've made it a bit more future-proof by enabling the workaround between all Win10 builds in the range of 16273 and 16500.
  10. Fiery
    What version and build of Windows are you using on your computer?
  11. Fiery
    You're right, 16278 carries on the issue. We need to release one more AIDA64 hotfix to get around it again. We'll do that tomorrow or worse case Friday. I'll post a message into this topic once the new AIDA64 beta build is available for download.
  12. Fiery
    Thank you. Please right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA GPU Registers. 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. Also right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA SMBus Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post.
  13. Fiery
    Can you please post a picture of how HWiNFO displays GPU power draw in Watts?
  14. Fiery
    No problem, and thank you! I'm afraid we cannot find the missing readings in those dumps. Maybe your motherboard has a 3rd sensor chip that we didn't look for before. If it's possible, please upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta And post an updated ISA Sensor Dump. We've added a deeper scanning for sensor chips for Gigabyte X299 motherboards in this new AIDA64 build. Maybe this time it will pick up a "ghost" chip
  15. Fiery
    Meanwhile, we've rolled out a new AIDA64 beta build: https://www.aida64.com/downloads/latesta64xebeta In this build we've added a new option to the Preferences / Stability page to let you disable EC (Embedded Controller) polling. That way you would lose a few sensor readings, but maybe it helps to get around the latency issues. Also, in this build we've added GPU clocks as Correction items
  16. Fiery
    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
  17. Fiery
    We've implemented a workaround for this issue in 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 how it works
  18. Fiery
    Thank you for your feedback
  19. Fiery
    It's easy to check whether the sensor module or the LCD module causes the high latency: simply just try turning off all LCD modules, and try to enable the SensorPanel. Please let me know how it changes the latency. Note that we've seen latency issues caused by the Logitech LCD API in the past. There's a chance the whole thing isn't rooted in AIDA64 at all. As for the missing features, we'll work on them GPU clock correction should come first, it's relatively easy. GPU Watts usage, I'm not sure about, since it should be supported by AIDA64 already. What video card do you have? As for sensors individual enabling/disabling: we haven't really dealt with that on the basis that the Computer / Sensor page was designed to provide just a quick glance on all the readings. If you want to further customize it, then you can go OSD Panel, where you can pick the items you want to have displayed. And, if you want to go one more step further, then there's SensorPanel and LCD, where you can not only pick which item to show, but also the visual representation of those items. About sensors AIDA64 Engineer will behave similarly to AIDA64 Extreme, so it doesn't make much sense to deal with it.
  20. Fiery
    Try to do a complete uninstall again. Uninstall AIDA64, remove all the files belonging to it, restart Windows (this is an important part to get rid of the old kernel driver). After system restart check if there're any files left over. Then install the latest beta, restart Windows again, and check if it works.
  21. Fiery
    On your motheboard, VRM temperature reading should be there, as long as you're using the latest AIDA64 beta build: https://www.aida64.com/downloads/latesta64xebeta The rest of the readings in HWiNFO (Auxiliary and AUXTIN2) both look bogus readings to me, and so they shall not be displayed at all.
  22. Fiery
    Power efficiency is calculated using a special formula that's specific to not only the PSU manufacturer, but also PSU model/SKU. And we don't consider those formulas scientific at all. So we've decided to stay away from dealing with that. The formula of course involves the power input value, so AIDA64 will not measure or detect either of them. But, it should still show the power out (both Wattages and Ampers) for the voltage rails of Corsair PSUs using Corsair Link interface.
  23. Fiery
    Thank you for your feedback
  24. Fiery
    What video adapter do you have, and what version of Windows do you have installed?
  25. Fiery
    We wanted to wait to tell final judgement on this issue until we have more info and more input. It's a Windows 10 bug indeed that plagues Windows 10 Insider Build 16273 and 16275, but only the 64-bit editions. It prevents certain software to install and use its otherwise perfectly fine kernel driver. The issue affects several software, not just AIDA64. We're already working on a workaround, but we also expect Microsoft to fix this up soon. I'll post a message into this topic once we have an update.
×
×
  • Create New...