Jump to content

Fiery

Administrators
  • Posts

    11334
  • Joined

  • Last visited

  • Days Won

    476

Everything posted by Fiery

  1. Please try to disable Razer LCD support and enable SensorPanel or Logging instead. That way you could narrow it down to the sensor module being at fault, or the Razer LCD module itself. Let me know how it goes. Thanks, Fiery
  2. Delayed for sure I'm sorry for not being able to promise anything at this time.
  3. Do you use DPI zoom on either one of your displays?
  4. Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> SMBus Dump (Full). 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. Quite a lot. Under the hood the Windows kernel is under constant improvement and change. Probably Microsoft made a mistake about supporting your processors to the last bit
  6. Thank you. It's quite a puzzling issue I'm afraid we need two more dumps: Please right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> RAID Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post.. Right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> NVMe Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery
  7. Please right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> ATA 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. Also right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> RAID Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Then right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> NVMe Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Finally, right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> SMART Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery
  8. Please right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> SMART 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
  9. The first one out of the 3 monitors lacks the necessary information to detect it properly, but we've added the last two in the latest AIDA64 beta update: https://www.aida64.com/downloads/latesta64xebeta
  10. I guess this would overwrite an XML file periodically on the file system. It's not a good idea in the long term, especially if you have a SSD. We haven't heard back from Asus yet...
  11. I'm afraid there's no log or other info that we could use to find out more about what happened on your system about the upgrade. If you don't like the idea of simply replacing the files manually (which the auto-updater would do anyway), what you can do is backup your Preferences file (AIDA64.INI) and license file (PKEY.TXT). You can find both files in AIDA64 installation folder. Then uninstall AIDA64 v5.99 and install AIDA64 v6.00 using the self-installer EXE package. Then copy back your Preferences and license files to the new installation folder, and you're good to go.
  12. What you can try is to disable Embedded Controller (EC) support in AIDA64 / main menu / File / Preferences / Stability, and restart AIDA64 to apply the changes. You will lose a few sensor readings that way, but it should help to get rid of the stuttering.
  13. It's tough, because there are tons of Windows drivers and services installed even with a fresh Windows installation
  14. That's an interesting device. Do you know anything about the protocol one needs to use to submit alphanumeric or graphical data to the display?
  15. Virtual memory is the whole memory space Windows can use for various purposes. It includes both physical memory and swap space (pagefile or pagefiles).
  16. Please post a screenshot of the Preferences / Hardware Monitoring / LCD page as well, so we can see which LCD device you've enabled and what your settings for that device are. Thanks, Fiery
  17. Simply put: Core i7-6700K CPUs shouldn't throttle, even at +30 Celsius room temperature. If it shows any amount of throttling, you need to improve cooling of your CPU and/or your system case. As for the long bootup time, I'm not sure what might cause that. Maybe a Windows driver or service keeps holding up the booting process?
  18. It's not possible to measure utilization for Intel iGPUs. What other software might measure is Direct3D utilization for Intel iGPUs, but it's not the same as real GPU hardware utilization.
  19. 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
×
×
  • Create New...