Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    11546

  • Joined

  • Last visited

  • Days Won

    489

 Content Type 

Everything posted by Fiery

  1. Fiery
    Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Sensor Profiling 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
  2. Fiery
    I've sent you a private message about this issue.
  3. Fiery
    You've got a private message
  4. Fiery
    Please right-click on the bottom status bar of AIDA64 main window --> System Debug --> USB 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
    Please right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA SMBus 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
  6. Fiery
    We've never tried that, so would love to hear some feedbacks on such a configuration.
  7. Fiery
    Intel uses VCCIN for the Skylake-X voltage rail in question, so that's the correct term to use by monitoring software as well.
  8. Fiery
    If you don't have Asus AI Suite installed, try to enable the 2 options about EC in AIDA64 / main menu / File / Preferences / Stability: Embedded Controller (EC) support Embedded Controller (EC) bank switching After altering those options, make sure to restart AIDA64 to apply the changes.
  9. Fiery
    Please navigate to the installation folder of AIDA64, and create the following 2 new files there: ENABLE_SMBUS_LOG.TXT ENABLE_HWMONINIT_LOG.TXT They can be simply 0 byte long (empty) files. Then start AIDA64, go the Computer / Sensor page, wait for your computer to lock up, restart it, and check the 2 files that you've previously created. If they have a content, please attach the files to a forum post, so we can check where the lockup occurs inside the AIDA64 sensor module. After finding the culprit, we can work on fixing the issue or implementing a workaround. Thanks, Fiery
  10. Fiery
    HDMI, DSub, DVI and DisplayPort connected displays are handled as regular monitors by Windows, so you can use the SensorPanel module of AIDA64 to display sensor readings on your secondary monitor. If the display is always connected, the SensorPanel window will be placed at the right monitor at the right coordinates once you start AIDA64. Of course you can make AIDA64 launch automatically at Windows startup by enabling the option AIDA64 / main menu / File / Preferences / General / Load AIDA64 at Windows startup As for configuring your SensorPanel layout, make sure to check this guide: https://www.aida64.co.uk/knowledge-base/how-create-fully-customized-sensorpanel-aida64
  11. Fiery
    Not yet. We're planning to roll that out early next year.
  12. Fiery
    1) Reviewers do not rely on our reference results, but they use their own test results. And apart from reviewers, not many folks are interested in single-core benchmarks. Why to have 4, 6, 8 or 18 cores in your CPU and only use just one to check how great your CPU is? 2) No, we have no plans on that.
  13. Fiery
    I'm afraid we have no specific idea on what to do about that. Try to ask the same question in a forum that's geared towards Asus ROG users and products, or specifically Maximus VI motherboards and their owners.
  14. Fiery
    Thank you, that's great news!
  15. Fiery
    No, we haven't. But, let's hope that the new BIOS that Grainger posted above helps.
  16. Fiery
    It's hard to provide proper feedback on that. On the one hand, 45-50% throttling is quite a lot, so I'd take it as alarming. However, since it's a brand new notebook, there shouldn't be any cooling issue due to hardware failure or dust clogging up the exhaust ports, etc. So it may just be normal the way it is. It may be worth checking what happens if you restart your computer, open AIDA64, open System Stability Test, but don't start any test there. Just let it sit and watch as the throttling is monitored. Now, start a game, play for 30 minutes, and check back to the System Stability Test whether it indicates that the computer was overheating without running a stress test but while playing a game. If throttling exceeds 25% while playing a game, I'd take it back to the shop and inquire the sales persons about it.
  17. Fiery
    Try to go to AIDA64 / main menu / File / Preferences / Stability, and de-activate Embedded Controller (EC) support. You need to restart AIDA64 after altering that option. Let me know if it helps. Also, make sure to not have Asus AI Suite installed on your system, and that if you had it before, then all its background services are also uninstalled properly. AI Suite may just collide with the sensor polling activities of AIDA64.
  18. Fiery
    For nVIDIA video cards the video memory information is only detected for the first video adapter. Maybe the issue is that ForceWare manages your video cards in a different order than what you expect based on the PCIe slot arrangement?
  19. Fiery
    Thank you for your feedback
  20. Fiery
    Thank you both for your feedback
  21. Fiery
    1) What motherboard do you have? 2) Are you referring to the temperature labelled as "PCH" or the one labelled as "PCH Diode" ?
  22. Fiery
    1) Single-core PC benchmarks aren't relevant in this day of age. Also, it would grealty overcomplicate the maintenance of the reference benchmark results database. 2) It's not possible to limit the number of cores or CPU threads to be utilized by the AIDA64 multi-threaded cache and memory bandwidth benchmarks. It's by design, since those benchmarks automatically calibrate themselves to use the optimum number of cores and optimum settings (code path) to squeeze the maximum bandwidth out of the caches and RAM.
  23. Fiery
    It's due to the difference in motherboard and CPU as well.
  24. Fiery
    It's not that high, so I wouldn't be alarmed by it anyway.
  25. Fiery
    Thank you. In that case there's a good chance the +5VSB reading is invalid. Check if you can see that reading in the BIOS Setup or in ASRock's own monitoring utility. If it's not there, it's an invalid reading that you can ignore.
×
×
  • Create New...