Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12389

  • Joined

  • Last visited

  • Days Won

    550

 Content Type 

Everything posted by Fiery

  1. Fiery
    Please right-click on the bottom status bar of AIDA64 main window --> CPU Debug --> CPUID & MSR Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. We'll have to check the registers, and compare them against our 5820K. Maybe there's a way to fix it up by applying a workaround. Thanks, Fiery
  2. Fiery
    Can you please check if you experience the same issue with HWMonitor? BTW, on our 5820K + Gigabyte X99-UD4 system AIDA64 measures cca. 10W at idle and 100W under heavy load. So the problem may be related to 5930K or Rampage V Extreme motherboard.
  3. Fiery
    Please upgrade to the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild3206lgct2wrjxkzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how if it helps.
  4. Fiery
    Please report the issue to cleverbridge, our online payment processor. They will have to investigate this. Thanks, Fiery
  5. Fiery
    In case the FPU-only test also works fine, then yes, it should be considered a safe setup.
  6. Fiery
    What kind of data or conclusion would you be able to draw from such output? Regards, Fiery
  7. Fiery
    We believe the AIDA64 System Stability Test is a great tool to challenge your system's stability. Enable all subtests, press the Start button, and leave it running for a few hours. If it can stand that, then stop the test, enable only the FPU subtest (and the GPU subtest in case you've got a discrete video adapter, like a video card), press the Start button, and leave it running for a few hours again. In case your system can work under both settings stable, then I'd consider it a stable configuration. BTW, the first test I've mentioned is geared towards challenging computing stability, while the second test is to test thermal stability, ie. whether your system cooling is adequate. Regards, Fiery
  8. Fiery
    Do the memory timings appear properly on the Motherboard / Chipset page?
  9. Fiery
    Problem is: the USB protocol for LCDsysinfo was only published for the original LCDsysinfo device, but not for the more advanced GOverlay device. We've contacted the company behind the GOverlay both in email and through eB*y to request specifications, API description, SDK or any other material to let us connect to the device in AIDA64, but we've got absolutely no response from them. It's quite tough to work this way, and I cannot promise anything at this time about GOverlay.
  10. Fiery
    It depends on the motherboard PCB layout. But it's a safe assumption that the temperature diode measuring VRM temperature is placed close enough to the VRM circuitry.
  11. Fiery
    Our slight concern is the motherboard-integrated VRMs are not really inside the CPU package or even right next to the CPU socket in a strict sense. So using the CPU icon may not be closer to the truth than using the current icon.
  12. Fiery
    The issue will be fixed in the next AIDA64 beta release due in a few days from now
  13. Fiery
    What sort of security software do you have installed? Maybe that is the one that blocks AIDA64 from starting up at Windows boot.
  14. Fiery
    Make sure to upgrade to the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild3203dw9pkvh8sxzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps. Thanks, Fiery
  15. Fiery
    The icon in question isn't actually a battery icon, but more a generic power icon. It shows the battery in the background and a power plug in front of it. I admit, it's not the perfect icon to represent power delivery, power supply or a VRM, but there're other kind of VRMs that may or may not be directly related to the CPU, that's why we use a more generic power icon. Regards, Fiery
  16. Fiery
    I've sent you a private message about this.
  17. Fiery
    Notebooks, especially the ones using Intel Haswell-class processors, tend to operate at much higher temperatures than comparable desktop systems. Maximum temperature of 80 Celsius is actually not bad at all. Also, Haswell processor based processors can easily get to a point of overheating and throttling, it is considered normal operation for them. I'm not sure about cooling pads, never used such a thing. I suggest you to try googling for: notebook cooling pad review Regards, Fiery
  18. Fiery
    We've tried to replicate the issue on our DeathStalker Ultimate, but had no luck. For us everything worked properly. We've put a set of custom gauges on a gauge that we've put on Page#1, and then we've used another set with another gauge we've put on Page#3. Both gauges displayed fine, with the appropriate custom gauge state images. Please let me know if you experience a different issue. Also make sure to upgrade to the latest AIDA64 beta, it may (or may not) help http://www.aida64.com/downloads/aida64extremebuild3203dw9pkvh8sxzip
  19. Fiery
    I'm afraid we haven't yet found a way to display SensorPanel when using Aero Peek. I'm not even sure if that's possible to do...
  20. Fiery
    Here's the fix for the new firmware CFA-835 LCD: http://www.aida64.com/downloads/latesta64xebeta
  21. Fiery
    Thank you for the feedback
  22. Fiery
    No, I'm a real person, just like Siri And sadly, I cannot reply everyone as soon as I'd want to... I'm glad you've managed to solve it. Sometimes things are easy, but not obvious. And we cannot possibly wire everything to the user interface without making it unusable
  23. Fiery
    There's no way to do that automatically, from AIDA64. What you can do however is: 1) Close AIDA64 2) Save your AIDA64.INI file (backup) 3) Open AIDA64.INI file in Notepad or another text editor of your choice 4) Replace all occurences of HWMonLCDItemLgQ1 with HWMonSPItem 5) Save the changes, and start AIDA64. Enable the SensorPanel, and see if it look as intended. You may have to adjust the SensorPanel size to 320x240 pixels. Please note that the above explained steps will only convert the 1st Logitech G19 LCD page to SensorPanel. Also note that any existing SensorPanel items will also be kept, so before step#1 above, you may want to clear all SensorPanel items first. I hope it helps Regards, Fiery
  24. Fiery
    You can set it in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Update Frequency.
  25. Fiery
    It seems the problem is that AIDA64 handles CFA835 LCDs following the first spec issued for the display, based on firmware rev 0.1. We'll also update our CFA835 device to firmware rev 0.6 and adjust the LCD module to fit the major changes that the latest CFA835 firmwares introduced. I'll soon send you a new AIDA64 beta to try
×
×
  • Create New...