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
    If you mean you have 2 computers with one PSU each, then it should work of course In which case on the problemous machine (where the +12V reading is missing) 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. Thanks, Fiery
  2. Fiery
    Thank you. I have to say, that's quite puzzling. Can you please check what happens if you just start AIDA64, without performing any dumps and without navigating to any info pages? If it works properly that way, then please try to go to the Motherboard / Chipset page. I suppose it would trigger the issue.
  3. Fiery
    We haven't altered the timing settings for Broadwell-E SPD SMBus, so there should be no difference between the way it works since Build 3917. We've seen such timing issues with heavily overclocked DDR4 modules. Can you please check if the memory modules are more stable at DDR4-2400 setting? (which is the default for your CPU) As for the System Tray icon right-click menu, you're right, we'll fix that in the next AIDA64 beta update. Thanks, Fiery
  4. Fiery
    Please note that AIDA64 can only measure and show +12V for a single PSU. If you have issues about your Corsair PSU, please let us know what exact PSU model is it. Thanks, Fiery
  5. Fiery
    Then maybe the issue comes up only while you're playing 3D games. Then it may be related to a video driver issue, a video card failure or a power delivery issue.
  6. Fiery
    That's not necesserily a reliable method, since the manufacturer of the phone could change (update) the chip through the lifecycle of a certain device.
  7. Fiery
    Thank you. The SMBus workaround is working properly, so the culprit is most likely the Embedded Controller. Can you please repeat only the Embedded Controller Dump, and let us know whether or not it triggers the issue? Thanks, Fiery
  8. Fiery
    Try to run only the Cache and Memory subtests for a few hours. It may work best to trigger a potential cache fault. Regards, Fiery
  9. Fiery
    It's not there simply because it's not possible to talk to the GPS chip directly So we cannot extract any information from them. Regards, Fiery
  10. Fiery
    The requested feature will be implemented in the next AIDA64 beta update due in a few days from now. I'll post a message into this topic once the new beta update is available for download. Regards, Fiery
  11. Fiery
    AIDA64 already does everything it could to support hot-swap drives on the SensorPanel and other hardware monitor modules. When a drive is appended to the list of drives when you connect it, it should work fine. However, in case connecting or disconnecting a drive triggers Windows to re-arrange the list of physical drives in the system, AIDA64 cannot do much to get around that issue. If you don't have a RAID array defined, you can try playing with the RAID-related options in AIDA64 / main menu / File / Preferences / Stability, and see if it helps to fix this up. Maybe if you disable both such options, things get a bit better. Regards, Fiery
  12. 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. Then right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> SMBus Dump (Full). Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Finally, 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. Let me know if you experience any issues after issuing each of those 3 dumps. Thanks, Fiery
  13. Fiery
    We've implemented the requested Hot Keys feature in the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta You can configure it in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Hot Keys.
  14. Fiery
    We've implemented the requested Hot Keys feature in the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta You can configure it in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Hot Keys.
  15. Fiery
    We've implemented the requested Hot Keys feature in the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta You can configure it in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Hot Keys.
  16. Fiery
    We've implemented the requested Hot Keys feature in the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta You can configure it in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Hot Keys.
  17. Fiery
    Such hard-to-explain and temporary issues could happen after moving from an older Windows release to Windows 10 Anniversary Update. I'm glad it works fine now
  18. Fiery
    It's safe to use 500 milliseconds (half a second).
  19. Fiery
    Thank you. The lack of proper sensor readings is due to the fact that AIDA64 is unable to use its kernel driver. That could be because the kernel driver file (KERNELD.X64 or KERNELD.X86) is missing, or your Windows user has no administrator privileges, or a Windows prevents to elevate the security privileges of AIDA64.
  20. Fiery
    Please right-click on the Computer / Sensor page of AIDA64 --> Copy Debug Info to Clipboard. Paste the full results into this topic. Thanks, Fiery
  21. Fiery
    The mentioned new AIDA64 beta update is available for download at: https://www.aida64.com/downloads/latesta64xebeta
  22. Fiery
    Apparently Supermicro X8DAH motherboards use SMBus multiplexing that prevents AIDA64 from reading SPD memory information and DIMM TS thermal readings. We've implemented an experimental workaround for this issue in the latest AIDA64 beta update available at: https://www.aida64.com/downloads/latesta64xebeta Please note that the new workaround may cause system lockup or instability in case it doesn't do what we expect it to do. If it's possible, please submit a new SMBus Dump (Full) dump, as well as an ISA Sensor Dump. The latter would be necessary for us to check what's wrong with the other sensor readings. Thanks, Fiery
  23. Fiery
    Yes, we still have plans, but not for the short run. Today we still cannot see a considerable demand for such a product. And since it would require us to switch compiler + switch from Ansi to Unicode (due to the new compiler) + drop Win95, Win98, NT4 and Windows 2000 support (due to the new compiler) + handle special cases about non-existing 32-bit libraries ... well, it's not something we can allocate development resources for at this time. Especially when the advantages of such a product would be very small. Apart from supporting WinPE x64, we can already do everything using the existing 32-bit AIDA64 main binary. I wish it was a lot simpler to switch to a new 64-bit compiler...
  24. Fiery
    You can configure clock, temperature and voltage decimal digits in AIDA64 / main menu / File / Preferences / Hardware Monitoring. Regards, Fiery
  25. Fiery
    For that price you can easily buy a USB or DSub connected LCD monitor, and use the AIDA64 SensorPanel module.
×
×
  • Create New...