Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12009

  • Joined

  • Last visited

  • Days Won

    525

 Content Type 

Everything posted by Fiery

  1. Fiery
    Anytime
  2. Fiery
    1.8V is not VID at all, but some bogus value
  3. 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
  4. Fiery
    That happens when the sensor item is no longer available. Do you still have the UPS connected to your computer?
  5. Fiery
    We've done some experiments on that, but it wasn't successful. If the BIOS fails to properly initialize the thermal controller, PCH Diode temperature cannot be measured by Windows software or any other method
  6. Fiery
    The video driver reset takes a second or two, and after it is done everything should go back to normal. Except for the GPU subtest of the AIDA64 System Stability Test which will be stopped after the video driver reset. So in case a permanent blackscreen is exhibited, it may be due to a video driver reset issue in the first place, but then the video driver cannot recover due to -- in most cases -- a hardware stability issue. In other words: if you cannot get the display output working after the video driver reset, it's a hardware malfunction. Such malfunction can be due to a number of reasons, including excessive overclocking (and/or overvoltage), overheating, video memory stability issues (or overheating), PCI Express communication breakdown, etc.
  7. Fiery
    And we've done that in the latest AIDA64 beta update available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade.
  8. Fiery
    The mentioned new AIDA64 beta update is 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.
  9. Fiery
    We've added the requested new hot key in 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.
  10. Fiery
    1) If you're a power user, then I suppose shifting the indexes by one shouldn't be a problem 2) Please make a screen shot (or report, or copy-paste) of the Storage / Physical Drives page of AIDA64 at both states (when it's OK; and when the anomaly occurs).
  11. Fiery
    Thank you, that's great to hear
  12. Fiery
    Power out is calculated using the same formula as power efficiency. Efficiency = power out / power in. And out of those 3 values only the power out value can be directly measured or detected on most PSUs.
  13. Fiery
    I'd still say: I don't think it would qualify your motherboard for a RMA, but it may worth a try to call the store where you bought it.
  14. Fiery
    The best idea is to use an old classic LCD display (monitor) that you can connect via DSub or DVI cable, and extend your Windows Desktop onto it. Then you can sack the Samsung LCD module and use the much smoother working SensorPanel instead. If you want to re-use your Samsung LCD layout on your SensorPanel, then simply export the LCD layout (in AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD / LCD Items) and import it back to your SensorPanel using the SensorPanel Manager. You can launch the SensorPanel Manager via the right-click context menu on the SensorPanel.
  15. Fiery
    It could be the uncommon setting of disabled HyperThreading. Just in case, we'll check that scenario with our i7-5820K CPU.
  16. Fiery
    Thank you for your feedback. Quite frankly, I would have done the same, ie. to sack the HDD with the "weird" working firmware and use a different HDD model instead.
  17. Fiery
    Thank you. We'll remove the CPU Core voltage reading on Gigabyte X299 motherboards, and use CPU VID voltage as Vcore from now on.
  18. Fiery
    Thank you. Can you please try to configure the same fan duty cycle (%) value in AIDA64 / main menu / File / Preferences / Hardware Monitoring that you have configured in Corsair Link Software? Check the "Set Asetek fan speed" checkbox, and set both % values to the fan duty cycle of your choosing.
  19. Fiery
    We can do that, but I don't think it would help The only thing that helps -- and your case confirms this -- is to increase the update rate to several seconds (from 1 sec or sub-1 sec).
  20. Fiery
    RTSS labels cannot be customized at this time, so AIDA64 uses their default values. Regards, Fiery
  21. Fiery
    1) Power users and software developers are fond of zero-based indexing, but for the majority of users a one-based indexing is easier to follow. 2) I guess the explanation behind that anomaly must be that for some reason after system restart (or cold boot) your Windows installation messes up the physical drive indexes. So e.g. disk#0 may become disk#4 and vice versa, but it is restored back after the next reboot.
  22. Fiery
    It can be many things, including CPU, RAM, BIOS issues, etc... Hard to tell.
  23. Fiery
    I guess your system is just very sensitive to even the slightest overclock...
  24. Fiery
    Are you sure your panel can still go to mini-monitor mode? I'm afraid to me it looks like a hardware malfunction that can be due to a firmware issue.
  25. Fiery
    Thank you for your feedback
×
×
  • Create New...