Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12009

  • Joined

  • Last visited

  • Days Won

    525

 Content Type 

Everything posted by Fiery

  1. Fiery
    Thank you. I'm afraid we need to keep looking for the mysterious device that would provide the missing sensor readings... I'll let you know in this topic if we can find it.
  2. Fiery
    Thank you for the data. 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 how it works
  3. Fiery
    We've implemented it in the latest AIDA64 beta update available at: https://www.aida64.com/downloads/latesta64xebeta
  4. Fiery
    Please let me know what is the arrangement of the displays when it comes to Windows Desktop. Like are they connected horizontally, with the smaller display on the left? Or are they vertically connected with the smaller display on the top?
  5. Fiery
    Thank you for your feedback
  6. Fiery
    Thank you. It's rather odd, now it really should work. Can you please post an updated screen shot of the Computer / Sensor page of AIDA64?
  7. Fiery
    You're using a very old version of AIDA64. SMART information for RAID members of Intel RAID controllers is fully provided by AIDA64, but an old version may not support the latest RAID controllers. So it would be best if you could upgrade to the latest AIDA64 version of 5.92: https://www.aida64.com/downloads/latesta64ee
  8. Fiery
    No, it's more like some deep secret or issue in the "bowels" of Windows. It's definitely software related, but quite frankly, I have no idea what could cause it
  9. Fiery
    You can simply enter the license once, on your main computer. AIDA64 will save (copy) the license into a file called PKEY.TXT that you can find in AIDA64 installation folder. Or the folder where you've started AIDA64.EXE from, in case you use a portable package. You can then take the PKEY.TXT file and distribute it along with the other files of AIDA64 in the same ZIP package.
  10. Fiery
    The hardware failure in this particular case is most likely caused by an excessive RAM setting that makes the RAM modules generate CRC errors occasionally. If it were a lot worse, Windows would fail to boot up. Try to lower the RAM frequency a notch, like from DDR4-3000 to DDR4-2800, it should help.
  11. Fiery
    Well, it all comes down to how Windows manages physical and logical drives internally. And drive re-scanning and potentially re-ordering as well can occur by a number of reasons, not just when you connect an external drive. It's very difficult to diagnose this issue, unless you are able to find out what triggers it to go wrong. Maybe when you connect an USB device, like a printer or headphones? Maybe occasionally you connect/disconnect a different kind of external drive, like a flash drive that you don't expect to be monitored?
  12. Fiery
    Thank you. Does your Windows user have administrator privileges? Are you sure AIDA64 is properly installed, so it can load its kernel driver from its installation folder?
  13. Fiery
    You can also log the readings using the Logging facility, or have a Min/Max/Average of the values collected by the AIDA64 System Stability Test.
  14. 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.
  15. 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.
  16. 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.
  17. Fiery
    We don't have a preferred method. Anything could work, as long as the bootable Windows platform includes WoW64.
  18. Fiery
    I've sent you the download link in private message. Regards, Fiery
  19. Fiery
    Is phantom throttle different to "classic" throttling of Intel processors, dating back to Pentium II ?
  20. Fiery
    Thank you for your feedback. The workaround should work with RS4 Insider Preview Build 16353 as well
  21. 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
  22. 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.
  23. Fiery
    What version and build of Windows are you using on your computer?
  24. 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.
  25. 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.
×
×
  • Create New...