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
    Since there's a workaround for this issue (that I've mentioned above), we're not considering getting back to working on it. It would require us to come up with a new rendering solution, so it's not a few days work. And performance of rendering may also suffer because of transparency.
  2. Fiery
    We haven't got any further assistance from AMD to step further about that issue. There may not be a technical solution afterall
  3. Fiery
    The memory bus properties on the Motherboard / Motherboard page may refer to only the primary CPU of the system, or only the primary IMC (Integrated Memory Controller) of the system. You can check all IMCs for all installed processors on the Motherboard / Chipset page. The AIDA64 CPUID Panel however uses a trick to aggregate all available IMCs to show the total number of memory channels across all CPU sockets. We'll add the missing motherboard physical information in the next AIDA64 beta update due later this week
  4. Fiery
    You can only get rid of throttling by improving the cooling of the CPU. Since you already have a powerful solution, I'm not sure if there's more room for you to push the OC further. As for microstuttering, that can be caused by a few issues, and one of those is when the CPU momentarily throttles to mitigate overheating.
  5. Fiery
    The recently added new command-line option is: /STAY This option can be used to keep AIDA64 running in the background after report creation. It is useful when Network Alerting is used together with /R, /E or /FTPUPLOAD options. The default behavior is that after the report creation process is finished, AIDA64 quits. One can override this by using the new /STAY command-line option.
  6. Fiery
    We've checked, and we haven't been able to reproduce this issue with either Crimson 17.5.2 or 17.9.3 WHQL. Maybe because we use a RX 560 test card, and the issue affects only RX 570 and RX 580? Please right-click on the bottom status bar of AIDA64 main window --> Video Debug --> ATI GPU Registers. 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. BTW, have you tried to install the recently released Crimson 17.9.3. WHQL driver? I wonder if that makes this issue go away or not. Thanks, Fiery
  7. 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
  8. Fiery
    I apologize for the late response (in your other topic). Let's continue investigating this issue here. If you disabled EC support already, then I don't think merely reading a SIO (Super I/O) register like at index 43h could cause such issues. You can try dumping all SIO registers (all 256 of them) by issuing an ISA Sensor Dump, and see if any of those register readouts make the fan spin up to 100%. Right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. If you make such a dump, then please also 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. The dump may help us understand more about your system, and may provide us tips on where to look next. I really thought disabling EC support would cure the issues you're having on your system. Thanks, Fiery
  9. Fiery
    I'm sorry for the late reply. Let's continue this discussion in your other topic
  10. Fiery
    On your particular video card those 2 values are measured using different methods, so you definitely shouldn't add those numbers up or combine them in any ways. AMD GPUs use quite a few secret tricks that are not documented well enough -- but AIDA64 uses those tricks to provide every possible measurements. Due to the lack of documentation though, it's hard for us to provide you with guidelines on how to interpret the readings.
  11. Fiery
    We've only recently managed to acquire a Vega test card that we can use to improve the GPU diagnostic capabilities of AIDA64. We're already working on the issues you've mentioned, as well as a few other Vega related matters. I'll post a message into this topic once a new beta build of AIDA64 becomes available for download
  12. Fiery
    My guess would be the same: Steam must start a background process or service that constantly consumes a few CPU cycles. It would then leave that background process and service running after you closed the Steam Client.
  13. Fiery
    When the NIC items cannot be selected for your graph, what is the speed reported as numbers for your NIC1 Upload and Download rates? Also, can you see the upload and download rate properly reported on the Network / Windows Network page?
  14. Fiery
    What is the speed reported as numbers for your NIC1 Upload and Download rates? Also, can you see the upload and download rate properly reported on the Network / Windows Network page?
  15. Fiery
    I'm afraid it's not easy to get around that issue. If you're sure that your computers are all running AIDA64 already, then you can use the Remote Report Wizard feature to make a report of multiple remote computers though. If you cannot be 100% sure that AIDA64 is running on all your computers, then you may want to come up with a solution to first close a running instance of AIDA64 and only after then try to launch it again.
  16. Fiery
    Current clock frequency can already be measured in the AIDA64 System Stability Test. The rated Turbo clock levels for the individual AVX levels of the underlying hardware cannot be detected currently. We'll check that, although it may not be possible to detect it using classic detection methods, but only via a built-in CPU SKU database. The FPU subtest of the System Stability Test uses AVX2 when it's available (e.g. Haswell, Broadwell, Skylake, Kaby Lake), and AVX when it's available (e.g. Sandy Bridge, Ivy Bridge). AVX-512 is not yet supported, so on AVX-512 capable processors AIDA64 System Stability Test uses its AVX2 codepath. We're planning to implement full AVX-512 support, including AVX-512 optimized benchmarks and AVX-512 stress test in the upcoming months. We previously wanted to roll it out during the summer, but AVX-512 is way too complicated, and we needed (and still need) a bit more time to fully exploit its full potential in AIDA64.
  17. Fiery
    Please right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA GPU Registers. 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
  18. Fiery
    If the fan issues are caused by AIDA64 polling the EC (Embedded Controller) chip of your motherboard, then good news is that using the latest AIDA64 beta build you can now disable EC support in AIDA64 / main menu / File / Preferences / Stability: https://www.aida64.com/downloads/latesta64xebeta
  19. Fiery
    Once NetUpdate downloaded all files and asks you to let it restart itself, please do not let it do so just yet. Instead, go to the AIDA64 installation folder, and check whether there's a file called AIDA64.EXE.NEW in there. If not, then I guess AIDA64 has no permissions to write its installation folder. In which case it may be best if you could try moving the AIDA64 installation folder to e.g. C:\ That may help about the auto-update issues. Alternatively, you can try backing up the AIDA64 configuration file (AIDA64.INI) and license file (PKEY.TXT), both from the AIDA64 installation folder, then uninstall AIDA64, then reinstall it to C:\AIDA64 folder.
  20. Fiery
    The above mentioned new AIDA64 beta is available for download at: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works
  21. Fiery
    Thank you. It's quite puzzling at this point We've tweaked a bit on it, but we're not 100% sure whether it makes it better or worse. Please check it out, and let us know how it works now. https://www.aida64.com/downloads/latesta64xebeta
  22. Fiery
    Those measurements are obtained via the NVML API, which is difficult to utilize from our software. We will need to work more on it, and implement special tricks to use NVML, and so you can have the same GPU power draw measurements in AIDA64 as well.
  23. Fiery
    Thank you. We've done a number of test runs with different display configurations, all in horizontal arrangement, and couldn't reproduce the issue We may need to build a more similar setup to yours, in terms of operating system type, and the same display resolution as well. Please let me know those parameters, and also the approx. placement of the SensorPanel on your Windows Desktop. Alternatively, try to place the SensorPanel where you prefer it to be, close AIDA64, open Registry Editor (Windows key + R --> regedit), navigate to: HKEY_CURRENT_USER\Software\FinalWire\AIDA64 And let me know the value of these entries there: SensorPanelPosX SensorPanelPosY Having those coordinates, along with the exact resolution of both your displays, and the approx. coordinates you wish to have the SensorPanel placed should give us a bit more idea on where things may go south about the SensorPanel position restoring on your configuration.
  24. Fiery
    As I've mentioned above, any "lite" or cut-down version of AIDA64 would cost the same as the current AIDA64 Extreme edition. We simply cannot lower the base price, since it wouldn't be a sustainable business model for us.
  25. Fiery
    Thank you for the data. The measurements comes via the NVML API, which is difficult to utilize from our software. We will need to work more on it, and implement special tricks to use NVML.
×
×
  • Create New...