Jump to content

Squall Leonhart

  • Posts

  • Joined

  • Last visited

  • Days Won


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

Contact Methods

  • Website URL

Recent Profile Visitors

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

Squall Leonhart's Achievements


Newbie (1/14)

  • Dedicated Rare
  • Conversation Starter Rare
  • Week One Done
  • One Month Later Rare
  • One Year In Rare

Recent Badges



  1. I've seen it mentioned on a number of occasions that SpeedFan is safe to use with Aida64, however on Asus boards this isn't exactly the case. When I have both running there is a high degree of chance that all the devices indicated to be accessed via ATK vanish. Is aida64 and Speedfan accessing these via the ATK0 driver (ASACPI.sys)? Systems in question are Rampage 3 and Rampage 4 extreme boards.
  2. There is no such security concern, the application run at user level permissions cannot perforrm any kernel level escalation, all it can do is read (and not write to) the aida64 driver.
  3. I've put this towards a vanguard user to try and get a repro and then forward onto AMD, theres clearly an issue with a driver mutex or kernel memory corruption when the two software are paired that needs to be investigated from there end.
  4. Your BSOD is caused by a defective CPU or cosmic waves, contact Intel for a replacement.
  5. Sensor and GPU Sensor info latency is massive, report the issue to nvidia, I'll notify ManuelG of this thread and to be on the watch for the feedback. https://forms.gle/kJ9Bqcaicvjb82SdA You might also go further and perform the following Use nsight to analyze your system for causes of hitching and stutters https://developer.nvidia.com/blog/using-nsight-systems-for-fixing-stutters-in-games/ Then follow on with these if it doesn't display a trigger or theres evidence the issue is in the nvidia driver. Performance reports require the user to submit a gpuview or gpu-z log. How to generating an event trace log for GPUView to troubleshoot performance issues/low FPS/game stutter https://nvidia.custhelp.com/app/answers/detail/a_id/3507/~/how-to-generating-an-event-trace-log-for-gpuview-to-troubleshoot-performance Collecting GPU logs using GPU-Z https://nvidia.custhelp.com/app/answers/detail/a_id/4749/ extended logs can be put on a filestorage host like google drive and their share link mailed to driverfeedback@nvidia.com For the LM78 sensor, disable EC (Embedded Controller) monitoring and iirc for this mainboard you turn Asus WMI on? Your issue is basically caused by multiple utilities on the system hitting the same sensors at the same time which is neither a safe or performant thing to do. Ie, don't run aida64 at the samet time as Hwinfo64, speedfan, corsair link etc.
  6. These are listed as not supported on Processors that support either or both in some cases, meanwhile HWInfo64 is logging the time the processor is in the C6 state just fine.
  7. hi Fiery, I'm not on the affected platform but i can confirm that there are still users experiencing this in the wild. See the users thread here on guru3D https://forums.guru3d.com/threads/3700x-5700xt-crashs-everyday.436494/#post-5883244 Perhaps you might work with AMD to develop a safer API for their card interfaces?
  8. By allowing the administrator account to set a persistent Start = 0x2 from within the Aida64 options, and change the task schedule to include the user account in the name of the Run at Startup task so multiple admins or users can choose to start it or not.
  9. I see, well that would have to be a placeholder name, because the product is the Turing version of the Tesla T10 as shown running here
  10. Why In the change notes do you have the T10-8 identified as a Geforce RTX, when this nomenclature is a Tesla part.? TU102 T10 Generation 8 Tesla board.
  11. No, that didn't seem to work. I found why though, devices on the ASUSTOR driver are treated as a Raid device, so RAID Smart needs to be enabled.
  12. Easy, here you go. The drive is currently on the ASUS UASP driver, but Smart was also missing on the mass storage driver, regardless both could pass through smart to Crystaldisk, and I can also see the data in HD Tune, SSD-Z, etc. diskctrldump.txt raiddump.txt smartdump.txt I also have a cable based on the ASM1351 on order so i can get trim working on this ssd, so i'll likely be back with dumps for that too after it arrives lol.
  13. Hey Feiry, i grabbed a UASP sata 3 adapter cable produced by startech it uses the ASMedia - ASM1153E https://www.startech.com/au/HDD/Adapters/USB-3-SATA-adapter-cable-with-UASP~USB3S2SAT3CB Aida64 is unable to pull smart data from the drive attached, but CrystalDiskInfo has no such problem. Need a dump to add support? if so which ones.
  14. Fiery, the feature this user wanted is possible. The drive itself can report what SATA mode it is in, but not all do so and seems more likely when the Drive is Sata Rev3 / 6Gb with some exceptions being ODD's The utility SSD-Z implements it. Attached to Intel ICH10 sata Attached to Marvel SATA 6G Attached to JMI E-Sata
  15. Interestingly enough, the fields are now visible, seems that this information is not presented by hotplugged drives?
  • Create New...