Jump to content

Squall Leonhart

Members
  • Posts

    384
  • Joined

  • Last visited

  • Days Won

    3

Squall Leonhart last won the day on September 25 2018

Squall Leonhart had the most liked content!

About Squall Leonhart

  • Birthday 12/31/1986

Profile Information

  • Gender
    Male

Contact Methods

  • Website URL
    vba-m.com

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Squall Leonhart's Achievements

Apprentice

Apprentice (3/14)

  • First Post Rare
  • Collaborator Rare
  • Dedicated Rare
  • Conversation Starter Rare
  • Week One Done

Recent Badges

7

Reputation

  1. these bogus readings appear on Intel z690+ too, when EC reading is on.
  2. https://github.com/ysc3839/win32-darkmode/tree/delayload Technically it works on 10 as well, but there are some things to be concerned about, such as scroll bars, and the menu bar.
  3. it doesn't stay closed because you turned on a plugin in an external application, such as MSI Afterburner which automatically starts aida64 so it can receive data.
  4. update the asus ai suite software or remove it.
  5. These are supplied by Nvidia NVAPI, AMD has no equivalent api.
  6. you may have a HDD that has a high latency for SMART polling.
  7. the cpu usage on the Performance tab is not consistent with utitilities or the usage shown on the Details tab, this is a known issue where the performance and processes tab takes boost clocks and core count awake and used into account when factoring usage, because it factors these into things, the usage on these tabs are usually higher than the Details tab. For the clock reading on task manager and aida64, you need a power profile that has the min cpu state set under 100% to report correct idle behavior having min cpu state in the power profile maxed out to 100 will show constant max clocks in aida64, task manager will show up to 200mhz range from max clock HWInfo will show max actual clock, and low effective clock.
  8. Microsoft has resolved this on their end, aida64 cpu usage without any fixes matches MSIAB with the "fix"
  9. probably a stuck register in the CPU, fiery needs an ISA dump i believe.
  10. Its just a matter of snapshot interval, Aida64 is pulling the info from the nvidia api.
  11. the older driver also resolves a resume from hibernate freeze that was occuring
×
×
  • Create New...