Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    11334

  • Joined

  • Last visited

  • Days Won

    476

 Content Type 

Everything posted by Fiery

  1. Fiery
    1) LCD screens should be sent to sleep as the computer goes to sleep, but you need to use AIDA64 v4.70 or later version. Please check if you have a proper AIDA64 release running. It's best to use the latest version of v5.92, of course 2) LCD screens should stop updating the layout as soon as the computer goes to sleep. The screen may show the last measured value for CPU utilization before the computer went to sleep though, but it's not the current value. Let me know if the screen keeps updating the values, because in that case your computer is not really sleeping
  2. Fiery
    In order to fix it up, you need to specify your fan duty cycle (%) setting in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Set Asetek fan speed. Set both speeds to the same percentage value.
  3. Fiery
    Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor 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. Also right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Embedded Controller Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery
  4. Fiery
    I've sent you a private message.
  5. Fiery
    I've sent you a private message.
  6. Fiery

    SPD

    Fiery replied to LUMBERJACK's topic in General Discussion

    What kind of computer do you have? Are you sure your RAM is equipped with a SPD chip?
  7. Fiery
    Thank you for the data. Make sure to 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.
  8. Fiery
    Yes, of course. On Rampage VI boards with a Skylake-X processor installed, VCCIN will be measured, and Vcore will show the same reading as CPU VID.
  9. Fiery
    I've sent you both the download link in private message.
  10. Fiery
    As I've stated above, we're not sure, since we've never had a chance to handle a current generation DPS-G. If you need AIDA64 support for your next PSU, then I cannot give you a guarantee right now that it would work. I can however assure you that if it doesn't work, then in case you can let us know the full model name and part number of your PSU, we'll do our best to purchase a similar unit and find out how to implement support for it. If it has a USB connection and a manufacturer supplied Windows software that can read sensor values, then in theory any other Windows utility (e.g. AIDA64 ) can be adjusted to perform the same task
  11. Fiery
    It should be due to the BIOS accessing EC registers.
  12. Fiery
    Thank you for the screen shot. Since it's called "EC", maybe it's related to the Embedded Controller. Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Embedded Controller 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. Maybe that dump would show a few registers that could lead us to find the missing sensor readings.
  13. Fiery
    I'm afraid we need a bit more time on this. Unfortunately this isn't a nut we can crack easily
  14. Fiery
    Is there a proprietary NVMe driver for Plextor/Lite-On NVMe SSDs? In your dump I can see that the NVMe SMART readout works properly for your Samsung 960 Evo drive that uses Samsung's own NVMe driver. So I assume it may be possible to get around this issue using a similar driver for Plextor/Lite-On drives.
  15. Fiery
    Thank you for the info. Yes, sandboxing is a cruel mistress, and it's not possible to get around it. Hopefully one day Microsoft will implement its own FPS and OSD feature, or implements an API that can go through the sandbox...
  16. Fiery
    We've done more research on this. As it turns out, on Asus Rampage VI Apex and Extreme boards VIN0 holds VCCIN when you have a Skylake-X processor installed; but the same register holds the Vcore when you have a Kaby Lake-X processor installed. Similar separation of register layout, based on the type of installed processor exists with other manufacturers as well. It's a recent phenomenon about the X299 platform, and should be no longer an issue once Intel commits to a single CPU architecture for each platform We'll correct the VCCIN vs. Vcore issue in the next AIDA64 beta update.
  17. Fiery
    We've dropped the idea since then, on the basis that there was not a considerable demand from users, while in the same time the multiple SensorPanel feature would have been quite complicated to implement as well.
  18. Fiery
    SMART attribute labels are not supposed to be localized, on the basis that they are highly technical terms that may suffer from translation. Also, there are a lot of those attribute names, not just the ones you can see on your particular HDD or SSD right now
  19. Fiery
    It depends on the browser you use. You need to use the splash screen I've mentioned above to find out the proper resolution to use.
  20. Fiery
    The LCD Profiling Dump automatically enables all LCD modules to measure the rendering time for every one of them in a single round. Normally those modules are only enabled if you enable them in AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD.
  21. Fiery
    Thank you for your feedback! We're planning to roll out a new stable update sometime next month.
  22. Fiery
    Thank you for your feedback! AI Suite can indeed collide with other software that also polls the EC (Embedded Controller) chip for sensor registers. Sadly, Asus still haven't made any steps to synchronize AI Suite or other software of theirs with 3rd party monitoring applications. Other than uninstalling AI Suite and all its background services there's no solution to this issue I'm afraid. As for CPU Package, there's no offset to use on any processors, as far as we know. So AIDA64 should report the accurate readout as it is provided by the CPU. If you however are adamant that there's an offset to be applied, then you can configure it in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Correction.
  23. Fiery
    The following document should help you: http://download.aida64.com/resources/lcd/aida64_lcd_guide.pdf As for the mentioned device, that is not supported by AIDA64 currently. To me it looks like a SPI connected device, in which case you need to find a way to connect it to your computer at first. Most likely you would want to connect the device to a USB port, using e.g. a FTDI FT232H bridge chip.
  24. Fiery
    It says:
  25. Fiery
    Such things could happen when the text simply doesn't fit on the screen of the mobile device, and so the browser will wrap the text into multiple lines. Did you configure the right resolution for your browser? Also, I think the font is also incorrect. It could happen when the browser running on the mobile device doesn't support the selected font. In which case you should simply use a different font, like Arial.
×
×
  • Create New...