Jump to content
AIDA64 Discussion Forum

All Activity

This stream auto-updates     

  1. Past hour
  2. Tasos Elemes Tasos Elemes joined the community
  3. Today
  4. Эрнест Исхаков Эрнест Исхаков joined the community
  5. Gabriel Iulian Largeanu Gabriel Iulian Largeanu changed their profile photo
  6. Delwyn Julien Delwyn Julien joined the community
  7. Filter Filter joined the community
  8. Yesterday
  9. Arctucas
    Thank you. You see, this type of customer support is why I will continue to buy renewal license and promote AIDA64.
  10. Koithim
    Here is the USB dump. Thank you very much for your help. K usbdump.txt
  11. Gunner Thrasher Gunner Thrasher joined the community
  12. Erin Huffman Erin Huffman changed their profile photo
  13. Lobopr Lobopr joined the community
  14. Fiery
    We'll add that reading in the next AIDA64 beta update
  15. Fiery started following Thread stuck in device driver (BSOD) (MSI Vega 56 PMLog issue) and New EVGA Z10 RGB
  16. Fiery

    New EVGA Z10 RGB

    Fiery replied to Koithim's topic in Bug reports

    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
  17. Olivier Vekemans Olivier Vekemans joined the community
  18. Last week
  19. Arctucas
    Thank you very much. Keep up the great work! I hate to be a bother, but I noticed that there is a value; '3.3V EC', that HWiNFO reports that is different from the '+3.3V'. Is that a value AIDA64 can display, or no? Thanks again.
  20. Joranccon Joranccon joined the community
  21. Koithim
    Hey there, I replaced my old Z10 with the new Z10 RGB. When i try to enable the LCD i get: Error: HID device 3842-2601 not found. I have the latest beta installed (sept. 16). Cheers! K
  22. honolulu
    It could very well be some bugs in the bios . I also notice a 10% performance drop in 3dmark firestrike with virtualisation enabled in the bios . I don't think that's normal either .
  23. Fiery
    The above mentioned new AIDA64 beta update is available for download at: https://www.aida64.com/downloads/latesta64xebeta
  24. Fiery
    Thank you. Everything looks fine there. I think with virtualization enabled, the APIC clock runs slower than the BCLK for some reason. Maybe because APIC is virtualized then as well. As for the missing sensor readings, in the case the rest of the readings are there, and AIDA64 uses the Asus WMI interface, it is then due to a BIOS bug.
  25. Fiery
    I'm almost certain that if you disable GPU monitoring, the issue won't come up.
  26. honolulu
    Fair enough , thanks for your honesty . If you need some more info , just ask . Would this also mean that if i use aida64 for just cpu monitoring for example , it would not crash my system anymore ? Or does that have nothing to do with it . I can also mention that when i monitor the vega 56 card with GPU-Z , it doesnt not crash or bluescreen .
  27. Fiery
    On Vega 56/64 and RX 5700 Series AIDA64 uses AMD's standard PMLog interface that was designed to avoid such collisions when both AMD's video driver and 3rd party applications try to poll sensor readings and they alter GPU registers in a concurrent way. Apparently PMLog is still not 100% stable, so using it causes different issues then previously when low-level register readout caused collisions I'm afraid we cannot fix that issue from our end, so you need to report this to AMD and ask them to fix PMLog in their drivers.
  28. honolulu started following Thread stuck in device driver (BSOD) (MSI Vega 56 PMLog issue)
  29. honolulu
    Long story short , since june 2019 i have a new videocard (MSI Vega 56 Air boost OC) , which I am trying to get stable for the past 3 months now . I have been trying everything , swapping hardware in and out , changing fansettings , adding fans , DDU drivers , updating all programs/drivers on my pc and what not . Every time the PC crashes , i have to do a CMOS reset to get the pc to boot again . Just a restart or power down is not enough . The "Thread stuck in device driver" blue screen analysis points towards DX and AMD drivers , hence me being focused on those things at first . So in the end nothing helped and I decided to try to run stability tests in a completely new windows 10 x64 installation . Only installing chipset driver , sound drivers and videocard drivers . Suddenly no more crashes ... Since in a clean windows install stopped the crashes (meaning the hardware is fine) , i went back to my old windows installation to try and find out what software was causing these BSOD's . In the end I had a stable run of several hours .Yay ! Where the only program i closed was AIDA64 . So I decided to stop the stability test . After closing the stability run (Heaven benchmark) I opened AIDA64 back up . What do you think , mere 2 minutes after opening I get BSOD with thread stuck in device driver again . And this was just on the desktop , with no stresstests running . So the next day i closed 3 monitoring programs to be sure : AIDA64 , Rivatuner statistics server and Remote panel . I fired up a gpu stresstest and let it run all day and night . No crash ... . It was still running when i woke up the next day . This never happened before ! Software versions : - AIDA64 (I always used latest beta's since june 2019 . currently using 6.00.5161) - Rivatuner statistics server 7.2.2 - Remote panel 1.16 - AMD driver always latest optional since june (currently 19.9.2) The output of my monitoring currently goes towards a Samsung Galaxy s5 connected through usb) . But before I used a G19 keyboard , which was causing the same BSOD . To this post I also attached a bluescreen analysis with WhoCrashed . BSOD thread stuck in device driver analysis.txt
  30. Jeff Stubblefield Jeff Stubblefield changed their profile photo
  31. Xưa Điên Xưa Điên changed their profile photo
  32. tistou77
    Ok thanks I will put the fan on the fan controller, no monitoring
  33. Fiery started following Fan Information "Chassis # 2"
  34. Fiery
    I have no idea what disabling a certian fan RPM reading is accomplished by the BIOS Setup, but most likely it just means that the BIOS Setup stops monitoring that fan. It still could mean that the fan RPM register indicates a reading, and actually no sensor register is altered to indicate that Chassis #2 fan RPM readout is disabled. I'm not sure what to do about such issues. Unless of course you use the SensorPanel, OSD Panel (etc) modules where you can select which items you want to hide or show
  35. tistou77 started following Fan Information "Chassis # 2"
  36. tistou77
    Hello I put a fan on the Chassis #2 of the Asus Rampage VI Extreme, I disabled the Chassis #2 fan monitoring in the bios, but Aida64 still indicates the information It is not possible to disable Chassis # 2 in Aida64, since it is disabled in the bios ? Thanks
  37. Tdubbs
    The beta is the latest release, plus bug fixes and added code to work with more hardware than was available at last stable release. The next stable release will be a culmination of everything added over the various betas.
  38. xmanrigger
    Thanks for the reply. Yes, it worked. But I just paid for and am running the latest version, 6.00.5100. Why doesnt latest release work?
  39. MatG
    It works perfect, also when gaming. Thank you so much Fiery :))
  40. Fiery started following Aida64 wont display EVGA RTX2070 Super clock or memory speeds
  41. Fiery
    Make sure to upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps.
  42. xmanrigger started following Aida64 wont display EVGA RTX2070 Super clock or memory speeds
  43. xmanrigger
    Installed an EVGA RTX 2070 Super Black Gaming (08G-P4-3071-KR). GPU temp and voltage reported as well as GPU and memory usage. But GPU core and memory speeds not being reported. Using aida64 V6.00.5100. All previous VGA cards reported properly. Any ideas? SPECS: aida64 V6.00.5100 Win7 Pro 64 MOBO: ASUS RIVF BIOS 4804 (yes, older BIOS, but yields best overclocks) CPU: i7-3930K MEM: Corsair Dominator Platinum 2400mhz GPU: EVGA RTX 2070 Super Black Gaming (08G-P4-3071-KR) (DRIVER 436.3) PSU: Corsair AX1200i
  44. tocirahl
    Good news though! 5.95.4500 doesn't seem to have this issue. Unfortunately it also doesn't seem to fully support my GPU (EVGA GTX 1080 Ti FTW3 Hybrid) so I'm not getting memory temperature readouts for it, which I can live with. Looks like something between those two versions is causing the issue.
  45. tocirahl
    I've verified that this problem definitely still happens on version 5.97.4600.
  46. honolulu started following Asus Prime X470-Pro - 2 issues (Virtualization, Asus WMI)
  47. honolulu
    #1 see attachment #2 it is already enabled . so i can not enable enable it see list of what's enabled (stability.png) cpuidmsrdump_virtualisation disabled.txt
  48. MatG
    Thank you Fiery, i just disabled Embedded Controller (EC) support and it helped with the Core spikes. I'll keep you updated on the gaming part later.. The autostart function, i can make an automated task in windows that is delayed for a minute after start/logon if it still hangs in loading screen.
  1. Load more activity
×
×
  • Create New...