Jump to content
AIDA64 Discussion Forum

All Activity

This stream auto-updates     

  1. Today
  2. Ok did that thank you, i hope for the best. So i avoid using aida64 for now ;-(
  3. Squall Leonhart

    AIDA64 and Aorus Graphics Engine doesn't work

    Gigabyte are using a nasty mutex access, as usual :\
  4. Exactly the same issue here on my x370 taichi motherboard, fans spin to 100% randomly, only a reboot slows them down.
  5. Squall Leonhart

    Asrock X370 Taichi Fan Spin Up Bug

    oh, there is previous feedback
  6. Driver feedback to https://surveys.nvidia.com/index.jsp?pi=6e7ea6bb4a02641fa8f07694a40f8ac6 dump file to driverfeedback@nvidia.com
  7. POE

    Asrock X370 Taichi Fan Spin Up Bug

    No even from a fresh install aida 64 still does this
  8. Squall Leonhart

    Asrock X370 Taichi Fan Spin Up Bug

    you are mixing system management utilities.
  9. dump file must go to nvidia and feedback provided with system details, this is an nvidia driver bug. PS: it comes up as being in ntkrnlmp.exe here, all changes based on the application scanning the dump.
  10. Turn hpet on, This is a platform bug where timers slowdown after resuming from sleep.
  11. Hi there I have a similar problem. My minidump files however are pointing at nvlddmkm.sys. The "kmode_exception_not_handled" only occurs during long idle times...... never while hammering my system @ 100% with stress tests or demanding games. My System: Aida64 latest build (with remote display active trough tcpip) i7 3770k Asus z77 Maximus V Extreme (latest BIOS 1903) Gskill Trident 16 GB @ 2400 EVGA 980 ti Classified (Latest Nvidia drivers 397.64, DDU cleaninstall) WIndows 10 B17134 (Clean install through iso image) I tested it to be certain;: When AIDA64 is running my system will do a bugcheck and quit with kmode_exception_not_handled, rebooting into logon screen after about 30 min to 60 min. Without Aida64 it idled 12h+ Ive been using aida64 for many years now and i dont want to miss it any suggestions? Thank you 052418-6937-01.dmp
  12. Greetings Aida Team! I'm using this Software for quite some time now for monitoring my hardware along with the Logitech G19 LCD Keyboard. First of all, the sensors work as they should with everything "default" enabled. Problem is the LCD support for certain sensors (I think). with defaults and LCD running I got random freezes watching video or listening to music. even some games used to freeze and it always comes with a loud buzzing sound in all cases. however, I did some research and played around with the "stability" settings in Aida64Extreme by switching and testing. the "Low-level MSR operations" option turned out to be the culprit. with this one unchecked I get decent results with "DCP Latency Checker" even with G19 LDC activated. however, because of the missing "Low-Level MSR operations" I miss some sensors such as individual core speed, PCB temp or CPU power usage. I attached my Aida Hardware Report File as well as DCP Latency comparsions (defaults enabled, LCD disabled and LCD enabled but low-level MSR disabled). I hope there will be a fix for this issue because I'm missing some important sensors on my LCD display lately. best regards, Nokrahs Oliver nokrahsReportAida.txt
  13. Yesterday
  14. Squall Leonhart

    Page file details may randomly glitch

    This topic involved a crash in the application that occured when it was left on that page of aida64, this has been fixed for a long long time now. PS: Don't turn off the page file, windows can't do some things with one turned off, such as allocate large virtual blocks (whether it intends to fill them or not). Set a Min/Max pagefile instead.
  15. Squall Leonhart

    AIDA64 is freezing PC

    Drive type and model would be agood idea too ;), as well as the ahci driver in use.
  16. Fiery

    AIDA64 is freezing PC

    Please let me know what motherboard, CPU and video card(s) do you have, and whether you're using the latest Windows 10 build (17134).
  17. Forumuser

    AIDA64 is freezing PC

    Hello, I have recently upgraded to the latest Intel 8th series CPU/MB and since then AIDA64 is freezing my system after a few readings. Initially its ok when I run it, then switch to Sensors and leave it there. Its freezing system in 20-60 seconds. Also when I am successful enough to run it for a couple of minutes, once I wake up my PC from the sleep, CPU temp reading reads -55 C. Please let me know how do I debug these issues?
  18. Last week
  19. Are aida64 devs not responding anymore?
  20. tistou77

    Order of SSD display

    Yes, I know but I'll wait until you integrate the customization (renamed) the names of the probes, etc ... in this menu
  21. tistou77

    Order of SSD display

    Ok thanks for the explanation, even though I did not really understand why the Intel drive is between the 2 Samsung drives
  22. so far so good at the moment with the SMB unticked.
  23. Hello, I try to display the CPU Clock of a Processor with Turbo Boost enabled. (LGA 2011-v3) If I display the CPU Clock within the TaskManager (Windows 10) it shows me every second a new value inert the Clock variant. It may differ extreme with two decimal values. E.G. 2.73 GHz- 3.45 GHz and so on. Of course, this is a calculated value. If I show the same CPU Clock value within Aida64 it will only show 2 Values with only a little differentiation. 1200.1 GHz what is indeed the lowest level and 4500.1 what is the highest value. In some Cases it will show 4499.8 or 4499.9 instead of 4500.1. If I look with an MSI Tool over the CPU real Frequency it will, of course, differ in many circumstances over all cores in a great variant. All cores runs with different clock scores. So, what is the difference between the calculation of the real clock to the displayed value in Aida64? ​How did you calculate the value? The calculation of the TaskManager seems to be smoother and smarter then the aida calculation. PS: The same behaviour on the CPU Multiplier, this value shows also only two values, min and max. an never a value between.
  24. I believe the nvidia kernel mode driver is suffering a double free or use after free which is brought on via applications using nvapi, thats why the faulting process is one which accesses the card using this api. windows will often say ntoskernl or ntkrnlmp because of an imprecise timing issue in the exception handler, in my case its pointing at X64_0x1E_nt!KiDispatchException+1c7 which is definitely not the actual fault lol.
  1. Load more activity
×