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
    We've fixed the copy-paste issue in the latest AIDA64 beta update available at: http://www.aida64.com/downloads/latesta64xebeta Let me know how it works Thanks, Fiery
  2. Fiery
    Please try it with the latest AIDA64 beta available at: http://www.aida64.com/downloads/latesta64xebeta Let me know if it helps
  3. Fiery
    We've implemented Corsair's synchronization semaphore in the latest AIDA64 beta update available at: http://www.aida64.com/downloads/latesta64xebeta Let me know how it works Feel free to re-enable both Asetek LC sensor support and Corsair Link sensor support in Preferences / Stability, they should work from now on too.
  4. 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. Thanks, Fiery
  5. Fiery
    In such situations the usual order of business is to update the motherboard flash BIOS, re-check all memory timing settings to conform what the memory modules dictate, and check if the CPU Turbo ratios are properly configured by the BIOS. If none of those help, you may want to lower the memory clock (if it's overclocked), and loosen up a bit on the memory timings. Changing Command Rate (tCR or tCMD) from 1T to 2T could do wonders in the quest of reaching 100% system stability Regards, Fiery
  6. Fiery
    Samsung SPF picture frames would work fine, although a few users complain about the device overheating under constant communication with AIDA64 -- clearly a hardware issue. As for Odroid, we support Odroid-Show natively in AIDA64, but those are small displays VU7 seems to support direct HDMI connection, so it would work as a secondary monitor. In other words, you can expand your Windows Desktop to that display, and you won't even need to use the AIDA64 LCD module. You can instead use the AIDA64 SensorPanel feature, and import your previous LCD layout to there. Those true monitor displays are the best devices out there, although some could cost a lot of $$. You can also use virtually any DSub, DVI, HDMI or USB connected monitors in the same way as the VU7. Sometimes you can pick up 2nd hand 17-inch LCD monitors for as low as US$20. They could provide a huge space to place your sensor readings as well
  7. Fiery
    Yes, but ideally, we would like to synchronize AIDA64 with Corsair Link Software about any device access, not just when it comes to AXi, HXi and RMi Series PSUs. That way, you would be able to re-enable the 2 other, currently disabled options too. Or at least we have high hopes about being able to access any Corsair hardware by implementing Corsair's own synchronization technique If they did it the right way, and we implement it the right way, it should work fine.
  8. Fiery
    The root cause of the issue is that for some reason Corsair refuse to use the industry standard synchronization mutexes that would ensure AIDA64 and other monitoring software (like AMD OverDrive, CoreTemp, CPU-Z, EVGA E-LEET, GPU-Z, HWiNFO, HWMonitor, MSI AfterBurner, RivaTuner, SIV, SpeedFan, etc) work properly next to a running Corsair Link Software instance. Corsair came up with their own solution, and now we have to implement it in AIDA64. We'll try to do that in the upcoming days, and hopefully I'll be able to send you a new AIDA64 beta download link in this topic in a few days from now. Thank you for your patience about this issue.
  9. Fiery
    Thank you for the updated dump. We'll do some further improvements in the next AIDA64 beta update. I'll post a download link for the new beta update into this topic soon.
  10. Fiery
    Do you have a SDK for the keyboard, or any other technical details on how to talk to the keyboard? Here they didn't seem to find one, but maybe things have changed since then: https://github.com/SpoinkyNL/Artemis/issues/55
  11. Fiery
    You can try the following to resolve the issue, which seems to be related to the memory or cache subsystem: 1) Update the motherboard BIOS 2) Re-check all memory timings to make sure they match the values G.Skill recommends 3) If none above helps, it may be best to lower the memory clock and/or to use more relaxed memory timings. Sometimes a simple change like upping the Command Rate (tCR) from 1T to 2T can do magic I personally would never trust a setup that generates hardware failure errors in any stress test software.
  12. Fiery
    That unfortunately is normal for mobile systems since the introduction of Haswell CPUs. The processor is designed to not overheat and not throttle under "regular load" scenarios -- but it will overheat and throttle when running a very demanding task like AIDA64 System Stability Test. As long as the throttling doesn't affect the way you can use your computer, it's not a big deal. If you however can find hiccups while gaming, and you're certain it's because of overheating, then try to improve the cooling of your system. Regards, Fiery
  13. Fiery
    We've implemented a) as right-click context menu --> Copy. The info is copied to the Clipboard as TSV (Tab-Separated Values) that you can directly paste into Excel or other spreadsheet software. You can find the latest AIDA64 Extreme beta at: http://www.aida64.com/downloads/latesta64xebeta We'll work on b too
  14. Fiery
    Thank you for the info. Please upgrade to the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. If it still cannot find your keyboard, then please post a new USB Dump. We've added a few more details to that dump to help investigate this issue. Thanks, Fiery
  15. Fiery
    Windows.Devices.Power.Battery.AggregateBattery.GetReport().FullChargeCapacityInMilliwattHours and Windows.Devices.Power.Battery.AggregateBattery.GetReport().DesignCapacityInMilliwattHours Documentation on those: https://msdn.microsoft.com/hu-hu/library/windows/apps/windows.devices.power.batteryreport.aspx
  16. Fiery
    Thank you for the feedback
  17. Fiery
    Is this an old variant of the K70 or a recent one? Do you perhaps know the hardware revision of the keyboard?
  18. Fiery
    If you start with a blank LCD layout, then AIDA64 would display a splash screen where it shows what resolution you should use. It's not about the native resolution at all, but the resolution the underlying web client uses to render the page. For example, on an iPhone SE, even though the native screen resolution is 640x1136 pixels, the web client uses 980x1648 resolution. If you already have a few items placed on your LCD layout, you can select them all and push the Hide button (in AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD / LCD Items / Logitech Arx). That will effectively clear the layout (while retaining your old items of course), and trigger AIDA64 to show the splash screen on the LCD again.
  19. Fiery
    Thank you for the info. However, under Windows Vista and later operating systems, the Run Registry key is not supposed to be used, since it may interfere with UAC. It's best to clean that Registry path from AIDA64 entries (if there's any), then clean whatever AIDA64 related entries you can find in Task Scheduler (the built-in tool of Windows Vista+), and then enable the Load AIDA64 at Windows startup option in AIDA64 / main menu / File / Preferences / General. In case that way AIDA64 cannot be auto-started at bootup, then it's usually because the security software installed prevents it from running. Then you need to alter the configuration of your security software Regards, Fiery
  20. Fiery
    On iOS, yes, we've managed to find an undocumented method to measure battery charge rate and a few other bits & pieces about battery
  21. Fiery
    Thank you for the feedback
  22. Fiery
    Thank you. Please check it with this new AIDA64 beta: http://www.aida64.com/downloads/latesta64xebeta
  23. Fiery
    Thank you for the feedback. Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Aquaero 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. Please also let us know what flow rate values can you see in AquaSuite 2016. As for the pressure, it's managed separately right now because pressure as a type of sensor item is not implemented in the AIDA64 hardware monitoring module yet. We have to change a lot of little bits & pieces in AIDA64 to make that happen. We'll try to do that before the next AIDA64 beta update
  24. Fiery
    We've implemented support for AquaStream Ultimate in the latest AIDA64 beta update available at: http://www.aida64.com/downloads/latesta64xebeta We seem to have been able to figure out almost everything. The only thing we're not entirely sure about is the flow rate. We use a specific formula that works on other AquaComputer devices, but it may not be suitable for AquaStream Ultimate. Please let me know how it works on your system, and whether the flow rate is properly calculated or not.
  25. Fiery
    I've sent you your product key in private message.
×
×
  • Create New...