Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12614

  • Joined

  • Last visited

  • Days Won

    566

 Content Type 

Everything posted by Fiery

  1. Fiery
    Thank you for the info. Let's hope in the 2nd hardware revision ASRock can fix the issues about accessing the sensor chip under Windows. There's a good chance A-Tuning Utility doesn't support H270M Pro4 because of that hardware issue...
  2. Fiery
    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.
  3. Fiery
    What processor and motherboard do you have, and what version of Windows are you using? We're not planning to enable that, since you can already do that using the SensorPanel module of AIDA64.
  4. Fiery
    That's normal, and is due to the fact that AIDA64 uses OpenCL to stress the GPU(s) in the system. And OpenCL works through the Direct3D display layer. When you use a demanding OpenCL kernel, it could cause the display to lag.
  5. Fiery
    Yes, that's a known issue of the new Catalyst drivers. We'll implement a workaround in the next AIDA64 beta update, that will effectively remove the nonsense voltage value BTW on R9 290X video cards, AIDA64 shows the GPU Vcore as "GPU VRM".
  6. Fiery
    I don't know, I'm sorry
  7. Fiery
    Thank you. We're not ready to give up yet Please also post a Super I/O Dump. You can find it in the same right-click menu where ISA Sensor Dump is.
  8. Fiery
    Thanks a lot! I've sent you another private message
  9. Fiery
    Thank you. Does it mean you've got only one of those SSDs connected to the JMB363 controller, and you've got the other one connected to the internal SATA controller of your chipset?
  10. Fiery
    Thank you. I've sent you a private message about this issue.
  11. 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. Please post a new ISA Sensor Dump. We've extended that dump to better suit the special sensor solution of your motherboard. If it's possible, please also create a screenshot (photo) of how the sensor readings look like in the BIOS Setup (a.k.a. UEFI Setup), so we can have a better understanding on what values your motherboard can measure. Thank you for your help.
  12. Fiery
    The mentioned new AIDA64 beta build is available for download at: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works
  13. Fiery
    I'm not sure why the CPU drops to 3.50 GHz. It's not supposed to do that, as long as the base frequency is properly configured as 3.60 GHz by the BIOS at bootup.
  14. Fiery
    Please give us a few more days to diagnose this issue. I'll get back to you in this topic soon. Thank you for your patience, and for the data you've submitted above
  15. Fiery
    That is actually due to an AIDA64 bug We will fix it in the next AIDA64 beta update due in a few days from now.
  16. Fiery
    Those pages show static information, which was detected or measured at the time you start AIDA64. The CPU core frequency displayed there are influenced by both Turbo Boost and the power management (power-saving) features of your CPU, namely SpeedStep and C1E (Enhanced Halt State). Dynamic clock measurement is available on the Computer / Overclock page, and the AIDA64 CPUID Panel (main menu / Tools / AIDA64 CPUID). I'm not sure what CPU-Z is doing. Please note that it's not our software, so we don't have a full understanding on what it does or what bugs it might have about clock measurement
  17. Fiery
    Thank you. Was the 4x4GB kit also DDR4-3200 and also made by Corsair?
  18. Fiery
    Since you're doing both the hardware and software (interface/API) development, maybe the most convenient solution would be to develop a protocol that is compatible with an existing alphanumeric LCD protocol, like CrystalFontz, LCD2USB or Matrix Orbital. That way your solution would be compatible with not just AIDA64 but other LCD software as well.
  19. Fiery
    We'll do that in the next AIDA64 beta update. And thank you for the dump. We'll get a set of Corsair DDR4-3200 memory modules and check it out in our own Broadwell-E test system.
  20. Fiery
    What kind of JMicron SATA controller do you have your SSDs hooked at?
  21. Fiery
    Thank you, we will fix the issue in the next AIDA64 beta update due later this week. Regards, Fiery
  22. Fiery
    Have you tried to use the latest AIDA64 beta version? It's available for download at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade.
  23. Fiery
    Have you tried to update the CFA634 firmware to the latest version? If yes, then what firmware version do you use on your device right now? Thanks, Fiery
  24. Fiery
    Thanks for the feedback, I'm glad it works now. AIDA64 may work 100% fine under a virtual machine. But when it doesn't, since it's a virtualized environment, it's very tough for us to hunt down hardware-related issues.
  25. Fiery
    IMHO the cheapest solution would be to pick up and old TFT monitor. Some of those 2nd hand parts, in the 14 to 17-inch panel range would cost $20 or $25. An example: http://www.ebay.com/itm/15-TFT-LCD-VGA-Monitor-Model-CT-V1501-/391657569911?hash=item5b309c3e77:g:Qw8AAOSwo4pYWcas Sadly, brand new, USB-connected, dedicated colour LCD screens (like LCDInfo USBD480) are way more expensive than that.
×
×
  • Create New...