Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    11554

  • Joined

  • Last visited

  • Days Won

    489

 Content Type 

Everything posted by Fiery

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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
  6. Fiery
    It's safe to use 500 milliseconds (half a second).
  7. 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.
  8. 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
  9. Fiery
    The mentioned new AIDA64 beta update is available for download at: https://www.aida64.com/downloads/latesta64xebeta
  10. 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
  11. 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...
  12. Fiery
    You can configure clock, temperature and voltage decimal digits in AIDA64 / main menu / File / Preferences / Hardware Monitoring. Regards, Fiery
  13. Fiery
    For that price you can easily buy a USB or DSub connected LCD monitor, and use the AIDA64 SensorPanel module.
  14. Fiery
    Please send us a link to a picture frame that supports such interface an can receive bitmaps via the wireless connection.
  15. Fiery
    As long as free exceeds total, it's nothing we can do about it We need the video driver to report memory usage properly.
  16. Fiery
    Thank you! That looks like a ForceWare driver bug. Via the standard nVIDIA video driver API (called NVAPI) ForceWare reports the following values when things go south: Total / Free Video Memory = 8388608 KB / 9376044 KB Obviously "free" should never exceed "total"
  17. Fiery
    Please go to AIDA64 installation folder, and create new file there called ENABLE_HWMONINIT_LOG.TXT. Then start AIDA64, go to the Computer / Sensor page, and wait 1 minute. Then close AIDA64 (if Windows allows it), or restart your computer. You should be able to find then a new file on your Windows Desktop called LowLevelLog.txt. Please copy-paste the full file into this topic, or attach it as a file to your post. After that test is done, please make sure to remove the file ENABLE_HWMONINIT_LOG.TXT from the AIDA64 installation folder to disable logging. Thanks, Fiery
  18. Fiery
    GX Typhoon RGB backlighting control will be implemented in the next AIDA64 beta update due in a few days from now. It will add 2 more sliders next to the current Brightness slider. The old slider will be responsible for controlling the intensity of the red backlighting component, and the 2 new sliders will be for blue and green.
  19. Fiery
    We would love to support any photo frames, but most of them simply do not support passing bitmap data over the USB connection, so we cannot support them.
  20. Fiery
    I'm afraid we have no plans to separate the configuration of those features. You need to further filter down the values exported, in order to get the list you need in your other software. Regards, Fiery
  21. Fiery
    Can you please create and submit a nVIDIA GPU Registers dump before and after the anomaly occurs? You can create such dumps by right-clicking 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. Thanks, Fiery
  22. Fiery
    Yes, it is a false positive. Just let it submit the file to Malwarebytes. AIDA64 files got considerably bigger because we're in the process of implementing DPI scaling (DPI awareness) in AIDA64. And it requires adding high-resolution versions of the existing graphical content (e.g. splash screen, report wizard theme image, About box logo, CPUID Panel background, icons, etc). And since we need to prepare AIDA64 to scale to 400% and even beyond that, we need to add quite large images to the resources of the main module (AIDA64.EXE) as well as to existing DLL resource modules. But don't worry, it doesn't mean AIDA64 would load those images to RAM all the time They are only used when such high DPI setting is actually in use, and even so only one of the high-resolution images is loaded, not all of them.
  23. Fiery
    AIDA64 supports up to 16 Aquacomputer devices. It can be any kind of a mix of Aquaero 4, Aquaero 5, Aquaduct, Aquastream XT/Ultimate, MPS, PowerAdjust, or Farbwerk. Regards, Fiery
  24. Fiery
    Thank you. TBM 3.0 is only supported by Core i7-6800 and 6900 Series, so we can skip that. On your particular setup the best explanation may be that EIST is disabled for some reason, and what you can see the CPU alternating between the min and max multiplier is due to C1E activity. Another explanation might be that due some BIOS pecularity the EIST states (like 14x, 16x, etc) are not properly configured in the ACPI BIOS, and Windows fails to read the in-between states. In which case even though EIST is active, Windows may not be able to fully utilize its clock speed steps granularity.
  25. Fiery
    One feature that may influence the way the CPU switches between various power states is Turbo Boost Max 3.0: http://www.anandtech.com/show/10337/the-intel-broadwell-e-review-core-i7-6950x-6900k-6850k-and-6800k-tested-up-to-10-cores/2 I'm not sure however what CPU you've got, and whether you have TBM 3.0 enabled or not. Also, when a CPU is overclocked, it may behave completely different to a similar CPU running at stock settings. So it would be very important to find out what CPU you've got, and also whether it works different without OC and special settings, so in its factory default state. It would also be interesting to see the list of PStates the BIOS Setup configures for your CPU. Also, if you disable SpeedStep (EIST), the CPU may fall back to using C1E (Enhanced Halt State), to save power. C1E only alternates between the min and max ratio, no middle steps. Same thing could happen if you (or a software) alters the Windows CPU power management settings by forcing the CPU to work at the highest ratio all the same, effectively disable SpeedStep. In which case C1E may still work, so the min and max ratios may be used, just no middle steps. BTW, you can check and modify the Windows CPU power management settings, enable/disable C1E, enable/disable Turbo Boost using the CPU Tweakings panel of AIDA64. Which you can launch from the same right-click context menu that you use for CPU Clock Monitor.
×
×
  • Create New...